Critical Chain Method vs Agile Scrum

Critical Chain Method vs Agile Scrum

'Traditional vs Agile Project Management!'

It is always been the confusion between the Agile Project Management. APM Manifesto suggests that the use of processes should not be preferred and basic Tools & Techniques of PMBOK need not be used. Pmbok Project Management describes the tailoring of process for the project as Tallor!

Critical Chain Method of PMBOK is a critical tool to schedule the critical tasks on the critical path with buffers. APM may not use the CCM for the Scrum iterations, waves and releases and the concept of Slack, Pomodoro Technique and Kanban can be used for more reliable and effective bug-free deliverables.

  • CCM can be used for tasks of iteration and it would be more useful along with the Sprint Backlog & Product Backlog priorities for all the team members.
  • CCM provides the pictorial view of the tasks, iterations, waves and releases, especially, releases where the buffers can be used for more effective deliveries in releases.
  • It also lessens down the number of releases and waves for less carrying forward of the stories & usecases to next iterations.
  • CCM would be a useful tool to be Lean as much as possible by removing the waste from the Sprint & Product Backlogs.
  • CCM improves and corrects the estimation accuracy more and more reliable. Planning Poker or Wideband?Delphi usage for estimation with CCM would be a drastic improvement for schedule, cost and scope estimation.
  • Use of Function Point leads to more accurate size estimation of the project.
  • Execution of different components with Scrum improves the efficiency more and reliable.

Traditional Project Management with APM may be more useful with less failures! Chickens are still needed, specially for Big Solution Portfolios/Programs/Projects!


#pminstitute #agile #pmp #criticalthinking #strategicleadership #consulting #pmbok #projectmanagement #programmanagement #leadershipgoals

要查看或添加评论,请登录

Sakul Pranjal的更多文章

社区洞察