scaling scrum-mega-framework

36
SCALING SCRUM STEP BY STEP: “THE MEGA FRAMEWORKRafael Maranzato, MSc Marden Neubert, MSc Paula Herculano, MSc Universo Online S.A – http://www.uol.com.br UOL R&D Department São Paulo, Brazil

Upload: drewz-lin

Post on 01-Dec-2014

576 views

Category:

Documents


1 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Scaling scrum-mega-framework

SCALING SCRUM STEP BY STEP:

“THE MEGA FRAMEWORK”

Rafael Maranzato, MSc

Marden Neubert, MSc

Paula Herculano, MSc

Universo Online S.A – http://www.uol.com.br

UOL R&D Department

São Paulo, Brazil

Page 2: Scaling scrum-mega-framework

Background

• UOL R&D department develops products and

services for Brazilian Internet users

– Before 2006: used a RUP-based development

process with teams organized per function

– 2007: some teams were organized per product,

with different functions in each team

– 2008: started using Scrum

– 2010: started scaling Scrum

Page 3: Scaling scrum-mega-framework

My experience with Scrum

• First ScrumMaster in the company

• Helped other teams to use Scrum

• Gave introductory training in the company

• Became Product Owner after one year

• Started scaling Scrum in a live system

Page 4: Scaling scrum-mega-framework

Case study: leading online payment

system

• Tried to use Scrum for more than one year,

and failed (previous paper at SPLASH’11)

• Returned to Scrum and scaled it using “The

Mega Framework”

Page 5: Scaling scrum-mega-framework

Sprint Planning

Daily Scrum & Work

Product Increment

Sprint Review

Sprint Retrospective

Update Product Backlog

The Mega Framework

• Additional layer to Scrum framework

Sprint Planning

Daily Scrum & Work

Product Increment

Sprint Review

Sprint Rerospective

Update Product Backlog

Scrum

Framework . . . . . . Scrum

Framework

Page 6: Scaling scrum-mega-framework

The Mega Framework

• Set of practices and meetings

• It provides synchronization in all levels

Teams

ManagementStakeholders

Page 7: Scaling scrum-mega-framework

The Mega Framework

• Motivated by a huge backlog

– One Scrum team was not enough

• Growing revenues and competitive product

Page 8: Scaling scrum-mega-framework

The Mega Framework

• Challenge: how to synchronize and scale

Scrum with multiple teams keeping agility

– Created an additional framework above the

Scrum framework

• Started with 2 teams in 2010 and now we

have 10 teams (7 published in the paper)

Page 9: Scaling scrum-mega-framework

Team evolution

Phoenix

Tucson

Salvador

Istambul

Hanoi

Curitiba

Galápagos

Monte Azul

Manchester

Bruxelas

Tucsonja

n/0

8

ma

r/0

8

ma

i/0

8

jul/

08

set/

08

no

v/0

8

jan

/09

ma

r/0

9

ma

i/0

9

jul/

09

set/

09

no

v/0

9

jan

/10

ma

r/1

0

ma

i/1

0

jul/

10

set/

10

no

v/1

0

jan

/11

ma

r/1

1

ma

i/1

1

jul/

11

set/

11

no

v/1

1

jan

/12

ma

r/1

2

ma

i/1

2

jul/

12

set/

12

Page 10: Scaling scrum-mega-framework

The Mega Framework

Strategy

Framework

1. Feature teams

2. Mega Backlog

3. Grow, then split

4. Hiring and ramp up

5. Sprint length

6. Teams per release

7. Values instead of rules

8. Development environment

9. Continuous improvement

1. Mega Planning

2. Mega Stand-up

3. Mega Retrospective

4. Sprint Reviews

5. Weekly Pre-Planning

6. Weekly Product Owner and ScrumMaster

meeting

7. Regular Mega meetings with business area

8. Knowledge sharing

Page 11: Scaling scrum-mega-framework

Strategy

1. Feature teams

2. Mega Backlog

3. Grow, then split

4. Hiring and ramp up

5. Sprint length

6. Teams per release

7. Values instead of rules

8. Development environment

9. Continuous improvement

Page 12: Scaling scrum-mega-framework

1) Feature teams

• Teams focused on features instead of

software components

• Multiple teams, but one big team

• Scalability, refactoring and other engineering

practices are solved by feature teams

Page 13: Scaling scrum-mega-framework

2) Mega Backlog

• High-level features

• Prioritization of feature teams

– New teams

– Change focus of existing teams

Page 14: Scaling scrum-mega-framework

3) Grow, then split

• Add people to existing teams before creating

new ones

• Knowledge in the product is shared

• Motivational factor � opportunities

Page 15: Scaling scrum-mega-framework

4) Hiring and ramp up

• Strict hiring process

• Written test and interviews

• Skills instead of technologies

• After hired, evaluated by the team

Page 16: Scaling scrum-mega-framework

5) Sprint length

• 3-week length � 4-week length

• It is better to synchronize agendas

• Timeline will be shown at the end

Page 17: Scaling scrum-mega-framework

6) Teams per release

• Releases every week– Merge code too

• Each feature team releases once a month

• Group related teams to release together

Page 18: Scaling scrum-mega-framework

7) Values instead of rules

• Agile development is not a set of rules � it is

based on values

– Commitment, transparency and teamwork are

more important than the process

• Communication is a key factor to synchronize

multiple teams

Page 19: Scaling scrum-mega-framework

8) Development environment

• Each feature team has its development

environment

• They share just one pre-production

environment

Page 20: Scaling scrum-mega-framework

9) Continuous improvement

• We know it is a key factor to move on

• Team members contribute to improve the

process

• Everything can be improved!

Page 21: Scaling scrum-mega-framework

Framework

1. Mega Planning

2. Mega Stand-up

3. Mega Retrospective

4. Sprint Reviews

5. Weekly Pre-Planning

6. Weekly Product Owner and

ScrumMaster meeting

7. Regular Mega meetings with business

area

8. Knowledge sharing

Page 22: Scaling scrum-mega-framework

1) Mega Planning

• Occurs after Sprint Plannings of teams in the same release

• ScrumMasters and one tech leader of each feature team

– in the beginning, everybody was invited

• We continue to improve this very important meeting

Page 23: Scaling scrum-mega-framework

2) Mega Stand-up

• In the middle of the Sprint, with all the team

members of the release

• The goal of this meeting is just to synchronize

the teams

Page 24: Scaling scrum-mega-framework

3) Mega Retrospective

• Every six months

• Captures global impediments that can be

hidden in local retrospectives

Page 25: Scaling scrum-mega-framework

4) Sprint Reviews

• Uses the pattern of single Scrum teams

• Besides the team and stakeholders, we invite

one member of each feature team

• We don’t have a Mega Review

Page 26: Scaling scrum-mega-framework

5) Weekly Pre-Planning

• Attendance is Product Owners and

stakeholders

• Product Owners show the prioritized backlog

• Two days before each Sprint Planning

Page 27: Scaling scrum-mega-framework

6) Weekly Product Owner and

ScrumMaster meeting

• Agenda: impediments, main features planned, changes, pending issues, corporate policies and decisions

• High level of synchronization

• One of the most important meetings of this framework

Page 28: Scaling scrum-mega-framework

7) Regular Mega meetings with

business area

• At the beginning, it was more often

– Nowadays, just once a month

• Agenda: pending issues, problems and new opportunities to the product

• Synchronization among Product Owners, stakeholders and management

Page 29: Scaling scrum-mega-framework

8) Knowledge sharing

• Every week

• Team members are responsible for the

agenda

• Encouraged by Product Owners and

ScrumMasters

Page 30: Scaling scrum-mega-framework

Before timeline

• 7 teams

• Group related teams per release

– Release I: Team A & B

– Release II: Team C

– Release III: Team D & E & F

– Release IV: Team G

Page 31: Scaling scrum-mega-framework

The Mega Framework: TimelineMonday Tuesday Wednesday Thursday Friday

Planning A Mega Planning

A & B

Mega Stand-up

A & B

Review A & B

Release A & B Retrospective

A & B

Planning C

Review C

Release C Retrospective

C

Planning D Mega Planning

D & E & F

Mega Stand-up

D & E & F

Review F

Release D & E & F Retrospective

D & E & F

Planning G

Review G

Release G Retrospective

G

Pre-Planning A & B

Pre-Planning C

Pre-Planning D & E & F

Pre-Planning G

Weekly PO/SM

Weekly PO/SM

Weekly PO/SM

Weekly PO/SM

Knowledge Sharing

Knowledge Sharing

Knowledge Sharing

Knowledge Sharing

Planning A

Week

1

2

3

4

5

Planning B

Review E

Review D

Planning E

Planning F

Planning B

Page 32: Scaling scrum-mega-framework

Where we are right now

• 10 feature teams

• Adapting Mega meetings

• Planning to have more teams in 2012 and 2013

– And studying how to customize the framework to fit

it in the timeline

Page 33: Scaling scrum-mega-framework

Challenges and problems

• Rollbacks and mistakes from one release

affect the calendar and releases of others

• How to deal with more than one release per

week

– What is the limit of that timeline?

– Of course, we will learn and adapt

Page 34: Scaling scrum-mega-framework

Conclusion

• We presented a framework to scale Scrum

– Strategy

– Framework itself

• Synchronization in all levels

• There is always room for improvement

Page 35: Scaling scrum-mega-framework

QUESTIONS?

[email protected]

Page 36: Scaling scrum-mega-framework

THANK YOU!

[email protected]