SCRUM ProductManagementJournalVolume 7 13 addedorstoriesarecompleted.Aburndownchartrecordsuserstories completedandshowstheteamiftheyareon-tracktodeliverthe volumeofworkpreviouslyforecast. Scaling Scrum Scrumisgreatforstandalonedevelopmentprojectswheregoalsare changingandthe scalecanbe handledbyasingle team.However manyprojectshave anumberofteams workingindifferent locations,on multiplesystemsor onfundamental architecture changes.Thisisa commonchallenge inlargeprojectsand theimpactisto drivehybrid development modelssuchastheoneshowninFig.8.andmethodologieslikethe ScaledAgileFramework. Astheproductleadyouneedtoco-ordinate withyourcolleaguesandacrossmanydevelopmentteams.The challengeismaintainingconsistencyofpriorities,aligninguserstories andschedulinginter-dependentdevelopments. Greater responsibility Astheproductowneryousetthedevelopmentprioritiesthrough theproductbacklog.TheAgileapproachmeansthatyoucanchange directiontorespondtomarketandcompetitormovesorasthe understandingofwhat’sneededevolves.Thisplacesaheavy responsibilityonyourshouldersas,morethanever,thesuccessofthe productisdowntoyou. Sprint 1 Sprint 2 Sprint ‘n’ Final sprint Dev team 1 Sprint 1 Sprint 2 Sprint ‘n’ Final sprint Dev team 2 Product owner Product owner Product lead Product owner Sprint 1 Sprint 2 Sprint ‘n’ Final sprint Dev team 3 Sprint 1 Sprint 2 Sprint ‘n’ Final sprint Dev team 4 Sprint 1 Sprint 2 Sprint ‘n’ Final sprint Dev team 5 Sprint 1 Sprint 2 Sprint ‘n’ Final sprint Dev team 6 Fig.8Managing multiple development teamswith Scrum