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 »

JIRA Service Desk is the fastest growing product in Atlassian history, and we only started two years ago. The rocket ship we're riding is amazing. We get out of bed every morning, ready to continue crafting software that IT teams actually like to use. We want customers to feel at home and live up to the high standards set by JIRA. And we don't want all this to cost you a bazillion dollars. Based on a report that just came out, it seems we're on the right track. Voted one of the best service

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 »