back to Practices
Build
The Build Process
Turn your solution into deliverable and measurable features.
Length
1 Week (repeating)
Participants
Core team, and occasionally the primary stakeholder
Why Do It
- You want to always “build the right thing”
- You want to minimize risk during delivery
- You want to maximize stakeholder engagement
When To Do It
- After you’ve aligned on your priority solution to implement
- Repeated cycle for the duration of the delivery process.
How To Do It
- User Story Writing
- Lean Experiments
- Iteration Planning Meetings
- Three Column Retrospective
- Demos
Introduction
Building is the final step of bringing value to your users. It takes an agreed-upon feature for the top prioritized solution to create a living backlog of work.
Why a living backlog? While research may seem complete during the Discover and Frame phases, it has only begun. Getting working code in front of your users will enable you to pivot or persevere based on their reactions and adjust your outcome-oriented roadmap accordingly.
User Story Writing
- Create a hypothesis around how your next features will benefit your users
- Determine measurements to validate the impact
- Frame user stories around those emotions and measurements
Lean Experiments
- Validate your latest work with your users
- Document their reactions
- Compare reactions to a hypothesis in user story
Iteration Planning Meetings
- Determine the highest priority value to deliver
- Align effort and complexities with the core team
- Prioritize your product backlog
Retrospective
- Surface feelings and tensions
- Align on improvements heading into the new week
- Action those improvements to core team members to achieve by the following Retrospective
Demos
- Share work internally with stakeholders
- Get stakeholder feedback
- Get feedback from subject matter experts external to the core team
- Iterate the outcome-oriented roadmap based on feedback