Agile development is a trend in the IT industry that has become more and more popular in recent years, even though it has been around for some time. It is an alternative method to waterfall development, with the main difference being smaller, iterative cycles. However, there is a bit more to it than that – the agile development life cycle is different, which I’ll explain in this article.
The Agile Development Life Cycle Overview
This image outlines the agile development life cycle.
The process includes several areas:
In Progress Tasks
In Acceptance Tasks
Download this as a PDF file of the Agile Development Life Cycle.
What Is A Sprint?
The process that ties all of these stages together is the sprint. A sprint is a short release timeline – it’s a window of time that ends up with some features being released into a final version. These sprints are usually short – sometimes only a week, or up to four to six weeks. This depends on the company and the environment they are in. The work done each day is on certain items that are allocated to each sprint.
What Is The Agile Backlog And How Do Tasks Progress?
The project starts with what is known as a backlog. This is a list of “stories” or requirements/features for the project, which are prioritised by the users and stakeholders in the project. The backlog is simply a list of requests that have yet to be started.
Tasks progress by being assigned to the current sprint, which is based on prioritisation from the stakeholders. These requirements will be built into the next sprint. This moves the items from the Product Backlog into the Sprint Backlog.
Tasks move from the Sprint Backlog into In Progress when they are actually started by the project team. Requirements are gathered, programming is done, hardware is configured and installed, all of these activities are done depending on the requirement. They are usually done independently of other tasks.
How Does An Agile Task Get Completed?
Moving from the In Progress step to the In Acceptance step is next. This happens when the work has been done on the task, and is ready to be tested and accepted by the stakeholders. The criteria for this is decided at the start of the process – when the requirement is devised. Once it is In Acceptance, it needs to be taken to the relevant users or stakeholders for approval. Work can then commence on a different item while this is waiting.
Once an item has been accepted, it moves onto Completed. It is then able to be released into the current sprint, which happens at the end of the sprint period. Once it has been released, at the end of the sprint, feedback is provided back to the project team and the Product Backlog is reassessed. Tasks are often reprioritised and work can commence on the next sprint.
This process is known as the agile development life cycle. It allows for quicker response to changes and faster time to get a product released to the users.
Hopefully this has cleared up any questions you had on the agile development life cycle. Post your comments in the area below!