Sponsors

Microsoft

TechWell

We have 2248 guests and 4 members online

Home Blogs Featured Blogs CM for Agile Holistic view of Continuous Integration & Build (Bite-size Stories) – Part 4 of 9

Holistic view of Continuous Integration & Build (Bite-size Stories) – Part 4 of 9

 E-mail
Wednesday, 10 August 2011 08:14
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.
Note: consider reading Adapting Configuration Management for Agile Teams, consider by Mario E. Moreira Wiley Publishing, 2010 for more information on this topic.   




Posted: 2011-08-10 16:14:32Author:

Trackback(0)

Comments (1)add comment

feedSubscribe to this comment's feed

Kevin Dietz said:

Kevin Dietz
 ...
You mentioned merging ... in this context I assume you mean workspace merging, not branch merging. If you're using branches and want to merge changes between branches, combined with continuous integration, you might want to look at Timpani Software's MergeMagician solution, which is designed for these scenarios.

http://www.timpanisoftware.com

I'm anxious to read the next installment of your series, which sounds like will discuss branching and CI strategies in more detail.
 
September 15, 2011
Votes: +0

Write comment

You must be logged in to post a comment. Please register if you do not have an account yet.

busy