...
Why? Allows consistent reporting within and across teams. Timeboxing encourages refinement and avoids over-investing.
Examples:
Stories: New feature work. Written from the end-users perspective.
Tasks: Maintenance or non-code work.
Bugs/Defects: Error correction and handling.
Spikes: Investigatory efforts. Typically timeboxed to a couple hours or days at most.
Utilizing Start & End Dates
Start/end dates
How to define “start” - As scoped solidified
End as potential work done or released date
Creating Card Type Definitions & Upper Time Bounds
Common card type definitions
Define the smallest increment of work
Subtasks?
Add spike card
Story/New Feature
Task, no code or repeatable
KTLO task vs bug
Bugs
Internal vs external field or separate issue type
Investment / Capitalizable Concepts at Parent Level
Capitalizable flag at epic level
Any other investment type information you want to have
Tech debt, etc.
ULT-Work Categorization
Can be variable at parent level
Common definition and size for epics / initiatives
Goal of any parent is an org-wide definition
Jira Issue Workflows & Azure Devops Work Item States
...
Sub-tasks: Smallest component of work, always the child of a story, task, bug, or spike. Always timeboxed to under two days to encourage refinement and work understanding.
Potential Day to Day Work Item/Issue Workflows and Statuses to Consider:
New
Product Requirements
Ready for refinement
Refined - Ready for Dev
In Dev
Waiting for code review
Code Review
Waiting for QA
QA
Pre-Release
Done/Released
...