4squareviews

In John Stenbeck’s book “PMI-ACP and Certified Scrum Professional Exam Prep and Desk Reference”, he creates an “agile project management process grid” which describes 87 processes used in agile project management.   These processes are divided into five process groups (Initiate, Plan, Iterate, Control, and Close), which are analogous to the five process groups in traditional project management, and seven knowledge areas which can be mapped, more or less, onto the ten knowledge areas in traditional project management.

The previous posts have covered the “Initiate”, “Plan”, “Iterate”, and “Control” process group of an agile project.   Tomorrow I start on the “Control” process group, but I first want to define what I mean by that term of “process group”.   Why do I use this instead of the word “phase”?    Phase implies a sequence that goes more or less from one set of processes to another.   In reality, after the initiate and plan process groups, an agile project actually shuttles back and forth between the “iterate” and “control” process groups.   However, a project always ends with the “Close” process group.

Here are the processes in the “Close” process group:

1.10  Deliverables Acceptance

2.14  Product Release

4.14 Team Evaluations

4.15 Performance Incentives

4.16 Self assessment

6.10 Retrospectives

7.7  Process Tailoring

Out of the 87 processes in agile project management, the Close process group contains the above 7, making it the process group with the fewest amount of processes.   It is nonetheless as vital a process group as the others, and I will start with the first process in the group, 1.10 Deliverables Acceptance, in the next post.

Filed under: Uncategorized |