You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Here we are at 3:24 at Atlassian in San Francisco. We are reviewing our Trello board that is shared with our vendor. All dependent blockers are fixed. We are using HipChat to wake up our system admin in Sydney for a DNS update. Our JIRA ticket is previously filed with the explicit requirements. My Confluence blog to all Atlassian announcing the launch is in draft and ready to go! (and the champagne is in the fridge)
We chose to use Trello to share and manage a to do list with our vendor. It was light and easy to update, and we didn't want to give access to our internal JIRA project. We created columns to identify low priority, URGENT, Atlassian review, and closed.
Our team collaborated with stakeholders on requirements and decision registers in a confluence space dedicated to Atlassian Community. Here, our Design team also uploaded and shared their mocks per user story. You can see how we included JIRA tickets for our Project Central project. Atlassian uses a centralized JIRA project to share weekly project status updates across the company.
HipChat rooms helped to keep audiences separate. Organically, we arrived at having a room for X-Force that included contributors from anywhere across Atlassian including Marketing and stakeholders. We create Community Design for our UX team in Austin, TX to talk directly with our developers. And, we needed to create Decision Swarm, where we would all enter in to spare and come to agreements as new issues arose.
In JIRA, we used Kanban, and two week sprints. Our development team was new to the platform we were builidng on, and in many cases we were dependent upon our vendor to close tickets. Kanban gave us the flexibility to enable our team to pull in additional work if they were blocked. It also enabled our business teammates to track their activities required for launch alongside platform delivery.
And in the time that it took for me to write this, we have fixed a CDN issue, removed simple auth, our system admin arrived and is updating our DNS! (and the champagne is chilled.... gotta run!)