2. Anatomy of a JIRA Feature
How the JIRA development team uses Atlassian tools
Dylan Etkin, JIRA Architect, Atlassian
2
2
3. Phases of a Feature
• Idea & high-level planning
• Confluence pages, page comments and blogs
• Release & iteration planning
• JIRA & GreenHopper epicʼs & stories
• Development work & QA
• JIRA & GreenHopper issues & tasks
• Bamboo
3
3
4. Idea & high-level planning
• Confluence
• Specifications as Confluence pages
• Blogs for open opinion gathering
• Comments, comments, comments
• Example
• JQL, founder idea
4
4
5. Release & iteration planning
• JIRA & GreenHopper
• Planning board, run by product manager
• Outcome is prioritized and estimated
stories and tasks
• Idea (epic) -> Stories - > Tasks
• Example
• Logging work from a workflow transition
5
5
6. Development work & QA
• JIRA & GreenHopper
• JIRA time tracking used for iteration status
• Dashboard & agile gadget for reports
• QA can reject (workflow step) work
• Bamboo
• Commits trigger a series of builds
• Build telemetry for status monitors
• 45 min to find out build status for a commit
6
6
7. Summary
• Confluence drives specifications and
feature crystallization
• JIRA & GreenHopper track our
development and generate our
reports
• Bamboo keeps our developers
honest
7
7