In the last episode (e.g., Part 3 of 9) of this series, I introduced the importance of the Agile and CM mindset. One of the key elements in
CIB involves an Agile and CM mindset change to think more continuously. For Continuous Integration and Build to work effectively it is also important to ensure we are breaking down the work into bite-size stories and/or tasks to ensure we can have a potentially shippable increment. Let’s examine this in more detail.
In order to do continuous integration, you need to have the work broken-down into a size of work where you can integrate and build frequently. The ability to specify the right ‘‘bite-size’’ level of story represents change that allow for granular and frequent code changes. This implies that the Agile team has the skills to understand the stories well enough in order to effectively break them down into small and consumable chunks. This allows the team to make codes changes frequently and incrementally.
But what are some techniques that help you break down work into bite-size stories? Here are a few ideas:
• Phrase your stories following the Canonical form. A canonical form for a story is expressed as "As a
I want to a so that ". This allows work to be segmented into actor, action, and benefit which helps in breaking down the work.
• Utilize the INVEST approach which stands for making a story Independent, Negotiable, Valuable, Estimable, Small, and Testable (established by Bill Wake). This approach helps us split larger stories or work into smaller bite-sized stories. Here are more details:
- I - Independent can stand on its own and could be demo’able
- N - Negotiable indicates that stories are negotiable and can be adjusted
- V- Valuable to the users and customer
- E- Estimable so that the stories can be sized
- S – Small enough to be bite-sized
- T – Testable so they can be verified and validated to work as written.
• Utilize the Use Case method that helps you break down work into functional steps. Each step should produce a piece of functionality. By using this approach, it provides you a basis for reviewing and determining the value of the functionality from each use case step in the flow. This then allows you to establish a more bite-sized approach to the work using a value and/or priority approach.
As you move to Continuous Integration and Build, your team must have the skills to chunk out the work into bite-sized pieces, in this case into stories that can be done within half the size of a sprint. This makes continuous integration and build meaningful and allows for more frequent merging and building of the work. Stay tuned for the next episode where we will focus on the Right-sizing your Branching and what this means in a Continuous Integration and Build process.
Note: If you started with this entry (Part 4), consider reading the first 3 earlier blog entries in this series.