scrum shuhari

Scrum Shu Ha Ri

Christophe Addinquy

Thank to our sponsors

Thanks to our support sponsors & partners

Media PartnersSupport SponsorSupport Sponsor

Partner Partner Partner

Who Am I ?

✤ Playing with computers for a long time !

✤ Formerly : developer, consultant, trainer, project manager, business analyst, project director

✤ Agile addict since 2001

✤ Now agile coach @ Zenika

✤ Founding member of the French SUG until 2013

Agile, what it’s all about ?

Be agile ≠ Doing agile

Being agile = Becoming agile

Agility is a journey

Agility : a breakthrough

✤ Do = process

✤ Be = culture, mind set

Cynefin model

This is a radical change ! It takes more than one step to embrace it

3 steps

Shu Ha Ri

✤ Shu : Follow the example (learn)

✤ Ha : detach (break the limits)

✤ Ri : Be fluent (create, innovate)

✤ Refer to the Aïkido learning stages

✤ Introduced in the agile community by Alistair Cockburn

Scrum and the agile journey

✤ Not a process, but a «framework»

✤ Our companion during our journey : the Scrum unknown vertu !

✤ Discover the true nature of Scrum !

Scrum Shu

Scrum : Follow the guide !

✤ A simple framework

✤ 3 roles

✤ 2 mandatory artifacts

✤ 4 meetings

✤ 2 cycles

Scrum « by the book »

Scrum : the roles

The Scrum Master

✤Take care of the right Scrum implementation

✤Protect the team

✤Act as a facilitator

The Product Owner

✤Is the master of the backlog

✤Take the decisions about the product

✤Validate the implemented features

The Team

✤Is responsible for the outcome

✤Self organize to make the Sprint items « done »

✤Own all the skills required to achieve its mission

The Sprint recipes

✤ A Planning Meeting at the beginning to organize, set the objectives and the Sprint content

✤ A Scrum Meeting each morning to synchronize everybody and adapt the plan

✤ A Sprint Review at the end of the Sprint to demonstrate the work done

✤ A retrospective to learn and adapt about the process based on what happened

What could go wrong...

The «mini V»

✤ « A Sprint, is like waterfall, but reduced to 2 or 3 weeks. »

Only the tests remain to be performed...

✤ « A sprint outcome must be shippable in production »

Scrum, but...

✤ « We have adapted Scrum to our specific needs »

The rush mode

✤ The team must keep a sustainable pace from the beginning to the end of the Sprint. And keep this pace from Sprint to Sprint.

Way too long stories !

✤ Cut in thin slices ... but keep a business meaning !

✤ A story isn’t a requirements document

Scrum Ha

The basic package

Scrum « and »

Reinforce insideReinforce from the

outside

Reinforce Scrum inside

Acceptance Tests driven development

Specifications

Acceptance tests

✤ Write acceptance tests BEFORE the development !

✤ The test cases (examples) are part and strengthen the specification

✤ Write collaboratively to share understanding

23

Causal analysis

neuro-linguistique programmation

BPMKano Model

Design Thinking

Creativity workshop

Cognitive Bias

PLeffingwell Pyramid

Brainstorming

Personas

Mind maps

Contextual analysis

Use Cases

Story boards

Archeology documentation

Gap analysis

Non-fonctionnal requirements

Constrains

Questioning

Attributes List

Mesures

Vision

Risks Analysis

Liespotting

Glossary

Prototyping

Story maps

Stakeholders assessment

Elevator statement

Analyse système

Product features

CRC Card

Decision tree

Traçability Model

Business case

Usability engineering

Quantitative Analysis

Goal modeling

Service-Oriented requirements

Integrated requirements engineering

Agent-oriented requirements

Use Cases maps

UMLCollaborative reqt. gathering

Screenwriting

Card sort

Formal Specifications

Cognitive Analysis

Structured Analysis

EARS

Social modeling

Event-oriented reqt.

Contextual inquiry

Reqt. driven design

Problem frames

Domain Driven Design

HCI analysis

Stakeholders taxonomy

The power of games !

Games to

learn

Games to do

the job

Visual Management

See everything that

matters

A forum to interact

in front of facts

Where the work

happens

Reinforce Scrum from the outside

From Scrum to Kanban

✤ Work on the product following a flow

✤ Keep the iterations cadence for the team

✤ Focus on the value and delay rather than estimates

An agile definition of the product

✤ Take into account all the dimensions

✤ The Product Owner is not superman

Start from the goal (the « why »)

Subordinate the perimeter to this « why »

Lean Startup

✤ Agility extended to the business model

From the development to the production with devops

✤ 2 very different visions of the world

✤ Complementary but hard to put together

✤ A question of tools...

✤ But first a question of people and collaboration

Scrum Ri

Invent your own agility

✤ Understand what Scrum can teach us

✤ The rules are no longer required

✤ Create your own way to be agile

My own agile indicators

Feedback Focus

Pleasure

Scrum outside development

Extreme Manufacturing : A customized car for each client in 7 days !

Agile Transformation with Scrum

© Laurent Sarrazin /

Rupture 21

Thank you !✤ @addinquy

✤ http://freethinker.addinq.uy

✤ christophe.addinquy@zenika.com

✤ addinquy

✤ addinquy

✤ addinquy

✤ addinquy

✤ addinquy