We've written quite a bit about the conundrum of writing requirements in an agile environement. The most important takeaway is: the best way to kick-off your software projects is to build a shared understanding amongst your team. At Atlassian we find the best way to do this is to create a collaborative product requirement to hash out details for large complex epics. When your requirement doc is created and the details are all in one place, it makes it a lot easier for Development and Design to provide

Continue reading »

4 essential how-tos for dealing 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 and JIRA Agile integrations with Atlassian's developer tools. Even though

Continue reading »

Codegeist 2015 is Atlassian's 8th add-on developer competition. Add-ons allow you to extend JIRA and other Atlassian products with even more functionality. Whether you're an experienced add-on developer or trying something new, now is the time to build your add-on and share it with the community.

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 »