Mid-level Track Roadmap

Agile: feature grooming

This course explains feature grooming through one example: a one-sentence ticket asking to fetch a partner's logo from their website. It counts the decisions hidden in the finished code and separates grooming from estimation, planning, design review and status meetings. It applies a set of questions that starts with failure. It covers vertical slices, estimate disagreement, facilitating a session, and writing a groomed ticket with decisions, out-of-scope items, unchecked acceptance criteria and open questions that each have an owner.

What you'll learn

  • ✓Counting the decisions a one-sentence ticket hides
  • ✓Telling grooming apart from estimation, planning, design review and status
  • ✓Asking grooming questions, starting with what happens on failure
  • ✓Splitting features into vertical slices
  • ✓Facilitating a session and recording unknowns with owners and dates
  • ✓Writing a groomed ticket and a definition of ready
Free preview · Lesson 1 5 min read

Count the decisions

Grooming is easiest to understand backwards: look at finished code and count the decisions that had to be made before it could exist.

Read the full lesson free →

Curriculum

7 lessons
Type to start searching...