The document describes the lifecycle of a story in agile software development. It involves progressive elaboration of stories and features through story mapping, product backlog grooming, release planning, sprint grooming, sprint planning, development, and sprint demos. At each stage, more details are added to stories and features to prepare them for development and delivery. A variety of roles collaborate at different stages to further define requirements, dependencies, tasks and acceptance criteria.

1. TSavvy
STORY LIFECYCLE
PROGRESSIVE ELABORATION

2. TSavvy
LIFECYCLE OF A STORY
Feature Story
Mapping
Product Backlog
Grooming
Release Planning
Sprint GroomingSprint Planning
Development
Sprint Demo
Progressive
Elaboration: building out
the detail needed to
deliver based on what is
known at the time.
Features and Stories
are both being
elaborated

3. TSavvy
LIFECYCLE OF A STORY
Required input: Feature
Story Mapping
•Input: Feature
•Output:
•Story with title, description,
user and context;
•further elaboration of the
Feature
•Participants: PM, PO, Tech
Leaders, Team
Product Backlog Grooming
Input: Feature/Mapped Stories with
better description, acceptance
criteria
•Output: Split stories, business and
technical dependencies. Better
detail in description and ACs
Participants: PO, Tech Leaders,
Team (Arch and PM as needed)
Release Planning
Input: Features, Groomed stories
(context, dependencies)
•Output: Rough sizing on Features,
sense of story timing based on
dependencies and value. What is
the priority to support release
goals?
•Participants: PO, Tech Leaders,
Team (Arch and PM as needed)
Story Title:
Description:
Acceptance Criteria:
Priority: Size: L
Tasks:
Dependencies:
Story Title:
Description:
Acceptance Criteria:
Priority: Size:
Tasks:
Dependencies:
Feature Title:
Description:
Acceptance Criteria:
Value: Size:
Dependencies:
DoD:
Progressive Elaboration:
Features and Stories are
both being elaborated –
especially prior to sprint
grooming and planning

4. TSavvy
LIFECYCLE OF A STORY
Story Mapping
• Input: Feature
• Output:
• Story with title, description, user
and context;
• further elaboration of the
Feature
• Participants: PM, PO, Tech
Leaders, Team
Product Backlog Grooming
• Input: Feature/Mapped Stories
with better description, acceptance
criteria
• Output: Split stories, business and
technical dependencies. Better detail in
description and ACs
• Participants: PO, Tech Leaders, Team
(Arch and PM as needed)
Release Planning
• Input: Features, Groomed stories (context, dependencies)
• Output: Rough sizing on Features, sense of timing based on
dependencies and value. What is the priority for the release
• Participants: PO, Tech Leaders, Team (Arch and PM as
needed)
Sprint Grooming
•Input: Features, Groomed,
planned stories
•Output: further elaboration on
stories need for THIS sprint,
dependencies, initial subtasks
Sprint Planning
•Input: Groomed stories
•Refined Tasks, points for story
•Output: Sprint Commitment
•Participants: PO, Team, technical
lead
Development
Sprint Demo
Story Title:
Description:
Acceptance Criteria:
Priority: Size: L
Tasks:
Dependencies:
Story Title:
Description:
Acceptance Criteria:
Priority: Size: 5
Tasks:
Dependencies:
Stories are further elaborated,
incorporating new information,
dependencies and context added
for THIS sprint
High team participation:
making sure they have
what they need to begin
delivery.

5. TSavvy
LIFECYCLE OF A STORY
Story Mapping
• Input: Feature
• Output:
• Story with title, description, user
and context;
• further elaboration of the
Feature
• Participants: PM, PO, Tech
Leaders, Team
Product Backlog Grooming
• Input: Feature/Mapped Stories
with better description, acceptance
criteria
• Output: Split stories, business and
technical dependencies. Better detail in
description and ACs
• Participants: PO, Tech Leaders, Team
(Arch and PM as needed)
Release Planning
• Input: Features, Groomed stories (context, dependencies)
• Output: Rough sizing on Features, sense of timing based on
dependencies and value. What is the priority for the release
• Participants: PO, Tech Leaders, Team (Arch and PM as
needed)
Sprint Grooming
•Input: Features, Groomed,
planned stories
•Output: further elaboration on
stories need for THIS sprint,
dependencies, initial subtasks
(team)
•Participants: PO, Team, technical
lead
Sprint Planning
•Input: Groomed stories
•Refined Tasks, points for story
•Output: Sprint Commitment
•Participants: PO, Team, technical
lead
Development
•New tasks added
•Track Progress towards AC, DoD,
story completion
•Participants: PO, Team
Sprint Demo
•Demonstrate story, gather
feedback
•Output: input into further stories
and features
•Participants: PO, Team, Technical
Leadership, PM opt.
Note that the PO is available for
discussion during the development
and mini-demos may occur
throughout development
Story Title:
Description:
Acceptance Criteria:
Priority: Size: 5
Tasks:
Dependencies: