Roman Pichler is a leading Agile Product Management expert. He has more than 10 years experience in training and coaching product managers and product owners, and in helping senior management establish an effective product management function. Roman is the author of the book Agile Product Management with Scrum; he has created several powerful product management tools; and he writes a popular blog for product people. To see how Roman can help you, please have a look at his training courses and onsite workshops, or contact him.
Roman’s product management courses help product managers and product owners acquire the knowledge they need to succeed in their job. Roman runs his classes as instructor-led workshops.
Roman’s product management tools help product managers, product owners, UX designers and business analysts create great products. For more information including templates and guidance on using the tools, please click on the the individual tool.
Discover Roman’s popular blog on agile product management. Benefit from his advice on topics such as the product owner role, product vision and product strategy, product roadmaps, personas, product backlog, and user stories.
The GO Portfolio Roadmap
Products don’t exist in isolation. Instead, they are often related to other products, which they help sell or they share features and components with. Think, for instance, of the Microsoft Office suite or the iPod product line. If your product is part of a family, then you will benefit from a portfolio roadmap, a plan that shows how the products are likely to grow together. This post introduces such a plan, the GO Portfolio Roadmap, and it describes how this roadmap can help you manage your product family.
Three Common Product Roadmapping Mistakes
The product roadmap is a great tool to describe the likely growth of a product. But there are three common mistakes I see people make: View the roadmap as a guarantee; show epics and user stories on the roadmap; and speculate about the likely development of the product. This post discusses the three product roadmapping mistakes to help you avoid and rectify them.
How Detailed should the Product Backlog be?
The product backlog is a great tool. But using it effectively can be difficult. One of the challenges is to get the level of detail right. An overly detailed backlog is unwieldy and hard to manage. But a product backlog that is too coarse-grained is also not helpful: It provides too little guidance for the development team. This post helps you strike the right balance between too much and too little detail. It shows you how determine the right amount of detail for your product backlog.