What is the most effective way you have found to manage dependencies on a single scrum team (platform/foundation) coming from multiple scrum teams (application teams). Planning one sprint ahead works to some extent but have others found better ways? Saving Changes...
Sort By:
Javier ArtimeAgile Coach - Applied Innovation Team| NCR CorporationCabezã³n De La Sal, Cantabria, Spain
Have you tried scrum of scrums techniques? You could organize a higher-level scrum team focused on delivering the product that incorporates all dependencies. A member of each smaller scrum teams will be present in the scrum of scrums call. The bigger team should provide a clarity in the overall goal, individual teams planning and integration.
An article by Mike Cohn that describes this technique: http://www.scrumalliance.org/articles/46-a...-scrums-meeting Saving Changes...
Josh NankivelEngineering Project Manager| AppleSioux Falls, Sd, United States
How about trying a master Kanban for the teams in lieu of a scrum-of-scrums? By mapping the value stream horizontally, and the different teams vertically in their own lanes, I'd bet you can come up with a great way to visualize these dependencies and points where one team is an obstacle or blocker to another.
I have used Kanban in this way on my own teams in order to identify these dependencies with a visual marker for blocked or 'waiting' items, indicating which team we are waiting on for the input. Saving Changes...
The ideal solution of identify dependency early does not work practically. Scrum of Scrum meeting helps. We tend to ask frequently dependent teams to reserve some % of time to address unplanned dependent items. Saving Changes...
Gaurav SapraProgram Manager| TATA Consultancy ServicesEdinburgh, Scotland, United Kingdom
I agree, found disciplined Scrum of Scrum quite useful in managing different scrum dependencies effectively. I think, Scrum of Scrum is equivalent to Agile Program Management minus Benefits Realization Management. Thoughts? Saving Changes...
