Archives for the tag: JIRA

Inside Atlassian: 4 ways to deal with scope creep

Stealthy and unavoidable, scope creep hovers over every software development project. Like any other agile practice, no two teams manage scope creep the same and teams at Atlassian are no exception. So we decided to go straight to the horse’s mouth to learn how two of our teams deal with scope creep. We interviewed development leads on two teams: the JIRA Agile team and the Fusion team – our Fusion team oversees JIRA Software's integrations with Atlassian's developer tools. Even though

Continue reading »

When something goes wrong, it's nice to know that you can simply raise a ticket and see it fixed. For those of us doing the fixing, it's not as easy as it looks. You've probably got a backlog of tickets that you need to sort through each day. Some of those tickets actually report a broken service. Others might be suggestions for improvements. And some are, in fact, not bugs at all. The bug triage process helps you sort out which issues are which, communicate with the reporter in a timely manner

Continue reading »

With over 500k agile projects in JIRA (among just Cloud customers – wow!), we realized we're sitting on a ton of data that sheds light on how agile teams function. We then bet, that with some anonymized data mining, we could find teams that have a release cadence that they hit sprint after sprint after sprint.

Continue reading »

Last month, we had the pleasure of attending the SITS 2015 conference, and we were blown away by what we saw, who we met and the overall reception from newcomers and our peers alike. We met some amazing teams doing incredible things, and we were humbled by the glowing review that not just JIRA Service Desk received, but Atlassian. When we arrived at SITS 2015, we were new to the space – this was only our second year in London, so the Atlassian crew was a little nervous that JIRA Service Desk

Continue reading »