Archives for the tag: product management

When you think of an API, you probably don't picture a bunch of drawings on a whiteboard. But exactly one year ago, our plans for HipChat Connect were just that. In a year this idea evolved through several stages and finally made it to public GA with over 30 partners. We've learned a lot about shipping and partnership in the process, and we hope what we've learned will be helpful to other software development teams like yours.

Continue reading »

A story map is a visual representation of the journey a customer takes with a product, including activities and tasks they complete. Agile teams create the story map in a collaborative session to ensure they have a shared understanding of the customer and their desired outcomes. Today I'll show you the basics of user story mapping and why it’s a worthwhile endeavour for your agile team.

Continue reading »

This is part 2 in our "PMs weigh in" series, focused on how two seasoned Atlassian PMs navigate the flood of customer feedback inputs, and prioritize them in a way that maximizes customer and product impact. You can find the first part here. Gathering customer feedback, turning feedback into actionable inputs, and then prioritizing those inputs for your development team are some of the most important functions of a PM. They're also the most challenging. Every PM has their way of balancing and

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 »