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.

Big Picture

explorer build conveyer delivery reward
big picture
xxx xxx xxx xxx xxx xxx

Agile Focus

The Agile Focus are the key milestones or focus parts that form the shape of the framework. These are guiding deliverables to achieve collaboration and alignment. This is a key principle and without these components then focus on what to achieve may be seriously compromised towards the Agile Roadmap

Agile Frameworks take a customer centric view towards agility. Our focus is on the customer needs and how the customer can benefit from what is being delivered by the power teams. Each power team is aligned towards the business need of the customer. The requirements are focused not just on how? but more importantly why? and this is driven by the business case.

Delivering the right requirements aligned to a clear business strategy is the enterprise goal. Alignment is driven from the customer through to the business and into delivery and then back to the customer.

One of the main goals for Agile frameworks is top-down alignment of the organisation strategies that drive the epic level capabilities for an organisation. Each deliverable strategy is defined at theme level, and each epic is broken down into various epics. Each theme are what portfolios align too, and each epic is how delivery teams align themselves to the strategy.

The Business Vision is what the organisation wishes to achieve in a single increment of delivery. The Vision is defined at theme level and the goals are defined at epic level detail. All power teams align themselves to this goal, and is the focus for each of the sprints or timeboxes.

Objective and Key Results - OKR are a quanifiable method to measure goals and success criteria for deliveribles. Defining and measuring OKRs allow more transparency to achieve goals for a team. The metrics defined allow an organisation to measure their success by aligning the strategy to the delivery. Motivating teams to achieve goals and create thresholds and achieve strategic goals offers direction and purpose to meet deliverables.

OKRs from an Agile perspective is implemented by the use of Kanban boards this aids in metrics being transparent to the team, to look at items in progress and metrics achieved and realisation of the value benefit of delivery.

A healthy, breathing Product Backlog is vital for successful Agile delivery. Its is a pre-requisite. By defining the requirements and using the principles of prioritisation to provide the business the right value at the right time is paramount. The backlog is not a wish-list but a vehicle for the team to delivery the business strategy through the vision of the organisation.

Delivery is a key focus for agile teams, to deliver in a fixed time period, at a fixed cost and never compromise quality is the mindset for delivery - only scope of requirements are compromised.

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 - two should be selected as best fit and a hybrid approach can be adopted.

Build 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.