scrum scalability: advanced techniques for managing distributed agile teams

Scrum Scalability: Advanced Techniques for Distributed Agile

TeamsWed Sep 17th at 1: 00pm PT | 4:00pm

ET

Webinar

www.belatrixsf.com

PANELISTS

Hubert SmitsCertified Scrum Trainer & Scrum Coach

Juan Pablo CalvoProject Lead & Certified ScrumMaster

SCRUM AND SCALED SCRUM

Quick overview

SCRUM

www.craiglarman.comwww.odd-e.com

© c. larman & b. vodde 2008, all rights reserved

SCRUM | FEW TEAMS

www.craiglarman.comwww.odd-e.com

© c. larman & b. vodde 2008all rights reserved

TEAMS OF TEAMS

www.craiglarman.comwww.odd-e.com

© c. larman & b. vodde 2008

all rights reserved

LARGE TEAM EXAMPLE

Program Director

Off-Shore

Onyx (billing)

Flintstone (billing)

Jade (policy)

Obsidian (common)

Emerald (BI)

Quartz (test automation)

Near-Shore

Amatista (claims)

Oro (claims)

Team 3 (claims)

Team 4 (claims)

On-Shore

Core (core platform)

Tuff (UI platform)

Dilitium (modeling)

Fluorite (docs)

Tourmaline (User Experience)

QA Product Owners

Architecture Billing / Policy

Common / Claims

LA

RG

E T

EA

M E

XA

MP

LE

Near-Shore (PM)

Amatista (claims)

Diana

Sudeep

Ariel

Carolina

Lucas

Javier

M.D.

Juan Pablo

Cristian

Oro (claims)

Ruben

Wade

Nestor

Francisco

Abel

Gillermo

Elina

Mariano

Diego

Zafiro(claims)

Diana

Sree

Sebastian

Leandro

Evangelina

Miquel

Gonzalo

Fransisco

Nahuel

Esmeralda (claims)

Ruben

Senthil

Ale

Javier

Guillermo

Jose

Santiago

Marta

Diego

Near-Shore (Jose)

Julieta (Lead QA/PM)

ScrumMaster

ApplicationArchitect

LeadDeveloper

Developer

Lead QA

QA

DASHBOARD

STRUCTURE

ALIGN THE PEOPLE: RELEASE PLANNING

release planning meeting• review product backlog• add missing features• move features to the right sprint• find and solve dependencies

product backlogprioritized features

desired byproduct owner

release

2-4 months

productfeatures shipped to (internal) customer

release backlogordered features

desired by product owner

based on: Five levels of planning by Hubert Smits

ALIGN THE PEOPLE: SCRUM OF SCRUMS

9:00am9:15am

9:15am9:30am

9:15am9:30am

9:45am10:00am

Denver Team

scrum

Mendoza team

scrum

Lima team

scrum

scrum of

scrums

SUMMARY

• Delivered 152 StoryPoints during Sprint• Concluded Billing work• Sprint challenges for performance and quality:

– Drop in Off-Shore velocity (20%) caused by defects detected during acceptance– Increasing Off-Shore defects (39 this Sprint, 50% increase)– Less then expected Near-Shore velocity – expectations not set right

• Switching 1 Off-Shore team from Policy to Claims, may not be enough for Claims to reach targets for 2018

• Decision on CWS re-use: There is agreement that PO and Architects feel it will be less work overall to provide new IIP services rather than attempt to work with the existing code

• Hiring: near shore app architect & lead core architect in progress• Testing – process re-evaluated and modified for all teams

BUDGET

• March development actuals: $ 777,390 ($ 198,948 below budget of $ 976,338 )

• March product management actuals $ 113,179($ 27,584 over budget of $ 85,595)

• 2018 Forecast– 2018 Dev: $ 9,346k (-/- $ 1,445k)– 2018 Prod: $ 905k (+/+ $ 15k)– 2018 Total: $ 10,251k (-/- 1,430k)

PROJECT RISKS

• Calendar time is our single biggest challenge• Moving 1 team to Claims may not be enough to meet year-

end objectives (vs. jeopardizing Policy & Portal)• Attrition and retention in GHT and InsBroker• Quality & performance challenges in GHT teams (impact of

SLAs)• Ramp-up in SouthSoft teams slower than projected• Potential Claims backlog readiness upon full velocity• Technical unknowns based on Architecture Analysis

FIVE LEVELS

CADENCE

THANK YOU

Belatrix Software

@BelatrixSF

HubertSmits

@HubertSmits