Scrum distribution risk score
Download as PPTX, PDF0 likes534 views
The document discusses the challenges and risks of managing distributed scrum teams, emphasizing the importance of calculating a distribution risk score based on factors such as physical distribution, logical team organization, project size, and product organization. It outlines various strategies to mitigate issues arising from distribution, including adjusting team structures, increasing overlapping work hours, and enhancing communication. The document concludes with a call to recognize and manage these distribution risks effectively to optimize agile practices.
Scrum distribution risk score
- 1. SCRUM Distribution Risk ScoreAnna Obukhova, Project ManagerAnna.Obukhova@exigenservices.com
- 2. AgendaAgile – the distributed problemWhy we are forced to be distributedDistribution FactorsCalculate your distribution scoreWhat is different when you have high distribution scoreExamples of high-score team structureRecommendations
- 3. Why we start being distributed?Outsourcing to Low-Cost departments in one companyOutsourcing to another companyFollow the Sun modelMerges and Acquisitions - integrate productsLack of resourcesWork from Home
- 4. Factor 1: Physical distributionCollocatedCollocated Part-TimeDistributed with Overlapping Work HoursDistributed with No Overlapping Work Hours
- 5. Factor 2: Logical team organizationIsolated ScrumDistributed Scrum of ScrumsTotally Integrated ScrumFlexible Scrum
- 6. Factor 3: Project size1 Scrum Team - <10 members2 Scrum Teams - < 17 members> 2 Scrum Teams - > 17 members
- 7. Factor 4: Product organization> 1 products independent or using each other1 product – several integrated modules1 product with 1 piece of functionality or highly integrated modules
- 8. …. 4*4*3*3 = 144Max144 different SCRUM project organizations depending on these conditions. Lowest Distribution Score is 4 (1+1+1+1) = Collocated Isolated Small 1product). Ideal for XP and SCRUM, nice, productive, a lot of fun.Score 5-8 is normal for offshore development.Highest is 14 (4+4+3+3) Score = Flexible SCRUM, 1piece, distributed with no overlapped hours, team >20 members: project will not survive without special conditions or will have awful communication overhead.
- 9. We’ll discuss 2 and more teams (17 and more)Distributed with Overlapped working hoursAll levels of team logical distributionAll types of product integration level
- 10. When you have Distributed teamsNew Roles, management overheadProject manager (not Scrum Master)Architect (Chief Tech Lead)Proxy Product Owner (Analyst)More e-mails and documentationSelf documented code may be not enoughHandover architectural documentsReports on progress and impedimentsSub team and general Burn-DownLess Shared Code ownershipMini Demos
- 11. When you have Distributed teamsScrum of ScrumsHorizontal communication of Peers Scrum Masters/Chief SM (PM)Tech Leads/ArchitectTest Leads/Project Test LeadProxy Product Owners/Chief Product OwnerDependency managementCodeResourcesPeopleTime
- 12. Don’t forget communication toolsContinuous integration/build automationTeam collaboration/task/bug tracker/report builder (Jira, TFS)Meeting culture/Scrum Meetings/Sprint PulseSkype/Video facilitiesWebex/Screen sharingAirplaneBeer
- 15. So… if you face distributed oneMax attention to communication, visual, personalMore beer if necessary, start with team buildingKnow your type of Distributed Agile, plan additional rolesUse Kanban principle to balance the load and avoid the bottlenecks on specific rolesUse Sprint Pulse to manage the meeting and communication overhead level and team communicationPeers speak with peers, is your SMs do not talk to each other – you are in troubleCalculate the Load Factor – it will be different from type to type
- 16. Plan to decrease the distribution scoreTry to make your cumulative Agile distribution score as low as possible- avoid unnecessary distribution- define independent modules- Increase overlapping hours - think of smaller team - isolate Scrum where possible - any level raise treat and calculate as risk for the projectAnd…know and practice Agile from beginning to end, better practice lower distribution level Agile before (by you or get expertise in your company).