Menu

Maturing – Hybrid Model

Short Tip: The stage of initial detailing of the solution.

What is it?

It is the stage of initial detailing of the solution within the “Building and Using” phase. The goal is to initially align the Development Team and carry out a high-level detailing of the solution, particularly regarding scope, time and costs.

By the end of the Maturing stage should have the technical, human and material conditions to execute the first Development Cycle.

Why use it?

Without this stage, part of the first Cycle’s time would be dedicated to designing some fundamental artifacts, such as the Product Backlog, in a disorganized manner.

Using a previous stage for the initial detailing allows the team to discuss the solution at a higher level, including an overview of the user’s journey and the detailing of the initial requirements

Since it is a model for mainly predictive products, this stage also provides the detailing of scope, time and costs that are usually required by the organization before starting the development.

How to use it?

The Initiative Leader, with the Development Team:

  • Prepares and holds the Kick-off meeting to align the work carried out in the Conception stage with the whole team;
  • Designs the product’s WBS with the product deliverables;
  • Details the Product Backlog based on the WBS deliverables;
    • Depending on the product’s characteristics, designing a Story Map first may be relevant to contextualize the deliverables from the viewpoint of the user’s journey;

The Initiative Leader, helped by the Development Team:

  • Designs a detailed schedule based on the activities defined in the high-level specification and on the logical dependence for the Product Backlog’s delivery;
  • Draws an overview of costs for the product’s delivery based on the activities detailed above;
  • Designs the supplementary Canvas (e.g., risk), according to the product’s characteristics;
  • Designs a Roadmap with a high-level schedule to be presented to the stakeholders;
  • Throughout the process, the Development Team initiates the technical preparations to make sure all resources and configurations are available for the first Cycle.

The steps above are not necessarily unidirectional or sequential. For example, when a new risk is identified, this may imply changes in the Roadmap and the Schedule.