What happens in Execution
- The project organization is set up, including the execution organization that develops the solution.
- Situation analyses are carried out, and the requirements from the study become prioritised initial solution requirements.
- If business processes or structures are affected, the organizational requirements are mandatory.
- If the solution is procured, the tender is carried out, the offers are evaluated, and the product or system is procured.
- Each iteration creates a further part of the solution, the increment. Requirements are refined, split and worked through in descending priority.
- Alongside the increments, the organization concept, the operating organization, tests, migration, integration and the deployment concept are developed step by step.
- Preliminary acceptance, deployment measures and the launch of operation are carried out per increment.
How Execution ends
If the project management plan requires it, a release decision is taken before each further release. The closure phase release decision is taken, and after the launch of operation and the acceptance of the last release, Execution ends and the execution organization is dissolved.In Collabase
- Keep the solution requirements in the Backlog and plan iterations as Sprints with story points and burndown.
- If releases need a formal release, model each release milestone as a task and route it through an approval. See Milestones and decisions.
- Link test runs to a milestone per release to see its aggregate pass rate.