Critical Path in Complex Agile Projects
Syed Arifulla MBA, PMP, Prince2, Project Manager, United Kingdom
: Thanks, you are talking about agile manifesto which embraces change. And that in agile projects time and budget are fixed. This is a simple, basic agile concept.
The critical path I have described is the practical solution to actual delivery of large enterprise complex agile projects which will have multiple scrum teams with multiple agile projects running simultaneously and having dependencies on each other creating chaos for final end to end delivery.
Note: I never mentioned to fix scope, cost or time in this critical path.
For example: An end to end banking solution. There are 6 scrum teams.
Each scrum team is cross functional - front end, back end, webservcies, QAs, third party providers, integration etc. There will be several occasions when each scrum team is dependent on the other scrum team for various aspects. The solution above displays how such scenarios can be easily handled by the critical path concept in agile projects in every release, irrespective of time, budget and scope.