A Product Backlog is an ordered list of everything known to be needed in the product. In this webinar, we explore a variety of frameworks that Product Owners and Scrum teams can use to prioritize backlogs.
So backlog is prioritized according to value and teams always try and maximize the value they deliver. But how do you get your product owner to care about the technical stuff? Because even if you add it to the list they see no value in it. Do you add a technical product owner?
Carlton Nettleton: Carlton Nettleton is an international speaker based in San Diego County. He is a thought leader on Scrum and Agile software development and the author of Fourteen Observations of Good Scrum Practice. He provides advice, consulting, mentoring, and training to teams and organizations, from small start-ups to businesses that develop products regulated by the Food and Drug Administration. As president of Look Forward Consulting (lookforwardconsulting.com), Carlton has over ten years of experience working side-by-side with clients to improve quality, increase productivity, build great teams, and apply Lean Thinking to software programs. He is a Certified Scrum Trainer®, bilingual in English and Spanish, and a part-time Lisbon resident.
Luke Hohmann: Luke Hohmann is the founder and CEO of Conteneo In.(formerly the Innovation Games Company). Conteneo's enterprise software platforms and professional services merge collaboration frameworks, data analytics, and domain expertise to help organizations optimize decision making in the areas of strategy, innovation, sales, product development, and market research. Luke is also co-founder of Every VoiceEngaged Foundation, a 501(c) 3 nonprofit that helps citizens, governments, and other nonprofit organizations collaborate at scale to solve technical and wicked problems.
Answer: Yes. There are times when hiding the weighting criteria can improve the prioritization outcome because it helps participants focus on the degree to which an item aligns to a given initiative or attribute instead of the weights of the attributes. I explore this more fully in this conference talk.
Answer: I agree. The Business Value Game developed by Agile42 uses a Fibonacci scale of value points to help determine priorities. Just click here to try this framework in the Conteneo Weave™platform.
Question 3: So backlog is prioritized according to value and teams always try and maximize the value they deliver. But how do you get your product owner to care about the technical stuff? Because even if you add it to the list they see no value in it. Do you add a technical product owner?
Answer: Unfortunately, starving technical improvements is far too common in the Agile community. However, we do not recommend adding a Product Owner. Instead, we recommend that the PO use the Innovation Game® Prune the Product Tree to identify infrastructure items (the roots of the tree). Once identified, we recommend that the PO explicitly include technical items in both the roadmap and the backlog.