Managing work with JIRA epics Divide and conquer your development process with JIRA

1. Sync the moment
Managing work
with JIRA epics
Divide and conquer your development process with JIRA

2. Sync the moment
Problem
• How do you manage a huge pile of stories and epics
• As release manager you want to focus on the features in a release
• As developer you want to know what story is highest priority right
now
• As QA manager you want to know if agreed processes are being
followed

3. Sync the moment
Epic Kanban Board

4. Sync the moment
Epic workflow
• Any to Any workflow
• Epics are prepared in status ‘Preparation’
• Once that all I’s are dotted and all t’s crossed, epic gets in planned status
• Once that dev team is ready for more work, epic is moved into ‘in progress’
• Stories will appear on the dev work board
• Once that all stories are closed, epic moves to status ‘Resolved’ for final
validation

5. Sync the moment
Configuration
• Query
• category = "Exalate Product" AND issuetype = Epic AND "Epic Status" !=
done ORDER BY Rank ASC
• Category = “Exalate Product” allows to create a board over multiple projects
• Constraints on the ’in process’ statuses
• Priority based swim-lanes – pushes the high priority items up

6. Sync the moment
Dev work board

7. Sync the moment
Configuration
• The dev work board shows
• All epics and its stories
• All issues without epics
• Query (uses script runner)
• category = "Exalate Product" AND ( issueFunction in linkedIssuesOf("category = 'Exalate Product' and issuetype=epic AND status =
'in progress'") OR (issuetype = epic AND status = "In Progress" ) OR (fixVersion in unreleasedVersions() AND "Epic Link" is EMPTY) )
ORDER BY Rank ASC
• Epic based swimlanes
• Constraints on the ‘in process’ statusses
• Use bit-bucket – JIRA integration to auto transition issues