Agile Project Management is a common practice in the Software Development and Telecommunications industries. It is a requirement for a PM position.
But!
There is no standard agile project management approach.
It varies from one company to the next.
However, I would like you to see my framework which describes an application of Agile Project Management.
This will increase your knowledge of the approach. It will help you to determine the most efficient method of implementing it.
What is Agile Project Management?
Let’s be honest. Scrum or Kanban by itself is not Agile Project Management.
Kanban and Scrum are independent and self-sufficient frameworks. You can use one of them to manage a project.
Agile Project Management is a method that combines plan-driven phases and agile phases in one project lifecycle.
Scrum is used for the main execution phase. To test and fix critical flaws, you can switch to Kanban at the end.
After the initial implementation is completed, you can return to the plan-driven approach to deploy the project and complete it.
Why mix Agile and Project Management?
Not all clients and companies are ready to embrace Agile. I mean, to the full extent.
Scrum and Kanban can also be used to satisfy the management, administrative, and bureaucratic needs of large organizations (in a proper sense of the term).
It is, however, a natural progression for Project Managers.
A PM should choose the best tools and techniques.
These frameworks are not complete without the Agile Manifesto or marketing buzz around Kanban and Scrum. Tools.
It is a great combination for projects that involve many uncertainties.
Sorry, there is no magic.
Agile Project Management Lifecycle
I have already described the life cycle of agile project management. You will see that there is no standard.
Break the project down into phases. You can use an Agile approach in each phase. Now, you have Agile Project Management.Prerequisites to Project Management with Scrum and Kanban
Agile Project Management requires only a few prerequisites.
These prerequisites must be respected by all stakeholders.
They must be able to understand their role as well as the PM approach in general.
1. Requirements can be met using User Stories
This is a simplification that you and all your stakeholders should master.
All requirements should be collected in User Stories. Create Acceptance Criteria. The project team should handle all the details.
You can collect requirements in any manner you like. You can then transform them into User Stories. It is also valid.
2. Iterations can be used as a unit of measurement
Scrum makes it possible to make an iteration a key UoM. Iterations are used to plan scope, time, and costs.
If you have to, Gantt Chart can still be used for visualization. Be aware that deadlines can change in increments, not in days. You should be ready to descope your project
OK, not you. All stakeholders and clients need to be prepared.
It is impossible to pack your project scope with all the “must haves”
It isn’t real.
Second, you didn’t work hard enough to get along your stakeholders.
Third, your backlog was not prioritized well enough.
There should be enough scope margin to allow for “agile” parts.
4. Be ready to switch frameworks and approaches within a single project
You must use the best tools and approaches to manage projects.
Scrum is all you need to do everything.
But, is this the most efficient?
Agile should not be a dogma. You can switch between approaches and complete the work if necessary.
You shouldn’t be focusing on company transformations.
You use the strengths and weaknesses of your current organization to get things done. You choose the path with less resistance.
However, it doesn’t mean you can’t learn from your mistakes and suggest improvements.
Stage 1: High-Level Project Management
Please note:
