Anyone who works in support will agree: it feels like the dev team isn't exactly on your side. One of the biggest frustrations in support is when a problem can’t be solved because the dev team is needed to fix a bug or create a new feature. Check out we broke down the departmental silos.

Continue reading »

3 DevOps principles to apply to your IT team

DevOps is a movement that advocates a collaborative working relationship between Development and IT Operations, where historically they have been separated. Check out the three main DevOps principles (from The DevOps Cookbook) and how to apply them to your IT team.

Continue reading »

We've written quite a bit about the conundrum of writing requirements in an agile environment. 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 »

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 »