Reading Time: 3 minutesCompanies having an indifferent understanding of their own product values lack a product vision and product definition. They have a conception of the output only, but they don't have an overall conception of the outcome their products have.
Reading Time: 5 minutesTo create resilience in Product Development, identify product variants as unique products; slice your value streams by customer-centric end-to-end product thinking only; and install product teams as cross-functional, cross-department entities only.
Reading Time: 3 minutesIs Business Value only determined by maximising features delivered fitting the right time to ship the product to market? — Or do other aspects add relevant benefits?
Reading Time: 4 minutesWhen you ask Teams or Product Owners the question "What is your Product?" they often first answer with a list of functions and features. In the second attempt, then they describe the purpose from the view of the engineers and designers, and how they intend it. Very seldom does the customer occur.
Reading Time: 7 minutesSoftware Project Management is managing all kinds of Dependencies. We have to deal with Technical Dependencies due to the SW tools we use and the product architecture decisions we agreed to. And we have to deal with non-Technical Dependencies caused by workflow and team dependencies due to the organizational work model and the design of our organization.
Reading Time: 5 minutesIf you dive into Agile Product Development, resp. in Agile Software Development you get into a lot of new and abstract terms. One of the most blurred and therefore most fascinating ones is "Value" resp. "Product Value". However, the Scrum Guide 2020 is keeping very quiet about an explanation. In this post I argue for the customer to benefit from value.
Reading Time: 3 minutesProduct Discovery and Delivery are crucial in Product Development. In Product Discovery, we identify additional opportunities. In Product Delivery, we test continuously together with the customer our implementation.
Reading Time: 5 minutesIn the traditional way, a Product Roadmap states when and which functionality will be released. The Roadmap is aligned with business strategy and release dates. It is a kind of Roadmap, a long-term plan. Instead, an Agile Roadmap is more about communicating our product strategy than it is about communicating features and dates. However, important dates should and could be mentioned, the Roadmap is a statement of intent and direction. The Roadmap visions the certainty and uncertainty of the project/product evolution. It is not a Gantt-chart, or milestone table.
Reading Time: 4 minutesYou can sabotage your product delivery by focusing on customer/user feedback over product vision, by changing given requirements or by adding new requirements too often. In delivering a product there are six well-known anti-patterns: Product Death Cycle, Product Build Trap, Feature Hell, Experience Rot, Scope Creep, and Feature Creep.
Reading Time: 5 minutesMany agile glossaries still refer strongly to software development. but since Scrum Guide 2017/20 the new paradigm is Agile Product Development. One of the most blurred and therefore most fascinating concept is "Value" resp. "Product Value".
We lay the foundation for a shared common Glossary for Agile Product Development with a nucleus of only a few important concept definitions of user-centric Value-creation.
