top of page

Muay Thai

Openbaar·9 Sporters

Agile Product Management: Product Owner (Box Set) : 27 Tips To Manage Your Product, Product Backlog:

The Professional Scrum Product Owner class is the cutting-edge course about organizing product ownership with Scrum in the most effective way. It explores the worldwide challenge that many Scrum implementations run into, i.e. how business people and product managers should engage in an environment of Scrum and in collaborating with a Product Owner and Scrum Teams. It is the class for awesome Product Owners and for anyone responsible for or involved in optimizing the value that products and services maintained with Scrum deliver.

Agile Product Management: Product Owner (Box Set) : 27 Tips To Manage Your Product, Product Backlog:


The Professional Scrum Product Owner class introduces the role and accountability of a Product Owner within the organization (as an Agile product manager) and on a Scrum Team. The class builds on the core expectation for Product Owners to maximize the value of the work done for a product, thereby serving customers, users and the organization. It includes techniques and thinking tools for product delivery with Scrum and the related behavioral shifts.

The Professional Scrum Product Owner class is an interactive experience in which Gunther Verheyen, independent Scrum Caretaker and Scrum practitioner since 2003, collaboratively explores with you what embedding product ownership in the wider organization and being a great Product Owner for a Scrum Team entangle, thereby drawing on nearly two decades of practical experience. All materials used in the class are in line with the 2020 version of the Scrum Guide.

Planning, demoing, and learning together creates the alignment that enables teams to independently and reliably deliver value. Agile teams drive value through the entire continuous delivery pipeline. Collaborating with product management around continuous exploration, they continuously integrate, and they continuously deploy their work to staging and (ideally) production environments. While Agile teams strive to independently deploy and release their parts of solutions, some technical, regulatory, and other hurdles may hinder them. In those situations, teams coordinate and align their deployment and release to production.

A great technique to capture your insights about the users and customers is working with personas. Personas are fictional characters that are based on first-hand knowledge of the target group. They usually consist of a name and a picture; relevant characteristics, behaviours, and attitudes; and a goal. The goal is the benefit the persona wants to achieve, or the problem the character wants to see solved by using the product.

But there is more to it: The persona goals help you discover the right stories: Ask yourself what functionality the product should provide to meet the goals of the personas, as I explain in my post From Personas to User Stories. You can download a handy template to describe your personas from

User stories are intended as a lightweight technique that allows you to move fast. They are not a specification, but a collaboration tool. Stories should never be handed off to a development team. Instead, they should be embedded in a conversation: The product owner and the team should discuss the stories together. This allows you to capture only the minimum amount of information, reduce overhead, and accelerate delivery.

You can take this approach further and write stories collaboratively as part of your product backlog refinement process. This leverages the creativity and the knowledge of the team and results in better user stories.

Thanks for sharing your feedback and question Siddarth. By definition, user stories describe end user requirements. You can, of course, tell stories about how a product is built using technical stories. But I find that natural language is not well suited to capture technical requirements, and I prefer to work with a modelling language like UML (Unified Modeling Language). If you manage a technical product like a software platform, you should have the necessary technical knowledge to capture the requirements for this product. Hope this answer is helpful.

Regarding your question, if a user can process a file and the individual can work on a database table, then I would be inclined to write two user stories. Technically, the stories may be implemented largely in the same way. But this should not matter when it comes to story writing. Remember: A user story should always describe what a user can do with a product, not how functionality is implemented. If you decide to create two stories and if these stories will be implemented in a similar way, then this does not necessarily create a new dependency. But it might result in a smaller effort estimate of the second story, assuming that the code written to implement the first story can be (partially) reused in the second one.

What would you do if, due to certain system components being unavailable, the DEV team requests stories that describe slices of user functionality to be broken down further at system component level?For example, AS a buyer, I WANT to see the total price for the selected product, SO THAT I can decide if I want to buy it. Due to commercial reasons, and for the next few sprints, the DEV team has no code access to the back-end system that will process the logic to derive the price. What we did in this case is to leave the story as-is with the prefix [Front-end]. Without a real calculation in place the user will see a dummy price and the story will pass. We created an identical story with the prefix [Back-end] which remained in the backlog until the calculation logic could be built.

Hi Sergey, Sounds like you should write stories for the CRM users, assuming that they directly interact with the system. You may find it helpful, though, to take a step back, determine the users and customers of the product, and create personas before you write more user stories. Good luck!

Thanks for your feedback and for sharing your question. No matter what product you develop, always starts with the users and the value the product should create for them. In your case, I would ask what benefit the tool should offer or which problem it should address, and who the users are.

Hi Vit, You can find user story examples in my other posts on user stories. I would hope, though, that my tips allow you to start telling stories about how users interact with your product. Remember: A user story is simply a story, no more and no less. And we all can tell stories.

The last point in time for the user stories conversation to happen is the sprint planning. But I would recommend including the team or some team members in the product backlog management work (aka grooming or refinement), as I discuss in my post Grooming the Product Backlog.

In addition to understanding the market, you should also address the collaboration between you and the product owner. It sounds to me as if you were at risk of becoming a poxy product owner, which I tend to find an ineffective solution, see my posts:


Welkom in de groep! Je kunt contact leggen met andere leden,...
bottom of page