While the Scrum ideal is colocated teams, the Scrum reality is that many teams have Product Owners and Developers separated by multiple time zones, challenging traditional release planning practices. This webinar explores distributed team release planning, providing practical frameworks to help teams plan more effective releases.
Top 3 Questions Asked
Kevin Rosengren: Kevin Rosengren, CSP®, CSPO®, CSM®, is a senior consultant for AppliedFrameworks where he coaches product leaders to focus on the business of the product — not just the technology. Before joining the firm, Kevin was a senior director for product management at Capital One for over six years. With more than 17 years of experience in product management, he has lead teams of product managers and designers who delivered digital products for the credit card and retail rank divisions. Previously a director at E*TRADE, Kevin’s expertise lies in strategic product development and Agile team coaching. Kevin received his BS in business administration from Boston University with concentrations in finance and organizational behavior.
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: Try to let the nature of the epic help you answer this question. When the epic relates to or is decomposed into a User Story Map, it is often helpful to let one team handle all of the stories within Story Map because they’ll have a better grasp of the overall flow and the goals/needs of the users. When an epic is decomposable into separate, independent stories it is more easily distributed to different teams.
Answer: What I have found is that it’s not that they don’t want to develop or share a vision, but Product Managers often don’t appreciate how powerful they are for the team. A simple conversation perhaps part of a retro is usually all it takes. The other thing is to make it fun and collaborative. You can use frameworks like Product Box or Cover Story to develop and communicate a vision
Answer: I have seen some teams work tackle the problem with mock input/output. This can be acceptable, but I believe that mock input/output introduces other forms of risk. I prefer to have developers have access to a full copy of production data a technique I describe more fully in this post, Glass House Development.