Click to the right of the image above for more information
Note that Traditional and Agile etc., method
(correct process application) starts at the bottom of the ladder.
From the previous slide: Can you spot the Configuration Management process at Capability Maturity Level 2?
Now look for Project Planning (PP) and Project Monitoring and Control (PMC) at Level 2.
This lies at the heart of the PMBOK Dashboard found on the next page!
These processes are also the essence of the Edward W. Demings Plan, Do, Check and Act cycle
and his "red bead experiment" leading to his 14 Observations for Management.
The new PMBOK Dashboard (released September 2017) is a detailed "how to" checklist
to achieve Capability Maturity Level 2!
The new PMBOK dashboard being fully Agile compliant
can be used to check correct project implementation of all the project management
(and other) methods mentioned below.
PMWay understands that Project Management Process application lies in a continuum from
Traditional (IRON TRIANGLE) on the right,
moving along to Agile (SCOPE TRIANGLE) on the left.
The concept of DDUF (Detailed Documentation Up Front), (Enough) EDUF and (Little to None) NDUF can help to explain this:
(I.e. click here to to the Agile Manifesto and hover you mouse over the manifesto image to understand this)
As PMWay is essentially the backbone for Masters Dissertation research about Traditional, Agile and Process; the model here explains this research and approach.
To better undertake this research PMWay has investigated many project methods (standards / frameworks) and approaches including, but not limited to:
SCOPE TRIANGLE--- XP, SCRUM, DSDM(AgilePM), PRINCE2 Agile, PRINCE2 and PMBOK ---IRON TRIANGLE
The Capability Maturity Model, ITIL, Cobit, CMII etc., all support correct governance for process use of each towards the goal of improved excellence.
I.e. Governance - from the Latin gubernare: means "to take the reins" (of a cart with horse or from the saddle) and to steer these for safety.
While agility and tailoring is desired in all project types, a balance needs to exist between flexibility and stability for agility.
Agile, for example, says that true agility is the ability to balance flexibility with stability.
Agile is also being adaptive to change, being flexible, being able to cope with change.
While the Agile Manifesto clearly states value of people over process, the SCRUM method for example
has 19 clearly defined processes with Inputs, Tools and Outputs.
These, if correctly followed, must ensure PP and PMC.
Let PMWay quickly explain how the above works from a PMBOK dashboard
Maturity Level 2+ perspective, using the image below.
Remember that Project Management Process (Project Planning [PP in the Capability Maturity Model]) and Project Monitoring and Control [PMC] and Configuration Management [CM] to name a few of the Capability Maturity processes) in system engineering aims to move a business or system baseline forward, under control, towards next stable baseline.
Requirements Management (REQM), Verification (VER), Validation (VAL) and others are all processes
from the Capability Maturity Level 2 and 3 Process, Engineering, Project and Service Categories.
Bi-directional traceability is a specific practice of REQM.
I.e. REQM - Specific Practice (SP) 1.4 "Maintain Bidirectional Traceability of Requirements"
facilitates track and trace to ensure that requirements are installed correctly and that these serve their intended purpose (to realize value).
Agile (PRINCE2 Agile, DSDM
etc.) stands best
chance of success if the Agile team operates as an Empowered Workgroup.
I.e. from the perspective of the People Capability Maturity Model as found at Level 4.
More on this within PMWay.