Product Owner

The Daily Scrum, or Daily Standup, is a brief, 15-minute meeting where team members sync up on their progress, plan for the next 24 hours, and highlight any impediments. This promotes transparency, early issue identification, accountability, and open communication, fostering team cohesion.

A Sprint Planning Meeting is a meeting where the Scrum Team decides what they will work on during the upcoming Sprint. Primarily, the Product Owner and the Developers collaborate to define a goal for the Sprint and select the Product Backlog Items that will help achieve this goal. This Sprint Planning template will help ensure your teams success.

An excellent method for prioritization is Relative Weighting, which Karl Weigers introduced in 1999. This method not only provides a mechanism for prioritizing requirements based on user input and feedback but also includes the expert judgment of the team. Like other prioritization techniques, Relative Weighting allows the Product Owner to better gauge which features to implement and in what priority order.

As the sun rises over the digital landscape, Product Owners find themselves at the helm of a dynamic ship—their vessel, the product, charting a course through ever-changing waters. In this voyage, they encounter storms of stakeholder expectations, whirlpools of conflicting priorities, and the siren call of rapid release cycles. Fear not, fellow navigators! Let us unfurl the sails and explore the art of Product Ownership.

Having a Product Owner participate at Daily Scrum meetings can be an invaluable tool for ensuring Scrum team accountability. However, there are also some drawbacks associated which must be taken into consideration before deciding whether or not it’s worth it. In this article we will explore how having a Product Owner attend Daily Scrums can provide benefits as well as examine any potential drawbacks associated with their presence.

The Kano Model of Customer Satisfaction is a questionnaire-based approach and is a powerful way of visualizing product characteristics and stimulating debate between the delivery team and stakeholders.

Which feature will entice customers to purchase your product? Which feature will cause customers to upgrade? Which feature will make customers so happy that they’ll ignore or tolerate the features that they wish you would fix or remove?

Gardeners prune trees to control their growth. Sometimes the pruning is artistic, and we end up with shrubs shaped like animals or interesting abstract shapes. Much of the time the pruning is designed to build a balanced tree that yields high quality fruit. The process isn’t about “cutting” – it is about “shaping.” Use this metaphor to help create the product your customers desire.

We put a lot of emphasis on being Renaissance workers, able to step comfortably from one job role to the next. But, as I describe here, not all roles play nicely with each other, and trying to combine them may lead to disaster.