Download as PDF, PPTX
![development[pullrequests].open > 0](https://image.slidesharecdn.com/05-plan-pellow-170504095610/85/Black-Belt-Tips-for-JIRA-Software-114-320.jpg)
Uploaded byAtlassian
Black Belt Tips for JIRA Software
The document provides best practices for using Jira software, emphasizing the importance of early risk identification, effective estimation techniques, and streamlined workflows. Key suggestions include separating estimation from planning, utilizing quick filters and automated triggers, and maintaining focused standup meetings. The author encourages teams to engage actively and adapt practices that suit their unique workflows for optimal results.
More Related Content
Similar to Black Belt Tips for JIRA Software
Black Belt Tips for JIRA Software
- 1. Black belt tips forJIRA Software NICK PELLOW | DEV MANAGER | @NIICK
- 2. Photo of theJIRA Software Team
- 3. Esther Asenjo Atlassian Purchasing AndyDrizen JIRA Cloud Mobile Michael Tokar JIRA Edward Zhang JIRA Service Desk
- 4.
- 5.
- 6. You’ve worked with JIRASoftware before
- 7. Some form of‘Agile’ team
- 8.
- 9. Identify risks earlywith a pre-mortem
- 11. Esther Asenjo Atlassian Purchasing AndyDrizen JIRA Cloud Mobile Michael Tokar JIRA Edward Zhang JIRA Service Desk
- 12.
- 13. Separate estimation fromplanning
- 14. Time to gointo detail Separate estimation session Identify blockersFocused
- 15. Photo of teamdoing planning. Someone is looking out the window, bored
- 17. Epics and quickfilters to focus the content
- 18. Voiceover points only Point 1 Point2 Point 3 Point 4 Epic panel
- 19. Voiceover points only Point 1 Point2 Point 3 Point 4 Click to filter
- 20. Talking point Supporting textshould be brief and no longer than 4 lines. Limit one talking point and image per slide.
- 21. Voiceover points only Point 1 Point2 Point 3 Point 4 Quick filters
- 22. “Story Points” isEMPTY Status in ("To Do", "Ready for Dev”) labels = squirtle-squad Quick filter JQL Unestimated Not Started Sub team
- 23. Voiceover points only Point 1 Point2 Point 3 Point 4 Issue detail panel
- 24. Customise your board’sissue detail view
- 26. Photo of themeeting with someone saying that we need a new issue
- 27. Voiceover points only Point 1 Point2 Point 3 Point 4 Create issue
- 28. Voiceover points only Point 1 Point2 Point 3 Point 4 Create issue in epic
- 29.
- 30. Voiceover points only Point 1 Point2 Point 3 Point 4 Create issue inline
- 33.
- 34. The keyboard shortcutsto success
- 35. Assign Assign tome Send top Send bottom Key shortcuts + +
- 36.
- 37.
- 38. Photo of team interestedand engaged
- 39. Esther Asenjo Atlassian Purchasing AndyDrizen JIRA Cloud Mobile Michael Tokar JIRA Edward Zhang JIRA Service Desk
- 40.
- 41. Estimation SO KEEP ITFRESH! PLANNING POKER SOME > NONE Sometimes so hard, plenty of teams skip it entirely… Can often seem very arbitrary. Hard to calibrate a team on story points Low engagement == low commitment
- 42.
- 43. Order cards Planning prep Assignstory pointsPlanning prep Rough set of stories for sprint. Prints the agile cards. From simplest to most complex Start with simplest set: 1s Then next simplest set: 3s, etc etc
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52.
- 53. Blank with titleNewstory!
- 54.
- 55.
- 56.
- 57.
- 58.
- 59. Some > none Theart of estimation itself is often the value, not the estimate. More involvement Tangible cards on the table is fun. No laptops! Easier to estimate Much faster comparing 2 stories, than all stories! Relative Estimations
- 60. Esther Asenjo Atlassian Purchasing AndyDrizen JIRA Cloud Mobile Michael Tokar JIRA Edward Zhang JIRA Service Desk
- 61.
- 62.
- 64. Use an open workflow Issuescan move to any status
- 65.
- 66. TRIGGERS Branch created Pull request merged Deployment successful Typeyour annotation here, the dotted line can be moved and/or re-sized.
- 67. TRIGGERS Branch created Pull request merged Deployment successful Typeyour annotation here, the dotted line can be moved and/or re-sized.
- 68.
- 69.
- 71. TRIGGERS Branch created Pull request merged Deployment successful Typeyour annotation here, the dotted line can be moved and/or re-sized.
- 72. DONE means deployed On pullrequest merged ‘Awaiting deployment’ as a holding ground Master means customers
- 73. TRIGGERS Branch created Pull request merged Deployment successful Typeyour annotation here, the dotted line can be moved and/or re-sized.
- 74. Headline 3 Subtext typesize is optimized at 36 pt. Rehearse Rely on rehearsing your voiceover rather than writing. Branch created No worries It’s OK if the subtext lengths differ. Pull request merged Deployment successful Branch created
- 75. One pull requestper issue
- 76. Progress >> perfection Perfection isnot necessary to make an impact Each team is different Find what works for you Experiment Introduce slowly, allow for critique Triggers
- 77. Esther Asenjo Atlassian Purchasing AndyDrizen JIRA Cloud Mobile Michael Tokar JIRA Edward Zhang JIRA Service Desk
- 78. JIRA Service Desk EdZhang
- 79. Lack of progress Lackof focus Quality of demos Sprints are tough… Are we there yet ? Many, unrelated streams of work in flight Bad reflection on the team Bad vibe in the team
- 80.
- 81. Demo driven Sprint goals MeasurableDecideas a team With input from PM, however team needs buy-in & commitment During pre-planning, imagine what the demo will be like Be specific. Build your measurement first!
- 82. D3 conversion demoableand the dashboard performance improved by 10% on 9 August ServiceDesk #SprintGOAL
- 83.
- 85. Can be used aspro/con, hypothesis/ finding, etc. Use when explaining two sides of a point. ONE SIDE THE OTHER SIDE
- 86. Can be used aspro/con, hypothesis/ finding, etc. Use when explaining two sides of a point. ONE SIDE THE OTHER SIDE
- 87. Can be used aspro/con, hypothesis/ finding, etc. Use when explaining two sides of a point. ONE SIDE THE OTHER SIDE
- 88.
- 89.
- 90.
- 91.
- 92.
- 93.
- 94.
- 96. Build a standupboard
- 97.
- 98.
- 99.
- 100. Participants only Only active participants willtalk Less waffle Use this time wisely to discuss what’s important - the actual work! Leaner “Cut our standup time in half!” Task centric standups
- 101. Black Belt tipsfor JIRA Software Separate estimation sessions Epics and quick filters Create issues inline Automatic workflow triggers Use the dot Relative estimation Sprint goals Task centric standups
- 102.
- 103. Bonus JQL Quiz! JIRAQuery Language is the key to JIRA mastery
- 104. In which versionof JIRA was JQL introduced?
- 105.
- 106. What JQL allowsyou to find all issues created in the past 2 weeks?
- 107.
- 108. Find all issuesin an open sprint?
- 109.
- 110. Select all issueswhere the label ‘foo’ does NOT exist?
- 111.
- 112. labels != “foo”OR labels is EMPTY
- 113. Show all issuesreferencing a Pull Request that is still open?
- 114.
- 115. Thank you NICK PELLOW| DEV MANAGER | @NIICK