Building and Use – Agile
Short Tip: The stage of maturing and developing the solution, as well as delivering the product to users.
What is it?
It is the stage of maturing and developing the solution, as well as its use by users. The goal is to build the product as quickly as possible and carry out partial releases that add value to users and allow testing product hypotheses.
The building stage is inherent in any framework or method. With agile projects, however, it is cyclical, i.e., it occurs multiple times. This approach allows testing the product – even if partially – with users and collecting their feedback (inspection). This procedure allows corrections of course (adaptation) in the product, which is one of the model’s advantages.
How to use it?
The building stage is predominantly based on the Scrum Guide, with the following observations:
- It consists of two phases, the first being Maturing, which is necessary for the solution’s initial detailing, and Sprints, where the development cycles are executed;
- During the Sprints phase, changes (including, removing or changing stories) are common. It is advisable to make these updates in the Story Map and in the Roadmap if the team considers that they can generate value to the building process or to the communication with stakeholders;
- If the team identifies changes that can jeopardize the value generated by the chosen solution, then it should run a Relab, i.e., return to the laboratory of ideas in the Conception stage to discuss new alternatives;
- Each Sprint, when the Product Owner indicates that an increment must be released, specific delivery actions must be taken: DevOps for IT products, release communication and user feedback collection;
- The Developers monitor the Sprint’s evolution through Sprint Burndown, and the Product Owner follows up the product’s evolution or the next release through Product Burnup;
- Product information is consolidated into both the program (set of related products) and the portfolio (set of programs) for the monitoring of value metrics and alignment.