You hear a lot about agile methodology, especially when you are assigned to the web designing work. In here, you will learn more about agile methodology and how it can help your work be more productive.
The term “agile” is an odd industry term among designers that have never experienced working in the software space. This is a phrase that is widely used by many recruiters and employers, yet the people delivered with this term don’t seem to get it.
Don’t assume that this is a comprehensive guide nor is it a bible about “agile” or SCRUM, however it will give you ideas if you are going for a job interview for a company that deals with software or any other products associated with it.
Where Agile came from
The term “Agile” came into being back in the year 2001 when a team of software developers thought about and decided that they desired a different workflow. The formulation they’ve come up with were of 12 principles and then wrapped all of them as its manifesto. In it, it defines a process, thus referred to as a methodology.
What Agile is
If you can find a diagram of what a typical agile does, you will find that it is in a various series of “Sprints”.
Within the meaning of Agile, you will find more refined approaches. The term “Scrum” is one of one of these approaches and it has its own set of methodologies, too.
Whatever the case is, this Agile method involves in working through the incremental and iterative cycles. The best way to understanding is to take a look at this in contrast with how the “Waterfall” method is done.
The Waterfall Method
When it comes to product development, the waterfall method is the traditional approach to completing it. This is carried out sequentially, then becomes more rigid, not to mention becomes less effective.
Some benefits of the agile method are the faster release of the final product into the market, requiring incremental investments and being more collaborative. The less advantage side of this method is that it makes the stockholders nervous since the method itself is flexible in nature. It is also usually misunderstood.
How Agile Methodology Works
Seeing it in a practical design setting, like the product backlog. This possesses all the features that are going to be included in the final product. The features are all based on the needs of the user and then converted into some form of benefit. Every feature is then placed on an individual index card and then they are semantically structured, which is often based on the personas’ perspective at a certain way to achieve clarity and consistency.
For every card, being the designer you are expected to estimate how long this will take. You are also expected to make the estimate as well. No worries – you are only asked about the estimate. After your first sprint, you will get a better idea of how much time the tasks are going to take to complete. At a general perspective, every feature is given the size very much like the standard sizes of t-shirts such as S, M, L, XL, etc. The number of these sizes are going to be placed into the sprint.
In the “Project Backlog” section, you will also see the other “buckets” like the current sprint, blocked, in a review, etc. This is posted on a Kanban wall, which the Japanese word literally translates to “signboard”. It is a visual way of putting up the index cards on the wall in order to get a better picture of all the features needed.