Scrum Scalability: Advanced Techniques for Managing Distributed Agile Teams - PowerPoint PPT Presentation

About This Presentation
Title:

Scrum Scalability: Advanced Techniques for Managing Distributed Agile Teams

Description:

Managing one team with people in different locations is a challenge. But what happens when you have multiple teams in multiple locations working together? How to implement Scrum for large-scale development efforts where projects can involve hundreds of developers and take months or even years to complete? There are some advanced and proven techniques that help you succeed in your large-scale Agile projects. Once again Belatrix13 invites the Agile expert, Hubert Smits to share those techniques, ideas and best practices based on his broad experience. Also, true case studies will illustrate the approach. – PowerPoint PPT presentation

Number of Views:543

less

Transcript and Presenter's Notes

Title: Scrum Scalability: Advanced Techniques for Managing Distributed Agile Teams


1
Webinar
Scrum Scalability Advanced Techniques for
Distributed Agile Teams
Wed Sep 17th at 1 00pm PT 400pm ET
www.belatrixsf.com
2
PANELISTS
Hubert Smits Certified Scrum Trainer Scrum Coach
Juan Pablo Calvo Project Lead Certified
ScrumMaster
3
SCRUM AND SCALED SCRUM
Quick overview
4
SCRUM
5
SCRUM FEW TEAMS
6
TEAMS OF TEAMS
www.craiglarman.com www.odd-e.com c. larman
b. vodde 2008 all rights reserved
7
LARGE TEAM EXAMPLE
8
LARGE TEAM EXAMPLE
ScrumMaster
ApplicationArchitect
LeadDeveloper
Developer
Lead QA
QA
9
DASHBOARD
10
STRUCTURE
11
ALIGN THE PEOPLE RELEASE PLANNING
  • release planning meeting
  • review product backlog
  • add missing features
  • move features to the right sprint
  • find and solve dependencies

release 2-4 months
product features shipped to (internal) customer
release backlog ordered features desired by
product owner
product backlog prioritized features desired
by product owner
based on Five levels of planning by Hubert Smits
12
ALIGN THE PEOPLE SCRUM OF SCRUMS
900am915am
915am930am
915am930am
945am1000am
13
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

14
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)

15
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

16
FIVE LEVELS
17
CADENCE
18
THANK YOU
_at_BelatrixSF
_at_HubertSmits
Belatrix Software
HubertSmits
Write a Comment
User Comments (0)
About PowerShow.com