We are introducing Portfolio for JIRA 2.2 to help you improve your roadmap. Now teams can baseline their velocity, compare initial and current project timelines, and pick the best roadmap scenario plan so they can move forward with confidence. Keep reading to learn more about these new features and how they can help you plan better.

Continue reading »

One of our main goals as product managers as we move from casting the vision to building the version is to de-pressurize the room – no one on the team should waste energy sweating over the perfect product. Instead, focus on minimum viable product (MVP). That is, get the team to concentrate on shipping the best first version in order to gain insights. Then use that feedback as a compass for future versions.

Continue reading »

What's the best way to capture and document customer feedback without letting anything slip through the cracks? To learn how Atlassian product managers handle this process, we reached out to two of our own: Jason Wong, Principal PM of JIRA Software, and Sherif Mansour, Senior PM for Confluence. Today's post kicks off the two-part blog series with Jason, and in the second part we'll get insights from Sherif.

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 »

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 »