The sprint review and sprint retrospective are commonly conflated. In reality, these two scrum ceremonies are quite different in a variety of ways.

Product managers often struggle to communicate product strategy. See some tips for gaining buy-in from top leadership.

Are you a product leader looking for a way to inspire your team? This product strategy framework can help you guide your agile team to success.

Backlog grooming and sprint planning are both critically important to meeting your business and customer goals — and they’re also critically linked.

Quantitative product data is crucial to understanding user behavior. Learn how your product team can use this knowledge to improve the user experience, reduce churn rate, and generate ROI.

When launching a new product, it’s the product manager’s job to create a launch plan that aligns stakeholders around KPIs, promotional messaging, and more.

Believe it or not, planning poker a lot like it sounds. Learn how it helps agile teams estimate the work required to achieve their sprint goals (and plan accordingly).

You can’t plan for everything, but having a detailed, well-prioritized backlog can go a long way toward positioning your team for an efficient, fruitful sprint.

When considering a product management framework, you should select one that’s best suited to boost profitability and help streamline processes.

It’s the product manager’s responsibility to build and manage a live product roadmap that is fluid and resilient. Discover how to gain buy-in from executives, peers, partners, and customers.

When conducted effectively, the daily scrum can be a great tool for facilitating self-organization, accountability, and adaptability.

A sprint retrospective is a valuable exercise to gauge how your team is feeling and consider key learnings and actions that you might collectively take to improve ways of working, processes, and use of tooling during your next sprint.