Issue Flow and Sprint Planning Process
Epic Creation and Sizing
- Create Epics in Jira, linked to specific goals
- Epics should represent complete functional features
- Each epic should deliver independent business value
- Epics should be linked to specific goals
- Product Owner performs:
- T-shirt sizing of epics
- Priority setting
- Deadline alignment with related goals
T-shirt Sizing Reference Table
| Size | Hours Range | Complexity |
|---|---|---|
| XS | 1-4 | Very small, simple task |
| S | 4-8 | Small task, straightforward |
| M | 8-16 | Medium complexity |
| L | 16-32 | Large, complex task |
| XL | 32-80 | Very large, highly complex |
| XXL | 80+ | Major undertaking, needs breakdown |
Roadmap Planning
- Scrum Master creates initial roadmap based on:
- Epic T-shirt sizes
- Deadlines
- Team capacity
- Epic priorities
- Product Owner reviews and approves roadmap
User Story Development
- Developers create user stories for planned epics with Scrum Master guidance
- Issue Flow:
- Scrum Master reviews stories against issue criteria
- If approved, status changes to "Ready for Development" (assigned to Product Owner)
- Product Owner reviews for alignment with intended functionality
- Product Owner either:
- Returns with feedback
- Sets to "Selected for Development" and unassigns himself
Code Development
- Developers can pick up unassigned issues in "Selected for Development"
- After completion and code merge to development branch:
- Status changes to "Review"
- Tester can test from development branch
- After successful testing, completed issues are:
- Presented to Product Owner during sprint review (Friday)
- Released to master branch on Monday morning following successful review
Development Process
- Developers can pick up unassigned issues in "Selected for Development"
- After completion and code merge to development branch:
- Status changes to "Review"
- Tester can test from development branch
- After successful testing, completed issues are:
- Presented to Product Owner during sprint review (Friday)
- Released to master branch on Monday morning following successful review
Sprint Closure
- Scrum Master prepares sprint review proposal including:
- List of completed issues for review
- Overview of unfinished issues
- Recommendation per unfinished issue (keep or return to backlog)
- During sprint review (Friday):
- Team reviews unfinished issues
- Decision made per issue to either:
- Keep in sprint (if aligned with roadmap and capacity)
- Return to backlog
- Decisions are made in accordance with roadmap priorities