agile issue types and decomposition
TRANSCRIPT
AGILE ISSUE TYPE & DECOMPOSITION
How, when & why to enter Issues
• EPICS◦ TYPES◦ DECOMPOSITION
• STORY◦ TYPES◦ TEMPLATE EXAMPLES◦ STORY EXAMPLES
• SUB-TASKS• BUGS• SPIKES• QUESTIONS
AGENDA
EPIC • Objective that awaits decomposition
• Typically customer facing initiatives
• Summarizes certain business goalsoRelates only to size, not importance
oNot usually assigned to a Sprint or team member
SPRINT EPICoA large user story that cannot be developed and tested
within 3 - 5 days
Business Requirements
Epic Epic Epic Epic
Sprint-Epic
Sub-Epic
Arch. Epic
EPIC
Business Requirements
Epic Epic Epic Epic
Sprint-Epic
Sub-Epic
Arch. Epic
EPIC
Business Requirements
Epic Epic Epic Epic
Sprint-Epic
Sub-Epic
Arch. Epic
EPIC
STORY • Decomposed units of work
from the Epic
Epic
STORY Epic
Story Story Bug• Decomposed units of work from the Epic• Stated as a sentence or two of
plain English• Expressed from the user’s point
of view• Describes a unit of desired
functionality• Can be worked by multiple
developers / testers
1. TRADITIONAL• "As a <role>, I want <goal/desire> so that <benefit>“• As an admin I want to edit a scheme so that it matches the Sprint
2. “SO THAT" CLAUSE• "As a <role>, I want <goal/desire>“• As a non-administrative user, I want to modify my own schedule.
3. "HUNTING THE VALUE"• "In order to <receive benefit> as a <role>, I want <goal/desire>“• In order to view recent edits, the logged-in user is prompted to save.
4. FIVE W’S• "As <who> <when> <where>, I <what> because <why>.“• As a user closing the application, I want to be prompted to save anything that
has changed since the last save so that I can preserve useful work and discard erroneous work.
5. FUNCTIONALITY• "As a <role>, I can <action with system> so that <external benefit>”• As a logged-in user, I want to save my filter so that I can receive emails of jobs
that match my filtered options.
STORY
SUB-TASKS
• Tasks needed to fulfill the Story acceptance criteria
• Estimated in hours
• 4-6 hours for development
• Testing hours could be higher
Epic
Story
Sub-Task
Sub-Task
Tech. Task
Test Task
Story
Sub-Task
Sub-Task
Sub-Task
Test Task
Test Task
Bug
Sub-Task
Sub-Task
Test Task
BUG
• “Groomed,” Estimated & Planned• Sub-Tasks estimated in hours• 4-6 hours for development• Test cases re-used (updated as
needed)• Traceability to original story or
Epic
Epic
Story
Bug
Sub-Task
Sub-Task
Sub-Task
Test Task
Bug
Sub-Task
Sub-Task
Test Task
Open BUG if:• Development is complete• Testing finds undocumented issue
• Issue fix > 2-hrs.• Demo issues surface
Epic
Spike Story
10-Hours
Story
Sub-Task
Sub-Task
Sub-Task
Test Task
Test Task
STORY - SPIKE• Used to analyze or answer a
question• Yes – continue with story• No – save analysis for future
• Training activities needed to support a story
• Time-boxed in hours
• Typically no story points given
STORY - SPIKEEpic
Spike Story
10-Hours
Story
Sub-Task
Sub-Task
Sub-Task
Test Task
Test Task
Yes
• Used to analyze or answer a question• Yes – continue with story• No – save analysis for future
• Training activities needed to support a story
• Time-boxed in hours
• Typically no story points given
Epic
Spike Story
10-Hours
Story
Sub-Task
Sub-Task
Sub-Task
Test Task
Test Task
STORY - SPIKE
No
Close Story
• Used to analyze or answer a question• Yes – continue with story• No – save analysis for future
• Training activities needed to support a story
• Time-boxed in hours
• Estimated in story points
EPICSTYPESDECOMPOSITION
STORYTYPESTEMPLATE EXAMPLESSTORY EXAMPLES
SUB-TASKS BUGS SPIKES
REVIEW
QUESTIONS