Coming off an amazing Jira Admin Day, we were so thrilled to spotlight the amazing team at Twitter and go behind scenes during a live “Ask Us Anything” session with Joe, Aswin, and Rei to find out more about how they unified projects, streamlined communication, and improved reporting across the organization Jira helps them better manage and track their work.
Thank you to everyone that submitted such great questions for the Twitter team, we tackled most of the questions posted below + a few bonus questions!
Also wanted to share @Joe Pursel's talk from the 2019 Atlassian Summit "Why I built my career with Atlassian tools & you should too!"
In case you’re not familiar, Twitter is an iconic social media platform that hosts more than 186 million users -- and growing. Behind the scenes, Twitter is a company with thousands of employees and hundreds of different teams, who use numerous tools to conduct internal work. Since 2007, Twitter’s development teams have relied on Jira Software to manage their work. By 2019, the adoption of Jira expanded rapidly to almost every team at Twitter, as teams found that
They’ve been so successful that Atlassian recognized their work by awarding Twitter the 2021 Team Award for “Best in Class, Technical”.
Hi Benjamin and Dave! As mentioned during our AMA, we cannot live without JEMH and ScriptRunner :) We actually have done incredible amount of customizations involving the latter, and made requests/dreams of our userbase a reality.
We definitely should have purchased Automation for Jira earlier, but we were a bit cautious the power that plugin grants non-Jira admins and possible performance impact from purely designed automations. For that reason, we waited until our Jira Data center implementation :)
Personally, I'm eagerly waiting to purchase the Elements Connect plugin and start doing more magic by connecting to external data source!
Prior to the Jira Data Center implementation, we had to resolve the Jira Service Desk (Service Management now) licensing issue due to how significantly the licensing/cost model changes from Server to DC for JSM. We were on the "unlimited tier" for JSM prior to DC implementation, and there was no way justifying $640000+/year cost, when we knew not everyone at the company was leveraging JSM and its features.
We ended up creating a separate user group that is exclusively given access to JSM and included only users that have login history spanning 6 months. Though we sent out multiple comms through personalized email, we did have a handful of users who were caught off guard with access change. However, this new model allows us to be a better steward of licenses, and therefore company money. While access to Jira itself is a birthright access, we enforce users to sign-up to be added to the aforementioned group, and it's been working great :)
I found that as the engineers/implementers of new features on Jira, Confluence, etc., we immediately celebrate the victory upon shipping. As mentioned during the AMA, I think it's crucial to have retros involving major stakeholders to really be introspective and get feedback from external teams. Despite the documentations we shared and training sessions we held, few PMs did state that this product we built wasn't that intuitive to use. I think our team was just marveled at the engineering feat and the fact that it "worked properly" was considered a success for us. Therefore, the retro was super helpful, as was getting user feedback utilizing Polly.ai
In couple projects, we fire off a webhook that calls Polly API to DM users a poll right into their Slack. This is super helpful for different teams (including us!) to get candid feedback from users regarding the UI/UX.
Hi Vaishali! There is how our team does prioritization, and there is how other teams at Twitter do it. Our permissions are set-up so that any Jira users within our instance can create filter and create Scrum/Kanban boards at will. This means the burden/creativity of the prioritization is in the hands of the creator and her/his team. At least in our team, we do leverage the innate Priority field and look at the context of the Jira issues to determine their urgency. I personally do not utilize the innate Rank field that comes with the usage of the Agile boards that come with Jira Software. If the number of issues in the Backlog is a problem, I highly recommend leveraging quick filters that can be added on top of the boards to filter out issues based on desired criteria. In case of our team, we have a quick filter for each of our team members to quickly reveal what each member has on their plate for a given sprint during our sprint planning meetings :)
Thank you for your reply. In our case, we too have kept the permissions open for anyone to create filters and boards. But many of our teams have opted to create separate boards instead of quick filters. It gets the job done in short term but comes with its own set of housekeeping headaches.
Hi Ashley! I sincerely believe documentations and education are key in bringing current (and future) users on the same page and governance/best practices. Documentations are often a bore, for both the creator and the informed. However, even linking your Jira Service Desk (or Jira Service Management now) to your support portal goes a long away to save time for both the inquirer and the dedicated Atlassian team. We do have an awesome engineer such as @Joe Pursel who regularly holds Jira 101 (basic Jira usage) and 102 (JQL tricks and filter/dashboard creation) classes at Twitter to train users in a live classroom setting. We are actually planning to record some videos on popular Jira topics so users can check them out at will :) I also recommend leveraging Questions for Confluence as another form of Knowledge Base your users can refer to!
Cool! Looking forward to the meeting.
Wow, I'm super excited and can't wait for this talk!
- How many administrators do you have? How do you communicate with each other about changes in your Jira instance?
- In which methodology are you working? Do you have any best practices from your teams about useful features in Jira?
- Are you fans of team-managed projects? :)
How do you gain visibility over where your effort is going from a single team to large departments?
Where do you see the balance between having this type of information being fully automated in reports versus relying on human assessments?
What has been your main challenge(s) when doing this type of capacity/effort/people planning at scale?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events