Categories
Rapid JAD Requirements Uncategorized

Bundling

Facebooktwittergoogle_plusredditpinterestlinkedinmail

By Erik Jul

Bundling is a tidy idea.  Consider the humble bundle of sticks.

Bundle of Sticks

Useful.

Or the Roman fasces, shown here on the reverse of a U.S. Mercury dime, or Winged Liberty Head, dime.

Fasces

Powerful.

What makes each bundle desirable?

  • Utility
  • Fitness for a purpose
  • Ease of use
  • Similarity or complementarity of components, or
  • Some other bundle-making attribute that ties the individual pieces together

When selecting from a backlog of functional requirements, product owners and developers must select and form a bundle for the next development sprint.

This may seem like–or it may be–and easy job.  More often than not, however, it is fraught with decisions, trade-offs, and compromises.

What makes a good bundle?  Something must tie them together.

  • They implement a coherent feature.
  • They trace to user stories or epics.
  • They build upon a prior bundle.
  • They are required for a subsequent bundle.
  • They match the velocity of the development team.
  • They can be implemented in the current environment.
  • The account for any technical debt from previous bundles.

Of course, any bundle is only as good as its constituent requirements, which must be clear, correct, complete, consistent, unambiguous, verifiable, traceable, and testable.  Rapid JAD techniques greatly assist these objectives.

Creating the right requirement bundle is the basis for a successful development sprint, and a good bundle starts with a strategically stocked product backlog selected from a bank of user stories or epics.

Executing these challenging business analysis and project management tasks can prevent a bundle from becoming a bungle.

What’s in your bundle?

 

 

Facebooktwittergoogle_plusredditpinterestlinkedinmail