Making Software for the Software Makers: How Atlassian Teams use Jira Software
•
6 likes•46,169 views
Ever wondered how internal Atlassian teams push Jira Software to the limit? At Atlassian each team defines a process that best meets their unique needs and challenges. In this talk Product and Marketing Management duo Jason Wong and Jake Brereton will share insights into how Atlassian teams harness and stress test Jira Software to get their teams humming. You'll leave this session with a behind-the-scenes look at how our teams: - Build custom views that put the right information in front of every team, role, and specialization - Add depth and accuracy to status tracking with deep developer tool integrations - Use apps for Atlassian tools to ensure all team members are fully connected to a common workflow
Report
Share
Making Software for the Software Makers: How Atlassian Teams use Jira Software
- 1. Making Software for the Software Makers How Atlassian Teams use Jira Software JAKE BRERETON | JIRA SOFTWARE PMM | ATLASSIAN | @JAKEBRERETON JASON WONG | JIRA SOFTWARE PM | ATLASSIAN | @JASEWONG
- 2. No two teams are the same, and so no two teams use JIRA the same way. JAKE AND JASON
- 7. JDOG
- 8. 918 boards 468 custom workflows 337 projects
- 10. Agenda On Time Agile Experimentation at Scale Connected Crafts When Incidents Strike High Visibility Boards
- 11. Let’s run this as a deadline driven project! SAID NO AGILE TEAM, SINCE THE BEGINNING OF TIME
- 18. Upfront estimation. Investigation over estimation Dive in and spike it! QA kick off Be sure to still discuss technical approach Progress & risk Get a real handle on trajectory ASAP Constantly review The earlier, the better Iron triangle Have the hard conversations early
- 19. Wallboards Tactile and visual. An omnipresent reminder of progress and risk. Focus with fun Celebrating real progress. Agile slam Based on a poetry slam: encourages people to get up in front of a crowd to share through experiences. Encourage teams to develop and share new traditions
- 20. Agenda Connected Crafts When Incidents Strike High Visibility Boards Experimentation at Scale On Time Agile
- 21. Atlassian Growth Web Experimentation Team
- 25. Mars Experiments Status & Findings Metadata & Narrative Offline Notifications Status Reporting Source of Truth
- 32. Leverage the Jira APIs Jira has a modern set of web integrations that allow it to connect with just about everything. Jira Software + Confluence Jira always knows where work is. Confluence excels at providing vital context for that work. Automate scalable processes If there’s any process that you find yourself repeating, find a way to automate that process. Build systems that provide users with a single source of truth
- 33. Agenda When Incidents Strike High Visibility Boards On Time Agile Connected Crafts Experimentation at Scale
- 35. Tracking all of this in real-life Development ProductMarketingDesign
- 41. KEEPING TRACK OF IT ALL Tables Sprint by sprint. Dev, design & PM side-by-side. Links Rich in context, but content heavy. Updates Easy to setup and manually update, but difficult to maintain.
- 42. Tracking all of this in real-life Development ProductMarketingDesign
- 43. Development Marketing Design TO DO IN PROGRESS DONE PR / AwaitingTO DO DONEIN PROGRESS DEVBACKLOG SHIPPEDDESIGN TO DO IN PROGRESS READY SHIPPED Dark Boardwalk DEPLOYED
- 46. Cross functional board Promotes awareness and facilitates interaction across teams and disciplines
- 47. Walking the board Communications routine
- 48. Envision it. Build it. Market it. Establish solid connectivity across roles & teams, using a cross-project board. Boardwalk tradition Communicate! Storytelling, visuals & demos. A board for every team Enable people to specialise to their craft. Connected boards, continuous context
- 49. Agenda High Visibility Boards On Time Agile Experimentation at Scale When Incidents Strike Connected Crafts
- 52. By failing to prepare, you are preparing to fail. BENJAMIN FRANKLIN
- 54. Jira Software • Issue tracking • Customer incident reporting • One source of truth Confluence • Capture and deliver decisions • Post-incident review process HipChat (and Bluejeans) • Realtime, persistent group collaboration • Video conferencing StatusPage • Incident communication • Customer trust What tools do we use?
- 55. OPSJ / JIRAIMA Microservice Blue Jean Hipchat Confluence Update HOT ticket with link Web hook on “manage transition”
- 62. Bring method to madness Ensure you have one place to track incidents so your team can stay focused 100% on the issue. External comms matter Keeping your users and customers in the know during an incident is vital to business success. Shit will hit the fan We talk in terms of nines for a reason, and you must be prepared to respond in an instant. Weekends favor the prepared, and weekends are awesome
- 63. Agenda When Incidents Strike On Time Agile Experimentation at Scale High Visibility Boards Connected Crafts
- 65. feature / JIRA-30 master Commits Open PR Merged PR Builds Pass/Fail New branch Branches, commits and PRs provide tons of status information
- 66. feature / JIRA-30 master Commits Open PR Merged PR Builds Pass/Fail New branch TO DO IN PROGRESS DONE Branches, commits and PRs provide tons of status information
- 67. feature / JIRA-30 master TO DO IN PROGRESS DONE Branches, commits and PRs provide tons of status information
- 68. development[commits].all development[pullrequests].open JQL that identifies issues by dev status development[reviews].all development[pullrequests].all development[reviews].open
- 69. DEV STATUS JQL Green All PRs are merged! Yellow Reviews still not done or not merged Blue Only seeing commits, not yet any sign of reviews
- 74. Ability to quickly eyeball cards that are out of place You can better trust the board when it is cross checked with dev status
- 75. WE’D LOVE TO SEE YOUR TEAM’S JIRA customerstories@atlassian.com
- 76. Thank you! JAKE BRERETON | JIRA SOFTWARE PMM | ATLASSIAN | @JAKEBRERETON JASON WONG | JIRA SOFTWARE PM | ATLASSIAN | @JASEWONG