Scrum @ Comparisons The Big Retrospective€¦ · Presentation 1 from their Scrum ... Meeting PO Team ScM PM Remarks ... Big Retrospective – Agile Breakfast Scrum Master has to

Scrum @ Comparisons

The Big Retrospective

25.08.2015, Seite 1

Scrum @Comparisons Big Retrospective – Agile Breakfast Before I start…

25.08.2015, Seite 2

Company:

comparis.ch

Department “Comparisons”:

8 Business people

8 Developers

Me:

Dejan Milosavljevic

Scrum Master & Head of Software Development

25.08.2015, Seite 3

Agenda

Scrum @Comparisons Big Retrospective – Agile Breakfast Agenda

25.08.2015, Seite 4

Part 1 – How we introduced Scrum? (10 Min.)

Part 2 – Jump Start & Learning to Walk… (10 Min.)

Part 3 – Be patient, be patient… (10 Min.)

Part 4 – The big retrospectives and the world today (20 Min.)

Part 5 – Questions & Discussion (10 Min.)

Scrum @Comparisons Big Retrospective – Agile Breakfast Part 1 – How we introduced Scrum

25.08.2015, Seite 5

1 day workshop outside the

company

Entire department took part

The Agenda was open

During the day we defined dozens

of actions

Output: around 10 concrete

actions to implement in the next 2

months

One of them was to learn what

scrum is

In December 2013…

Scrum @Comparisons Big Retrospective – Agile Breakfast Part 1 – How we introduced Scrum

25.08.2015, Seite 6

Another department in the

company already worked with

scrum

Presentation 1 from their Scrum

Master

Presentation 2 from their Product

Owner

Department meeting no. 1 to

decide about scrum

Department meeting no. 2 to

decide about scrum –

YES we decided to try it!

In January 2014…

Scrum @Comparisons Big Retrospective – Agile Breakfast Part 2 – Jump Start & Learning 2 walk

25.08.2015, Seite 7

But where have we been at that

moment?

Consciousness & desire were

now awake in the team!

We engaged external coaches to

helped us

2 days jump start training

1 day sprint planning

… and we were in sprint 1!

In March 2014…

Scrum @Comparisons Big Retrospective – Agile Breakfast Part 2 – Jump Start & Learning 2 walk

25.08.2015, Seite 8

Our new organization had:

2 scrum teams (mixed with

developers and product

managers)

2 POs

1 Scrum Master

1 Head of Department (outside

the scrum organization)

Scrum @Comparisons Big Retrospective – Agile Breakfast Part 3 – Be patient, be patient…

25.08.2015, Seite 9

2014 Apr. Mai Juni Juli Aug. Sept. Okt. Nov. Dez. Jan. Feb. März

Team Djokers 1 2 3 4 5 6 7 8 9 10 11 12 13

14 15 16 17 18 19

Team Looney Tunes 1 2 3 4 5 6 7 8 9 10 11 12 13

Change the sprint

length!

Impediments!

(UX, external)

We did not commit

the go live!

Summer vacation &

time to think…

The

big retrospective

The retrospective

really hurts!

25.08.2015, Seite 10

«BIG» Retrospective 1

October 2014

Scrum @Comparisons Big Retrospective – Agile Breakfast

Part 4 – The big retrospective and the world today

25.08.2015, Seite 11

The big retrospective

(feedback from 14 members of the department)

Number of unique

team members voted

for listed actions

Highlighted are the

top votes from team

members

Row Labels Sum of Unique

Actions 31

Bads 48

Goods 41

Transparency 10

Team/Organization/Cooperation 7

Know how exchange 6

Effectiveness 5

Sprint Goal 4

Sprint Length 3

External Cooperation 2

Others 1

Two Team Approach 1

Communication 1

Story Quality 1

Grand Total 120


Actions 31

Bads 48

Overhead 7

Two Team Approach 5

PM Resources 5

Waterfall over Scrum 4

Story Quality 4

Flexibility 4

Kanban / Deployment / Daily Business 3

Big picture vs. Small picture 3

Others 2

Team Atmosphere 2

Estimations 2

Orange Tasks 2

Tech Stories 1

Personal Motivation vs. Team Motivation 1

Effort being lost 1

Quality 1

PM Responsibility 1

Goods 41

Grand Total 120


Actions 31

Meeting Reorganization 6

Tech Stories / Coding Standards 5

One Team 5

Story Writing Workshops 4

PM as Stakeholder 4

Others 3

Testing / Quality 2

Improve Estimations 1

Become more Agile 1

Bads 48

Goods 41

Grand Total 120



8/25/2015, Seite 12

A) Facilitate the role of “Story Owner”

Empower the stakeholders

Distribute responsibility

B) Merge the scrum teams into one pure

development team

C) Keep business and development

strongly connected

PM responsible for single stories

PM are interested that their stories do:

fulfill DoR

are well tested

fulfill DoD and acceptance criteria

D) Keep business work visible to the entire

department (create Kanban boards?)

E) Release plans (quarterly)


Actions 31



One Team 5


PM as Stakeholder 4


Actions 31

Bads 48

Goods 41

Transparency 10

Team/Organization/Cooperation 7

Know how exchange 6

Effectiveness 5

Sprint Goal 4

Sprint Length 3



8/25/2015, Seite 13

PO Story Owner

PM


Actions 31



One Team 5


PM as Stakeholder 4

Others… 3



8/25/2015, Seite 14

PO

SO SO

Pro

du

ct

Resp

on

sib

ility

Sto

ry

Ow

ne

rsh

ip

Deta

iled K

now

ledge

Custo

mer P

roxim

ity

Sco

pe

of

De

cis

ion


Actions 31



One Team 5


PM as Stakeholder 4

Others… 3



8/25/2015, Seite 15

Meeting PO Team ScM PM Remarks

Pre-planning X X X X

Planning 1 X X X X² ²available

Planning 2 X X

Daily X X X¹ ¹passive

Review X X X X

Retro X X X X


Actions 31

Meeting Reorganisation 6


One Team 5


PM as Stakeholder 4

Others… 3



25.08.2015, Seite 16

2014 Apr. Mai Juni Juli Aug. Sept. Okt. Nov. Dez. Jan. Feb. März

Team Djokers 1 2 3 4 5 6 7 8 9 10 11 12 13

14 15 16 17 18 19

Team Looney Tunes 1 2 3 4 5 6 7 8 9 10 11 12 13

2 TECH sprints without

business stories

Release plans!

Merged teams into

one scrum team



25.08.2015, Seite 17

Vacation plan

Sprint goals &

release plan

Operational tasks

Deployment plan Portfolio

management



8/25/2015, Seite 18

Challenges to address after first big retrospective:

Speed up (we learned to walk, now we want to run!)

We started to release after 1-2 sprints new applications

Story writing workshops

The story quality increased significantly since we declared story

ownership more precise

Reduce dependency with externals

UX matrix

Architecture department role and responsibility challenged

Translation department cooperation

Marketing actions in the frequency of sprints

25.08.2015, Seite 19

«BIG» Retrospective 2

May 2015

Scrum @Comparisons Big Retrospective – Agile Breakfast Scrum Master has to say something…

8/25/2015, Seite 20

“BIG” Retrospective 2

I was about to leave the company

We divided the roles of the Scrum Master and Head of Development

Team requested a second “big” retrospective while I was still there

This time we listed all actions online

Every team member could vote for his top 3 actions

The actions defined by the team were mature compared to last year.

Some examples:

Introduce ATDD (acceptance test driven development)

Write user stories together (PMs and developers)

Integrate translation department into the scrum flow


8/25/2015, Seite 21

“BIG” Retrospective 2 – Actions Voting Result


8/25/2015, Seite 22

Quotes from the scrum master

DOs:

Protect the methodology! (do it right or leave it)

Coach people inside your team and department

Don’t be shy, visit other departments and explain how

your department works

Explain it as many times as necessary

Be patient

Protect the team

The team can do much more. Let them do!

Remove or split line management from ScM role

8/25/2015, Seite 23

Questions ? / Discussion

Documents

Scrum @ Comparisons The Big Retrospective€¦ · Presentation 1 from their Scrum ... Meeting PO Team ScM PM Remarks ... Big Retrospective – Agile Breakfast Scrum Master has to