SELF-DESIGNED !
TEAMS!
at BMW

30.06.14 © valtech gmbh

1

SELF-ORGANIZED TEAMS AT BMW!

MARK BREGENZER
Principal Consultant
Agile Methodology
Agile Experience:! Agile Coach at Valtech since 2011
! Agile Coach since 2009
! Certified Scrum-Master since 2007

Software development Experience:! Since 1997 as developer, leaddeveloper, subproject leader…
Telecommunication and automotive
30.06.14 © valtech gmbh

2

SELF-ORGANIZED TEAMS AT BMW!

Agenda! Project history! Motivation for reorganization! Motivation for self-organization! Self-designing team workshop! Workshop reflection30.06.14 © valtech gmbh

3

Project history!

PROJECT STARTS IN FEBRUARY 2012!

About 11 project members
One team, cares for everything
features, continuous integration,environment...
Team consists of:
One PO, two PO Supporter, fiveto six Developer, Scrum-Master
Plus Project Manager andAgile CoachA
Requestor

PO

PO-S

PO-S

SM

Feature, Architecture & CI

Exploration phase for twomonths, then scaling starts

30.06.14 © valtech gmbh

4

Project history!

SCALING THE PROJECT UNTIL SEPTEMBER 2012!

About 60 project members
Four interdisciplinary area/componentteams
One cross cutting teams!
!

Continuous integration
Build governance (BMW architecture,BMW standards…)

One Project management team andagile coaches
One Scrum-Master for two teams
Adding team after team every twosprints
Project deals with about 30 externalinterfaces directly, even more indirectly

30.06.14 © valtech gmbh

A
Requestor

PO

PO-S

PO-S

PO

SM

PO-S

Component A

PO

PO-S

PO-S

Component B

PO

SM

PO-S

Component C

PO

SM

PO-S

SM

PO-S

Component D

PO-S

PO-S

SM

Architecture & CI

5

Project history!

PROJECT STRUCTURE AT JANUARY 2013!

About 80 project members

POFour interdisciplinary area/component teams

Build-GovernanceThree cross cutting teams!
!
!

Continuous integration
Defect- and test management
Build governance (BMW architecture,BMW standards…)

One project management team andagile coaches

ARequestor

PO

PO-S

PO-S

SM

PO

PO-S

Component A

PO

PO-S

PO-S

SM

PO-S

Component B

SMPO

PO-S

Component C

SM

PO-S

Component D

One Scrum-Master for two teams
POSM

Test Management

30.06.14 © valtech gmbh

PO

PO-S

SM

Continuous Integration

6

Project history!

PROJECT STRUCTURE AT JUNE 2013!

A second requestor

PO

About 100 project members

PODesign-GovernanceFour interdisciplinary area/
component teams

Build-GovernanceAB

Requestor

Requestor

Four cross cutting teams!
!
!
!

Continuous integration
Defect- and test management
Build governance (BMW architecture,BMW standards…)
Design governance (Businessclarification, release planning…)

One project management team andagile coaches
One Scrum-Master for two teams

30.06.14 © valtech gmbh

PO

PO-S

PO-S

Component X

PO

PO-S

PO-S

SM

PO

PO-S

Component A

PO

PO-S

SM

Component B

PO-S

SM

PO

PO-S

Component C

PO

PO-S

PO-S

SM

Component D

SM

Test ManagementPOPO-SSM

Continuous Integration

7SMMotivation for reorganization!

NEED FOR ACTION & UPCOMING CHALLENGES!
(JANUARY 2014) !

Current project structure is an impediment for future releases•••

Next release is focused on requestor B
Capacity of one team for all requests from requestor B is not sufficient
The project has still to serve requestor A

Unbalance between backlog priorities and capacity of the teams
Agile and engineering practices differs between the teams
Some teams got their routines, feel comfortable
Some severe social problems appeared
Renew one-team spirit30.06.14 © valtech gmbh

8

Motivation for self-organization!

MANAGEMENT APPROACH OR SELF-ORGANIZATION?!

The project management was going to set up the new organization
But…
After announcing that the project is going to be reorganized, we
received a lot of resistance••••Some team members lurked to leave the project
Others predicted the efficiency/performance will dropSome leading project members tried to influence the project management to skip
their team from the reorganization
Even after explaining this will be done by a self-designing team workshop, someteams predicted they will stay togetherIt‘s difficult to solve severe social problems from “outside“ withoutcompromising
Motivation grows by self-determination

30.06.14 © valtech gmbh

9SELF-ORGANIZED TEAMS AT BMW!

WORKSHOP AGENDA!

Management joined
beginning and end of theworkshop only
Management explained theProject vision and workshop
targets
About 80 participants incl.
crosscutting teams

30.06.14 © valtech gmbh

Dura%on	   Topic	  00:10	   Introduc-on/agenda	  00:05	   Project	  targets	  &	  vision	  00:15	   Presenta-ons	  crosscu9ng	  teams	  00:10	   Introduc-on	  ReOrg	  process	  &	  mo-va-on	  00:20	   Opening	  prac-ce:	  *	  Build	  a	  ship	  *	  Group	  according	  to	  tech.	  skills	  *	  Group	  according	  to	  business	  skills	  01:40	   ReOrg	  process:	  *	  3	  Itera-ons	  35	  min.	  incl.	  Review	  *	  Less	  -me	  for	  itera-on	  2	  &	  3	  *	  Break	  between	  itera-on	  2	  and	  3	  (10	  min.)	  00:20	   Closing	  ReOrg	  process:	  Find	  team	  names,	  ﬁnd	  team	  room,	  vote	  Lead	  Developer/Scrum-­‐Master	  00:15	   Team	  presenta-ons	  00:15	   Closing:	  common	  ac-vity	  and	  one	  word	  feedback	  03:30	  10Self-designing team workshop!

PROJECT TARGETS AND VISION!

Targets
Get more flexibility in working
on different backlog items
Push project effectivity
Renew one-team spirit
Increase motivation	  	  	  30.06.14 © valtech gmbh

Vision:	  Every	  feature	  team	  should	  be	  able	  to	  work	  on	  their	  own	  on	  every	  backlog	  item	  independent	  from	  the	  requestor	  11Self-designing team workshop!

PRESENTATION CROSSCUTTING TEAMS!

Each crosscutting team got three minutes to present their team to…
...explain what they do and what they won‘t do in the project...campaign for new team members	  	  30.06.14 © valtech gmbh

12

Self-designing team workshop!

OPENING PRACTICE!

Create one-team spirit•

All participants form a ship

Requestor B

Mix up the people, make visible
what they know/prefer•

Group according to tech. skills•

Group according to business skills

Product
Process Model
Customer

Requestor A

30.06.14 © valtech gmbh

13

Self-designing team workshop!

Rules!

The new project team should match the vision as much as possible
Due to contract issues, crosscutting teams remain in their structure/size but
swap of single team members is possible
5 feature teams
team container with 1 PO, 2 PO Support, 6-7 Developer
Each feature team has to have at least one internal Developer from thesubcontractor
Teams appoint their lead developer (main contact to Build-Gov. team) and a
Scrum-Master
Product Owner, Product Owner Support and Developers find themselves on
their own as teamProject management will accept every organization as long as it matches
these rules

30.06.14 © valtech gmbh

14

Self-designing team workshop!

Skill cards / avatars!

Makes it easy to see available skills during the team setup phases
Represents absent team members

30.06.14 © valtech gmbh

15

Self-designing team workshop!

TEAM CONTAINER!

Flip charts for all teams

30.06.14 © valtech gmbh

16

Self-designing team workshop!

REORGANIZATION PROCESS: ACTIVITIES!

Dura%on	  00:20	  Topic	  1.	  Itera-on	  ﬁnd	  teams	  00:15	  review	  00:20	  2.	  Itera-on	  improve	  teams	  00:10	  review	  00:10	  Break	  00:15	  3.	  Itera-on	  improve	  teams	  00:10	  review	  01:40	  30.06.14 © valtech gmbh

17

Self-designing team workshop!

REORGANIZATION PROCESS: FINDING TEAMS PHASE!

Every	  workshop	  par-cipant…	  …interviews colleagues…asks for new team member…pins skill card at teamcontainer.…?
bla bla...

yes!

30.06.14 © valtech gmbh

18

Self-designing team workshop!

REORGANIZATION PROCESS: REVIEW PHASE!

Every workshop participant…
…can move from team to team…checks if the team matchesthe vision…posts defects at the teamboard if needed

30.06.14 © valtech gmbh

Too many
PO Supporter
MissingDeveloper withrequestor Aknow-how

Lack ofdeveloper
capacity

Missingcustomer
know-how19

Self-designing team workshop!

ITERATION INSIDES!

First iteration
First newly formed teams
One component team (let’s call it team black) remains nearly unchanged
Second iteration
Teams tried to solve their defects and asked for support from team black
Further team members were leaving team black, less were joining
Team black was not complete
Other teams tried to keep their team membersSomehow the reforming process stagnated	  30.06.14 © valtech gmbh

20

Self-designing team workshop!

ITERATION INSIDES!

BreakAll participants had to leave theroom

POPO

Design-Governance

PO

PO-S

Third iteration
Participants were refreshed, got
new energy
All teams helped to solve the lastdefects and especially in teamblack
After solving the last defect thewhole team jubilated	  30.06.14 © valtech gmbh

Build-Governance

SM

PO-S

PO

PO-S

Feature team

PO

PO-S

PO-S

SM

PO-S

Feature teamA

B

Requestor

Requestor

SMPO

Feature team

PO-S

PO-S

Feature teamPOPO-SPO-S

SM

Feature team

POSM

Test Management

POPO-S

SM

Continuous Integration

21SMSelf-designing team workshop!

Closing Reorganization Process!

Find a team nameFind a team room
Vote for Lead Developer
Vote for Scrum-Master

Team Name Scheme
Bands
Mountains
StarsColors

30.06.14 © valtech gmbh

22

Self-designing team workshop!

Closing Reorganization Process!

Explaining how to work in next sprint
Uncompleted user stories remain with their developers
and move into the new teamPOs and PO Supporter keep their responsibilities/interfaces at first
Subject Matter Experts are no longer dedicated to one teamDefects under work remain with their developers
and move into the new teamDefects not touched yet, remain assigned to old team and get pulled bynew teams“test management” team escalates not taken defects from time to time

30.06.14 © valtech gmbh

23

Self-designing team workshop!

TEAM PRESENTATIONS TO MANAGEMENT!

30.06.14 © valtech gmbh

24

Self-designing team workshop!

Closing & Feedback!

Closing the workshop as
one-team

niceTeam activity
One word feedback

well done!
feels goodgreatexperiencecool

motivatedinteresting

30.06.14 © valtech gmbh

25

Workshop reflextion!

SUMMARY!

Very positive mood, energy and motivation after the workshop
Everyone was satisfied with his new team, even not joining teammembers were happy with their new teams
The one-team exceeded the management expectations
All feature teams are able to work on each backlog item independent
from the requestor
Social problems seemed to be solved
One self-designing team workshop is only a great start.
Therefore we offered all teams to do a team building workshop. Due toproject circumstances and vacation situation these workshops start in July.

30.06.14 © valtech gmbh

26

SELF-ORGANIZED TEAMS AT BMW!
!

SPECIAL THANKS!

Edward Dahllöf
Nils Bernert
Josef Scherer

30.06.14 © valtech gmbh

27

sBahnstraße 1640212 DüsseldorfTel: +49 211 179 237-0Fax: +49 211 179 237-19
Winzererstraße 47d80797 MünchenTel: +49 89 307 668-0Fax: +49 89 307 668-123
Werner-Heisenberg-Straße 263263 Neu-IsenburgTel: +49 6102 884 68-0Fax: +49 6102 884 68-28

TEAM

MARK BREGENZER
Principal Consultant+49 172 2 855 788
mark.bregenzer@valtech.devaltech.de