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 »

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 »

This post is part of our collection on product management. Learn best practices and get advice from Atlassian’s product managers here. As product managers, we take every opportunity we get to learn more about our customers because understanding their needs is critical to building and releasing useful products. This means conducting customer interviews, running surveys, and examining in-product analytics. The data we glean from product analytics tell us how users actually use the product –

Continue reading »

A product manager’s guide to release planning

Growing up, my ski coach always used to say "If you don't plan for it, it won't happen." He wanted us to set goals and lay out a path to reach them. The same sentiment can be applied to building software, except building software is much more of a team sport than skiing. You need to make sure everyone on your team – plus other stakeholders like marketing and support – understands what you're trying to build, why you're building it, how long you expect it to take, and how the project is tracking

Continue reading »