Setting Agile-Centric Release Criteria

room: Crystal C — time: Thursday 09:00-09:45
Level: Practicing

A huge quality-centered activity in Agile teams is defining “done-ness” as it relates to end of iteration or sprint deliverables. How we frame our team work goals, and measure their outcomes, plays an immense part in determining overall product quality and customer satisfaction. In this session, we examine the 4 levels of Done-ness when it comes to Agile Release Criteria:

  1. Team Craftsmanship Patterns
  2. Features – Complete
  3. Iteration – Complete
  4. Release – Ready

and share examples and stories of how Product Owners should interact with their teams.

Process/Mechanics

Comments In a 45 minute format, this is simply a Talk. A much preferred format would be a 90 minute Workshop session, where we get the chance to discuss and “practice” writing criteria at each of the “levels” I mention. We would do this from the context of group breakouts and driving what the groups feel are the most compelling criteria in their own experiences.

Slightly Extended Overview

A huge quality-centered activity in Agile teams is defining “done-ness” as it relates to end of iteration or sprint deliverables. Most agile teams don’t focus on complex criteria rather they look to deliver features or stories to a minimal set of acceptance criteria or tests.

This practice leads to incomplete and lower quality deliverables, which is unfortunate because it’s so easy to correct. I argue that Agile Product Owners are in a unique and powerful position to help guide their agile teams towards more complete and valuable work simply by defining a richer, more complete set of done-ness or iteration exit criteria.

In this session, Bob Galen will explore the 4 levels of Done-ness when it comes to Agile Release Criteria: 1. Team Craftsmanship Patterns 2. Features – Complete 3. Iteration – Complete 4. Release – Ready

and share examples of each. Beyond that, we’ll also explore patterns where Product Owners can exercise their collaborative skills in influencing their teams (developers, fellow testers, customers, etc.) towards delivering more complete & valuable work.

Learning outcomes
  • Introduce the basics of any release centered criteria—heuristics or characteristics of solid release criteria.
  • The 3 primary components of agile team work products—engineer work craft patterns, feature complete, and iteration complete and examples of relevant done-ness criteria for each.
  • The importance of aligning overall Release Criteria to drive team deliverables, system integration & testing, and assure value-drive releases.
Featured participants
Primary target persona
Reviews

No reviews

Subscribe to an RSS feed of reviews of this proposal Syndicate content