Process Delivery

Each practice is presented as a set of process cards that contain the elements you need to build your process, including competencies, activities and artefacts. The cards are provided to help you build and use the process.

The card metaphor makes the process itself lightweight, agile and easy to use.  Displayed electronically or presented as physical cards they are easily manipulated to facilitate process adoption, project planning and to provide handy reference guidance to practitioners. 

We have two kinds of artefacts: alphas and betas.  Alphas are the most important things that all software projects have whether they exist in a described form or not.  For instance every software project has the following alphas: implemented system, backlog and risk.  The project may keep this knowledge tacit (in their heads) or report it.  Each Alpha can have a set of betas : A project alpha may have a project plan or an iteration plan.  A project risk may have a risk list.  A backlog may have a feature list and change list. 

The idea with alphas and betas is to have a precise way of discussing how much to document.  This allows us to be agile in a disciplined way.  We can separate the essentials from less essential things. The cards contain the essential information linked to all of these items.  For each card there is a 2-4 page guideline presenting the most essential information needed to be able to put the cards into practice.