Ross Clanton and Amy Walters walk through an enterprise playbook, tactics, and case studies for how to successfully transform from a project to product based operating model. The target audience for this paper is leaders at any level of the enterprise who are driving a transition to a product-centric model. Transformations that shift from project to product require changes at every level and in every corner of the enterprise.
The Product Backlog Refinement (PBR) activity is one that many new Scrum teams struggle with. Insufficient PBR often results in long sprint planning meetings and incomplete backlog items at the end of the sprint. This article provides some tips on how to improve backlog refinement, which in the past was called backlog grooming.
The Minimum Viable Product (MVP) is an approach that aims to avoid building products that customers don’t need or want by maximizing your learning about what is valuable for them. In this article, Sergej Hermoni shares seven reasons why you should include building an MVP in your Agile approach.
Do you have a nagging feeling that your Scrum team may not be investing in building the right thing? Do your products have features that are rarely or never used? Does it take your organization the full investment of building and launching a product to validate an idea?
Minimum Viable Product (MVP) is one of the most misunderstood, misused, and abused terms in contemporary software development. In this talk, Jeff Patton explains the misunderstandings made by thought leaders that lead to the confusion we all deal with today. You will learn the counter-intuitive concepts hidden in the term and why really using them is so hard.
This video will provide you with practical techniques on how to build a powerful roadmap for your product or service, one that allows any Agile organization to get valuable feedback from their customers and deliver business value.
Your product roadmap can basically set your life course as a designer/researcher so why is it so often that user feedback can get lost in the discussion over “Feasibility” of implementation. Without a clear roadmap, research and design can often not have the lead time needed for activities. This leads to a state of forever catching up and being reactionary.