Setting Agile-Centric Release Criteria

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

He will then 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.

Facilitator Bio

Bob Galen is a software engineer by trade and a technical leader by experience. Currently his focus is Agile methods coaching, training, evangelism and speaking. He has a track record of effectiveness in leading diverse technical teams towards project success in an energized and humane fashion utilizing Agile and Traditional methods. Bob is a member of the Agile Alliance, a Certified Scrum Master and Scrum Product Owner, and an experienced XP Coach.

    Seminars