Critical Path in Agile Projects

12manage is hiring Management/MBA Students!

Critical Path Analysis > Forum Log in

Critical Path in Agile Projects
Syed Arifulla MBA, PMP, Prince2, SIG Leader
Recently critical paths are being identified and worked upon in agile projects. The main steps are:
  1. Form a network diagram of project initiation to delivery.
  2. Notice the dependencies of the activities in the project.
  3. Isolate these dependencies by mocking them till their delivery.
  4. Virtual mocking of the services, infrastructure, and applications. This is making it possible to isolate these dependencies and work to be carried out in parallel.
  5. Integration mode. The virtual components are replaced by the actual components and tested to see that the behavior is as expected.
  6. End to end testing.
  7. Final delivery.
I am looking forward to your reactions. Thank you.

Critical Path and Agility in Projects
Thieme, Member
OK, but critical path was invented to get a project's minimum duration and identify the tasks/work packages that - by no means - shall cause delays. That means that the projects scope is fixed, which is not the case in agile projects where time and budget are fixed. The agile manifesto states that embracing change is paramount to agility. Is critical path a concept that applies to that? I think not, but I'm open to discuss.

Critical Path in Complex Agile Projects
Syed Arifulla MBA, PMP, Prince2, SIG Leader
@Thieme: 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.



  Do you wish to study further? You can learn more from the summary, forum, discussions, lessons, courses, training, instructions, expert tips, best practices and education sources. Register.  

Special Interest Group Leader
Syed Arifulla MBA, PMP, Prince2
Project Manager

More on Critical Path Analysis
Best Practices

Expert Tips


About 12manage | Advertising | Link to us / Cite us | Privacy | Suggestions | Terms of Service
2018 12manage - The Executive Fast Track. V14.1 - Last updated: 22-6-2018. All names of their owners.