This document discusses how to enter different issue types in an agile project including Epics, Stories, Sub-Tasks, Bugs, and Spikes. Epics represent large initiatives that can be decomposed into Stories. Stories are user-focused descriptions of functionality that can be estimated and assigned to a sprint. Sub-tasks break down the work needed for a Story. Bugs track issues found during development. Spikes are used for research before determining if a Story is viable.

1. How, when & why to enter Issues

2. • EPICS
◦ TYPES
◦ DECOMPOSITION
• STORY
◦ TYPES
◦ TEMPLATE EXAMPLES
◦ STORY EXAMPLES
• SUB-TASKS
• BUGS
• SPIKES
• QUESTIONS

3. • Objective that awaits decomposition
• Typically customer facing initiatives
• Summarizes certain business goals
oRelates only to size, not importance
oNot usually assigned to a Sprint or team member
SPRINT EPIC
oA large user story that cannot be developed and tested
within 3 - 5 days

4. Business Requirements
Epic Epic Epic Epic
Sprint-Epic
Sub-Epic
Arch. Epic

5. Business Requirements
Epic Epic Epic Epic
Sprint-Epic
Sub-Epic
Arch. Epic

6. Business Requirements
Epic Epic Epic Epic
Sprint-Epic
Sub-Epic
Arch. Epic

7. • Decomposed units of work
from the Epic
Epic

8. 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

9. 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.

10. • 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

11. • “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

12. Epic
Spike Story
10-Hours
Story
Sub-Task
Sub-Task
Sub-Task
Test Task
Test Task
• 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

13. Epic
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

14. Epic
Spike Story
10-Hours
Story
Sub-Task
Sub-Task
Sub-Task
Test Task
Test Task
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

15.  EPICS
TYPES
DECOMPOSITION
 STORY
TYPES
TEMPLATE EXAMPLES
STORY EXAMPLES
 SUB-TASKS
 BUGS
 SPIKES