Agile Project Management
What is Agile PM?
According to apm.org ‘Agile project management is an approach based on delivering requirements iteratively and incrementally throughout the project life cycle. At the core of agile is the requirement to exhibit central values and behaviours of trust, flexibility, empowerment and collaboration.’ It is a project management approach where the focus is on on-time delivery without compromising the quality. To do that Features of the project can be varied. It is very much like Lean Startup, where the focus is on getting the product out in the market as quickly as possible by developing it iteratively using consumer feedback and adding features with time.
I knew much of the functions before, but I wasn’t aware of the methodology. Agile PM gives a logical and systematic approach to any project that minimizes the risk of failure. It runs on MOSCOW principle.
Mo- Must Have
It means the features and functions the project must have. They are absolutely necessary and cannot be avoided at any cost. They make around 60% of the total project
S- Should Have
It means the features that are not absolutely necessary but a project should have them. is recommended that they should not be avoided in a successful project. They are around 20% of the project.
Co- Could Have
It means the features and functions a project could have if there is time. They are not necessary and are an additional benefit. If they are achieved they make a perfect project. They are around 20% of the project
W- won’t have this time.
It means that the features which are not feasible at this time but could be done in future iterations.
MOSCOW is the heart of Agile PM. Other than this the main principles that make agile PM so successful and efficient are:-
Focus on the business need. – Never wander off from a brief and always check if we are working towards a goal
Deliver on time – It is essential in this methodology to always deliver on time, features can be changed to do this.
Collaborate- work in a team with others with clear goal and communication
Never compromise quality- Although features can be changed but the quality of the product/service should be good enough
Build incrementally from firm foundations- Prepare a base and then build upon it in iterations using Build-Measure-learn cycle
Develop iteratively- Develop the features and product in steps after testing and learning
Communicate continuously and clearly- Communication should be done everyday and clearly. Daily stand ups and Team Board are part of this.
Demonstrate control – Demonstrate control by showing everyone who is working the development and stage in front.
Association for Project Management, ‘What is Agile Project Management?’, apm.org, Accessed on 27/04/2019, https://www.apm.org.uk/resources/find-a-resource/agile-project-management/