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.

Today’s post on 2.14 Product Release is the second of 7 processes in the Close process group.

Product releases are sets of product functionality developed over the course of multiple iterations.   Releases may be defined as:

1. Internal–releases for projects which are for services or results that are to be used within the company
2. Incremental–releases for projects which are for products that are to be used by customers, but which are intended to be followed by further releases
3. Final–release for projects which are for products that are to be used by customers and/or end users

The next post covers 4.11 Team Evaluations.

Filed under: Uncategorized |