1

Scrum

managing thought complexity

2

Who am I?

3

What is SCRUM?

We’re losing the relay race

“The… ‘relay race’ approach to product development…may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‘rugby’ approach—where a team tries to go the distance as a unit, passing the ball back and forth—may better serve today’s competitive requirements.”

Hirotaka Takeuchi and Ikujiro Nonaka, “The New New Product Development Game”,Harvard Business Review, January 1986 4

5

Why?

6

Winston Royce’s “Grandiose” Model

“I believe in this concept, but the implementation is risky and invites failure.”

Winston W. Royce, “Managing the development of large software systems”, Aug 1970

“Single Pass” phased model to cope with US DoD regulatory requirements

Source: Silvana Wasitova

7

Winston Royce’s Recommendation

Iterations between phases, hopefully confined to successive steps

Source: Silvana Wasitova

8

Time

Conception Growth Maturity Decline Withdrawal

Project

ProjectProject

Project Project

Project

Project

Project

Product Life Cycle

9

Scrum is a framework structured to support

complex product development.

10

Complexity

11

12

Conception Growth Maturity Decline Withdrawal

Project

ProjectProject

Project Project

Project

Project

Project

Complexity zone Complex zone

Development Production

13

Facing new challenges….

Speed Stakeholders

RisksPermanent change

people

Business Alignment

14

Scrum

15

•Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time.

•It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).

•The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.

•Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.

Scrum in 100 words

16

time

resources

scop

e

Quality

Traditional Project Management

17

Split Cost (Resources) in People and Tools

Split Scope in Functionality and Quality (suggestion: Scott Ambler)

Add a dimension for Process (suggestion: Alistair Cockburn)

Add a dimension for (Business) Value (suggestion: Jim Highsmith)

http://www.ambysoft.com/essays/brokenTriangle.htmlhttp://alistair.cockburn.us/index.php/Process:_the_fourth_dimensionhttp://blog.cutter.com/2009/08/10/beyond-scope-schedule-and-cost-measuring-agile-performance/

18

1. Value2. People3. Functionality4. Quality5. Tools6. Time7. Process

And we get...the 7 dimensions of software projects

19

Scrum Theory

• Scrum is founded on empirical process control theory, or empiricism.

• Empiricism asserts that knowledge comes from experience and making decisions based on what is known.

• Scrum employs an iterative, incremental approach to optimize predictability and control risk

20

21

3 legs

TransparencyInspectionAdaptation

22

Scrum consists of Scrum Teams and their associated roles, events, artifacts, and rules.

Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage.

The rules of Scrum bind together the events, roles, and artifacts, governing the relationships and interaction between them.

23

The Scrum Team

• The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master.

• Scrum Teams are self-organizing and cross-functional.

• The team model in Scrum is designed to optimize flexibility, creativity, and productivity.

• Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback.

24

A Product Owner

• The Product Owner is responsible for maximizing the value of the product and the work of the Development Team.

• The Product Owner is the sole person responsible for managing the Product Backlog.

25

The Development Team

• The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint.– Self organizing– Cross-functional

• Optimal Development Team size is small enough to remain nimble and large enough to complete significant work.

26

The Scrum Master

• The Scrum Master is responsible for ensuring Scrum is understood and enacted.

• Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules.

• The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren't.

27

Basic principles

• Clear and catching vision

• Maintained Product Backlog

• High Stakeholder’s participitation

• Sprint is protected

• Collaborative Sprint Reviews

• Retrospectives focusing on work and progress

28

Example

29

Item 10

Item 11

Item 8

Item 9

Item 10

Item 11

Item 6

Item 7

Item 8

Item 9

Item 10

Item 11

Item4

Item5

Item 6

Item 7

Item 8

Item 9

Item 10

Item 11

Maximizing Value

06/1212/11

1 6 72 3 4 5

Item3

Item4

Item5

Item 6

Item 7

Item 8

Item 9

Item 10

Item 11

Item 2

Item 1

Estimation

❶❷❸❹❺❻Are milestones where we measure the variance between estimation and delivery

Item 11

?

?

?

??

Delivery

30

Where do find Scrum?

• Software development• Managing churchs• Venture Capital and Start’ups• Education• Enterprise Management

Scrum is teached as « Lean Management » in

Japan!

31

Scrum Evolutions

32

Credits• Jurgen Appelo, What is Agile Management?

• Mike Cohn, Introduction to Scrum

• Dave Snowden, Cynefin

33

Questions?

34

35

36

Thanks

37

Pierre E. NEIS

Management Consultant

Head of Lean Centre of

Competence at coPROcess S.A.

Scrum & Lean Coach