CAS Backlog Refinement
   

Topic Summary

It is difficult for teams which size is huge. In this webinar, we explored frameworks that support product owners and Scrum Teams working together to refine backlogs in large and/or distributed teams. It is providing focused, outcome-driven solutions to collaboration problems faced by CSPOs, ScrumMasters, and Scrum members in organizations of ten or more Scrum Teams. 

Top 3 Questions Asked

  1. Often we see Bug as PBI, is it good practice or we need to create a story for it?
  2. What’s the advantage of having single product backlog over one per team when scrum teams / POs are different for different modules/ sub products?
  3. How are some of these techniques done successfully with distributed teams? For example, how do you do story rounding with offshore teams?

Featured Framework

       story rounds

Speakers

Greg Hutchings: Greg Hutchings is an expert in new product development and organizational improvement. He is the founder of Amelior Services, providing Agile and Innovation training, coaching, and consulting to global clients. Greg also works with Xebia France as an Agile leader, serving large clients in the Paris area (he is bilingual French/English).

 

Jean-Paul Bayley: Jean-Paul Bayley is the Lead Consultant of Bay Spark Ltd., a firm specializing in business agility and organizational development. Jean-Paul is a former Software Development Manager and Enterprise Architect for Kaplan International. He led the Agile transformation there, and oversaw the growth of the department from three developers to over 40. Jean-Paul is a CSP®, CSM®, and CSPO®.

 

Luke HohmannLuke 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.    

More Frameworks Discussed in this Webinar

      Impact Effort Startstory roundsstory mapping

Contact the Collaboration at Scale Team

Subscribe and Receive Conteneo's Newsletter and Updates

Top 3 Questions Asked & Answered

Question 1: Often we see Bug as PBI, is it good practice or we need to create a story for it?

Answer: Sometimes we’ve found that  bugs capture aspects of our product that have not been as well designed as we intended. When this happens we often fix the bug AND write a user story to green the light the redesign work to make our offerings dramatically better.

Question 2: What’s the advantage of having single product backlog over one per team when scrum teams / POs are different for different modules/ sub products?

Answer: The different modules and sub-products may already be sub-optimizations from a product and customer perspective, and it is doubtful that they’d always be of equivalent urgency/priority (on the module level). A single product backlog encourages seeing and optimizing the whole, not the sometime arbitrary way in which we’ve chopped up the solution.

Question 3: How are some of these techniques done successfully with distributed teams? For example, how do you do story rounding with offshore teams?

Answer: Best is to have each site with self-organizing, cross functional feature teams that include domain skill – then each site can do refinement locally, with a merge / diverge / merge pattern to assure alignment between sites for one single backlog.