|
|
|
|
|
The Agile Roadmap goes through the journey towards agility, its a plan that helps visualising the steps necessary
to allows the transitions in mindset and culture for seamless migration from waterfall.
|
|
Agile Roadmap
An agile roadmap is used to guide the organisation towards the delivery journey ahead - all teams will be committed to this, and it will provide clear clarity in the key milestones to be achieved, for teams that are moving from a waterfall mindset it is really important to not jump in to a framework without trying to understand how the framework will meet your business needs and what is the maturity and transition for such an adoption.
In terms of the journey the key stages are adopted to align to the Agile delivery. This is tabulated below:
Exploration Phase |
 |
Before an organisation embarks on an Agile journey it needs to gain a understanding for the underlying values of principle. This is important to get business, the teams to think as a collective and adopt the correct mindset to achieve the transition. Agile workshops are encouraged for 2-3 weeks. In parrallel there needs to be analysis done on the Agile frameworks that may suit the organisation - 2 should be selected as best fit and a hybrid appraoch can be adopted.
|
Build Phase |
 |
Once the framework is adopted - we then build teams and people around to focus on the adoption. Lead positions are created according to actors in the framework and they will then be used to build the necessary artifacts and transparency on the approach. The increments are planned and the delivery plan created by the business and the agile ceremonies are set up. 3-4 weeks.
|
Execution Phase |
 |
This is all about the time boxes or the sprints - to execute the implementation of the deliverables. This is characterised by having prioritisation for artifacts, inspection and adaptation for items. Based on the framework selected the 'doing' bit is focused here with a view of building part of an increment and quantifying what value that part brings. The objective is to mature within the sprints and achieve optimal velocity, it is anticipated 6 sprints achieves a constant velocity rate.
|
Conveyer Phase |
 |
Plan --> Build --> Test --> Deploy approach to achieve a 'conveyer' belt process for developed features. The object for this phase is repeatability and stability with a focus on quality, in the conveyer phase quality cannot be compromised.
|
Delivery Phase |
 |
The delivery phase is focused towards integration and deployment, post the Execution phase the integration steps begin to take shape. The development team coding is committed to a shared repository and code integration, automation and testing takes place, the objective for this phase is to achieve deployment, where there is no manual intervention from code being developed to the deployment phase.
|
Reward Phase |
 |
This phase focuses on an iterative end to end approach which constantly adds value to the product increment.
|
|
