Scrum and Kanban 101

(1)

Scrum and Kanban

(2)

www.bebetterleader.com

(3)

What are your

(4)

What are the differences

between

(5)

What do you

(6)

Defined

Do

Check

Act

Plan

Empirical

(7)

(8)

(9)

Sub-optimization System optimization

(10)

(11)

Command and control

_{Self-management}

(12)

(13)

Paper

Airplane

(14)

Flavio Steffens de Castro, author of

www.agileway.com.br

Rafael Prikladnicki, professor from PUCRS

and agile coach and trainer

www.inf.pucrs.br/~rafael

Aut

hor

(15)

Split into teams Go!

We will build paper airplanes

Iterations and re-planning of 2 min each Line production concept

The plane starts in an edge and ends in the other The engineering of production is a team decision Teams are not allow to stock sheets for production

The product (airplanes) MUST conform with the scope defined If a product doesn‘t pass the final quality review, it will not be accepted in the iteration

Products that are unfinished can be used in the next iteration to be complete

Every team will represent a factory (with logo)

Bas

ic rul

es

(16)

The Air Force is planning to buy some new airplanes

The agent of the Air Force (me) contacted your factories to check for your proposals

I want to know how many airplanes you can deliver in TWO minutes

Since I am very impatient, you have ONE minute to discuss and inform the number of airplanes you produce in a TWO minute iteration

Start!

The b

egi

(17)

The Air Force liked the estimates and will open a competition You will have TWO minutes to produce a prototype. The scope is:

Must have 12 windows Must have a fly cabin

Must have the logotype of your company on both wings Must fly across table (~2 meters)

The prototype will be shown to the group.

(18)

(19)

Ins

tructi

(20)

The winner :

Deliver more airplanes

Deliver the quantity as promised

4 iterations of 2 minutes to produce the planes

2 minutes at the end of each iteration to check and act about your production line, to increase productivity.

You will give the estimates in the beginning of each iteration.

Pr

epar

ation

(21)

Client (me)

Gives the scope and approves each produced airplane

Team leader

The leader can‘t build the airplanes.

The leader should care the team, help to check/act the process, remove impediments and get the material.

Team

Produce the airplanes and check/act the process.

Select a Team leader!

(22)

Act/check time (2 minutes):

Number of planned to finish planes

Agree/improve work process

Start!

Work time (2 minutes):

Number of planned to make planes

Produce the planes

Start!

Show time

Count planes (done)

Repeat

Ite

rat

(23)

(24)

Did you get what the client wanted in the beginning?

Did the prototype help? Why?

Did the estimates got better with time? Why?

Was the concept of inspect/adapt useful? What was

the most useful?

Did team leader help? How? Who made decisions?

What is better for you and the client:

Deliver all the airplanes in 10 minutes?

Deliver a % of airplanes each 2 minutes?

Ret

ros

pec

(25)

You had just lived an Agile Process!

The teams became motivated and self-managed

The team leader worked for the team

The work process became more efficient and organized

in iterations

The communication became strong and powerful

You inspected and adapted, through iterations!

(26)

Do you have any

(27)

(28)

Individuals and interactions

over

(29)

Working software

over

(30)

Customer collaboration

over

(31)

Responding to change

over

(32)

Do you have any

(33)

(34)

(35)

5 principles

1. Deliver every sprint

2. Team decides everything

3. Inspect and adopt everyday

4. Define chief impediments removal

(36)

3 roles

1. Scrum master

2. Product owner

(37)

Scrum master

1. Enforces the Scrum rules

2. Facilitates all Scrum meetings

3. Shields the team from external interference

4. Leads the team to be self-organized and to

continuously improve

5. Coaches and supports PO

6. Removes impediments

(38)

Product owner

1. Envisions the product

2. Is the only one responsible for Product backlog

3. Is responsible for the product’s profitability

4. Decides on release date and content

5. Accepts or rejects work results

6. Collaborates with both the team and stakeholders

(39)

Team

1. Self-organizing

2. Cross-functional with no roles

3. _{7± 2 members}

4. Responsible for meeting their commitments

5. Authority to do whatever is needed to meet

commitments

(40)

(41)

Sprint planning

1. PO presents top priority Product Backlog items

2. Team selects the amount of Backlog for the

upcoming Sprint

3. Acceptance criteria are negotiated and clarified

4. Sprint Goal is defined

(42)

Sprint planning

1. Team participates while PO’s available

2. Team breaks items into tasks to form the

Sprint Backlog

3. Involves detailed design

4. Team makes commitment for the Sprint

(43)

Daily scrum

1. What have you completed since last meeting?

2. What will you complete before next meeting?

3. What is in your way?

(44)

Sprint review

1. Team presents the “Done” work and “Undone”

work

2. Get feedback from the Product Owner and

Stakeholders

3. Update Product Backlog and release Burndown

chart

(45)

Sprint retrospectives

1. Scrum Team inspects the last sprint regarding

people, relationships, processes and tools

2. Scrum Team identifies possible improvements

and agrees on the measures for next Sprint

3. Scrum Team may update its own working

agreement

(46)

(47)

Do you have any

(48)

(49)

3 rules

1. Visualize workflow

(50)

Kan

(51)

Do you have any

(52)

Scrum and Kanban

(53)

Scr

um

Product creation

Rhythm

Frozen backlog

1 backlog : 1 team

Any size tasks

Board restarts

Manufacturing

Flow

Event-driven

1 board : n teams

Similar sized tasks

Persistent board

Ka

nb

an

(54)

Scrum and Kanban

(55)

Scr

um

Ka

nb

an

Pull scheduling

Limit WIP

Transparency

(56)

Do you have any

(57)

Have we met

(58)

Do you have any

(59)