scrum distribution risk score
DESCRIPTION
Presentation for AgileDays 2011 by Anna Obukhova, describes the problems of distributed development and team composition with recommendations.TRANSCRIPT
![Page 1: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/1.jpg)
April 10, 2023 www.ExigenServices.com
SCRUM Distribution Risk Score
Anna Obukhova, Project Manager
![Page 2: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/2.jpg)
2 www.ExigenServices.com
Agenda
Agile – the distributed problem Why we are forced to be distributed Distribution Factors Calculate your distribution score What is different when you have high distribution score Examples of high-score team structure Recommendations
![Page 3: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/3.jpg)
3 www.ExigenServices.com
Why we start being distributed?
Outsourcing to Low-Cost departments in one company Outsourcing to another company Follow the Sun model Merges and Acquisitions - integrate products Lack of resources Work from Home
![Page 4: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/4.jpg)
4 www.ExigenServices.com
Factor 1: Physical distribution
1. Collocated
2. Collocated Part-Time
3. Distributed with Overlapping Work Hours
4. Distributed with No Overlapping Work Hours
![Page 5: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/5.jpg)
5 www.ExigenServices.com
Factor 2: Logical team organization
1. Isolated Scrum
2. Distributed Scrum of Scrums
3. Totally Integrated Scrum
4. Flexible Scrum
![Page 6: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/6.jpg)
6 www.ExigenServices.com
Factor 3: Project size
1. 1 Scrum Team - <10 members
2. 2 Scrum Teams - < 17 members
3. > 2 Scrum Teams - > 17 members
![Page 7: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/7.jpg)
7 www.ExigenServices.com
Factor 4: Product organization
1. > 1 products independent or using each other
2. 1 product – several integrated modules
3. 1 product with 1 piece of functionality or highly integrated modules
![Page 8: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/8.jpg)
8 www.ExigenServices.com
…. 4*4*3*3 = 144
Max144 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.
![Page 9: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/9.jpg)
9 www.ExigenServices.com
We’ll discuss
2 and more teams (17 and more) Distributed with Overlapped working hours All levels of team logical distribution All types of product integration level
![Page 10: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/10.jpg)
10 www.ExigenServices.com
When you have Distributed teams
New Roles, management overhead– Project manager (not Scrum Master)– Architect (Chief Tech Lead)– Proxy Product Owner (Analyst)
More e-mails and documentation– Self documented code may be not enough– Handover architectural documents– Reports on progress and impediments– Sub team and general Burn-Down
Less Shared Code ownership Mini Demos
![Page 11: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/11.jpg)
11 www.ExigenServices.com
When you have Distributed teams
Scrum of Scrums Horizontal communication of Peers
– Scrum Masters/Chief SM (PM)– Tech Leads/Architect– Test Leads/Project Test Lead– Proxy Product Owners/Chief Product Owner
Dependency management– Code– Resources– People– Time
![Page 12: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/12.jpg)
12 www.ExigenServices.com
Don’t forget communication tools
Continuous integration/build automation Team collaboration/task/bug tracker/report builder (Jira, TFS) Meeting culture/Scrum Meetings/Sprint Pulse Skype/Video facilities Webex/Screen sharing Airplane Beer
![Page 13: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/13.jpg)
13 www.ExigenServices.com
Totally Integrated Example
![Page 14: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/14.jpg)
14 www.ExigenServices.com
Flexible Scrum Example
![Page 15: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/15.jpg)
15 www.ExigenServices.com
So… if you face distributed one
Max attention to communication, visual, personal More beer if necessary, start with team building Know your type of Distributed Agile, plan additional roles Use Kanban principle to balance the load and avoid the
bottlenecks on specific roles Use Sprint Pulse to manage the meeting and communication
overhead level and team communication Peers speak with peers, is your SMs do not talk to each other –
you are in trouble Calculate the Load Factor – it will be different from type to type
![Page 16: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/16.jpg)
16 www.ExigenServices.com
Plan to decrease the distribution score
Try 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 project
And…know and practice Agile from beginning to end, better practice lower distribution level Agile before (by you or get expertise in your company).
![Page 17: Scrum distribution risk score](https://reader036.vdocuments.us/reader036/viewer/2022081414/54b520164a79595e1c8b457b/html5/thumbnails/17.jpg)
17 www.ExigenServices.com
Thank you.
Question time.