The phase model
Every project starts with Initiation and ends with Closure. Between them lies the development of the solution:
Initiation and Closure are always run in the traditional way from a project management point of view, even when the team uses agile tools in them.
Milestones frame each phase
A milestone stands at the start and at the end of each phase. Milestones are quality gates: before a milestone is reached, the responsible role decides on the outcomes and on how to proceed. At every phase release, the project sponsor releases the resources for the next phase. In the agile approach, the project can also require a release milestone for each release. See Milestones and decisions for the full list.The phases
Initiation
Study, solution variants, procurement analysis and the execution release.
Concept
Traditional: requirements, concepts, architecture and procurement.
Implementation
Traditional: build or configure, integrate, preliminary acceptance.
Deployment
Traditional: activate the solution and start operation.
Execution
Agile: iterations, increments and optional release milestones.
Closure
Hand-over, archiving and the final project evaluation.
In Collabase
Plan each HERMES phase as a parent task of a dedicated task type, for example Phase, with a start date and a due date. The outcomes of the phase become its subtasks. The Roadmap then shows the phases as bars on a timeline, with the outcomes indented below them, and highlights any subtask that falls outside its phase.1
Create a Phase task type
Go to Admin → Task Types and create a type named Phase. See Workflows for field rules.
2
Create one task per phase
In the project, create a Phase task for each phase of your approach, with its planned start date and due date.
3
Add the outcomes as subtasks
Open each phase and click + Add Subtask for every outcome the phase must produce.
4
Check the plan on the Roadmap
Open the Roadmap view and switch to Quarter to see the whole project.