UP TO DATE NEWS YOU NEED
17 Nov 2016
Agile project management has been created as a solution for the often unpredictable, time-consuming and complex nature of software development projects, giving developers a way not only of organising themselves but of keeping stakeholders in the loop. In this article, we will look at some of the main advantages, as well as provide a brief summary of how to use agile project management correctly.
Main advantages of agile
- High quality - ultimately agile project management comes down to producing a higher quality product, and this is achieved by everything that happens along the way. Requirements are clearly defined, daily testing is carried out as part of the development process, and a product is not labelled as 'done' until it has been fully developed, then tested, then integrated.
- Human resources - agile project management affords teams a more streamlined way of working which means that they often need less management and can be kept to smaller groups - 5-10 people in some cases. Team structures can be customised according to the particular project, and team members are empowered to make decisions on their own.
- Customer satisfaction - another end goal is the higher level of customer satisfaction that agile project management can bring. Customers and stakeholders are kept updated throughout the project, meaning they are more engaged. Working functionality can be demonstrated on an ongoing basis, and products can be brought to market quicker.
How to use agile
There are three main project management processes that are commonly used by agile - but they are often used more frequently than in normal project management. They are:
Sprint - this is the quick defining of a deliverable, including what can be delivered and an end date. The nature of the deliverable and the time frame are subject to change.
Short daily meetings - keep all stakeholders involved with a brief daily update on what has been achieved in a day, including what will be done the next day and any issues that have arisen.
Review meetings - the end of each sprint is marked by review meetings which cover what has been achieved, any modifications needed, and how they will be implemented.