Blog


Agile Project Management vs. PMBOK® Guide – Overview – Exec. Summary

However, I would argue Agile methodologies do define a different framework and philosophical approach for managing projects that is currently not embraced in the PMBOK® Guide. The PMBOK® Guide currently defines a very formal, prescriptive – (or “Push approach”) – for managing projects. Agile, on the other hand, dictates using a far less formal approach – (or “Pull Approach.”) We will discover requirements in an iterative way, and let them emerge; we will let the team choose as they move through the project what documentation is needed, …
Read More…


Agile vs. PMBOK® Guide – Parts 2 & 3 – APM Criticism of Waterfall;Defense of PMBOK® Guide

2)      APM’s Criticism of Waterfall, and  3)      Defending the PMBOK® Guide.   Waterfall Method Let’s take a step back, and describe how software projects were often done in the past with the waterfall method, and contrast this with the much …
Read More…


Agile vs. PMBOK® Guide – Part 4 – Other Misconceptions About the PMBOK® Guide

One of the most important parts of all Agile Project Management methodologies is the approach taken for managing the project team, and the collaboration between all key stakeholders – (the product owner, the project manager, the project team, and also the customer) – at all times in the project. … For APM, in their view of traditional project management, the project manager takes on more of a directing role, and prescribes roles and responsibilities and tasks for team members to carry out. However, actually, PMI’s vision is that as project managers we wear a lot of different hats.
Read More…


Agile vs. PMBOK® Guide – Part 5 – True Incompatibilities

For PMI, the WBS is the heart of all planning processes, and will virtually drive all other types of planning such as scheduling, budgeting, planning for quality, risk identification, and planning for procurements. The lowest, most detailed level of the WBS is the “work-package” level. The WBS is fundamentally about deliverables and engineering requirements, and therefore later, the estimates for schedule durations and cost estimates of activities are largely driven by the technical products. In the traditional/PMI approach different teams are responsible for the different views of requirements.

With the APM approach, we would not focus on a WBS per se, but on an FBS (Feature Breakdown Structure) instead. Also, in Agile, the entire team collaborates throughout each iteration with the detailed breakdown of the features and stories: a customer focus is maintained.

Read More…


Agile vs. PMBOK® Guide – Part 6 – How Will Version 5 of PMBOK® Guide Address Agile?

6) How Will Version Five of the PMBOK® Guide Address Agile? PMI has indicated that the first draft of version 5 of the PMBOK® Guide will be released on the pmi.org website on February 17, 2012. Project managers and PMPs …
Read More…


Agile vs. PMBOK® Guide – Part 7 – Conclusion – What Approach Is Best In What Situation?

Conclusion – What Framework is Best for What Situation?  So, if we accept that there are two basic and different philosophical approaches to managing projects being defined: (1) the prescriptive or “push approach” of the PMBOK® Guide, and (2) the …
Read More…


Mapping the RDS to the PMBOK Guide

Here is a table that maps the tasks in the most recent version of the RDS to processes in version four of the PMBOK Guide. RDS Domain RDS Tasks PMBOK Processes/Tools Comments Initiating Task 1: Perform project assessment based upon …
Read More…