Top Banner
Confidential - do not distribute Be Agile…Stay Lean A gentle introduction to agile/lean principles •Giuseppe Lucio Sorrentino
28

Agile/Lean Induction

Apr 14, 2017

Download

Software

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Agile/Lean Induction

Be Agile…Stay LeanA gentle introduction to agile/lean principles

• Giuseppe Lucio Sorrentino

Page 2: Agile/Lean Induction

AgendaStay Agile…Be Lean G. L. Sorrentino 40m

Does software fail?

The new product development game

Lean principles

Empirical by definition

SCRUM and Kanban

Page 3: Agile/Lean Induction

Does software fail?

Page 4: Agile/Lean Induction

How often software fails? 1

• 5 to 15 % of the IT project will be abandoned before or shortly after delivery as hopelessly inadequate

• Many others will arrive late and over budget or require massive reworking

Page 5: Agile/Lean Induction

“Failure is not an option…

…it comes bundled with the software”Unknown Auhtor

Page 6: Agile/Lean Induction

Why waterfall fails more? There are many replies…

• Waterfall • Agile/Lean

Page 7: Agile/Lean Induction

The new development game

Page 8: Agile/Lean Induction

The new product development game 2

“Companies are increasingly realizing that the old, sequential approach to developing new products simply

won’t get the job done. Instead, companies in Japan and the United States are using a holistic method as in

rugby, the ball gets passed within the team as it moves as a unit up the field.”

Page 9: Agile/Lean Induction

Manifesto for agile software development 3

That is, while, there is value in the items on the right, we value the items on the left more.

Page 10: Agile/Lean Induction

The 12 Principles of Agile Development

They can be divided into four categories 4:

1. Delivering the project

2. Communicating and working together

3. Project execution

4. Constantly improving

Page 11: Agile/Lean Induction

Delivering the project1. Our highest priority is to satisfy the customer through early and continuous delivery of

valuable software

2. Welcome changing requirements, even late in development. Agile process harness

change for the customer’s competitive advantage

3. Deliver working software frequently, from a couple of weeks to a couple of months, with

a preference for a shorter timescale

Page 12: Agile/Lean Induction

Activity TimeWhat’s in your team?

Page 13: Agile/Lean Induction

Communicating and working together

4. The most efficient and effective method of conveying information to and within a

development team is face-to-face conversation

5. Business people and developers must work together daily throughout the project

6. Build projects around motivated individuals. Give them the environment and support

they need, and trust them to get the job done

Page 14: Agile/Lean Induction

Activity TimeWhat’s in your team?

Page 15: Agile/Lean Induction

Project execution7. Working software is the primary measure of progress

8. Agile processes promote sustainable development. The

sponsors, developers and users should be able to maintain a

constant pace indefinitely

9. Continuous attention to technical excellence and good design

enhances agility

Page 16: Agile/Lean Induction

Activity TimeWhat’s in your team?

Page 17: Agile/Lean Induction

Constantly Improving10. Simplicity – the art of maximize the amount of work not done – is essential

11. The best architectures, requirements and designs emerge from from self-organizing

team

12. At regular intervals, the team reflects on how to become more effective, than tunes and

adjusts its behavior accordingly

Page 18: Agile/Lean Induction

Activity TimeWhat’s in your team?

Page 19: Agile/Lean Induction

Be agile…Many Agile Framework describe:

• Governance

• Time-boxed Strategy

• Meetings and Tools

SCRUM is just one of many Agile Frameworks

DSDM, AUP and many others agile frameworks exist

Page 20: Agile/Lean Induction

Lean principles

Page 21: Agile/Lean Induction

…Stay Lean! 5

Two Principles (JIT and Jidoka) to:

• reach organization goals

• driven by oranization values

• through specific tools and methods

Kanban cards and boards were just two lean methods used in Toyota

Kanban was choosen as name for aFramework from D.J.Anderson in 2010

Goals

Just-In-Time Jidoka

Methods and Tools

Values

Page 22: Agile/Lean Induction

Just-in-time

Airport Check In Process

Client Arrives Client On Board

Three main types of wastes:

• Activities not adding value (Muda)

• Uneveness (Mura)

• Overburden(Muri)

Two main objectives:

• Eliminate wastes in the process• Defend the process flow

Page 23: Agile/Lean Induction

Just-in-time

Airport Check In Process

Client Arrives Client On Board

Security Check

THROUGHPUT TIME - TT

CYCLE TIME - CT

Bottlenecks Law: increase TT and create Queues

Effects of Variation Law: More variation increase TT

Page 24: Agile/Lean Induction

Activity TimeProcess Simulation

Page 25: Agile/Lean Induction

Jidoka 5

Two main objectives:

• decide as late as possible

• empower the team

• see the whole

Page 26: Agile/Lean Induction

Empirical by definition

Page 27: Agile/Lean Induction

One more thing… 6

Page 28: Agile/Lean Induction

References1. http://spectrum.ieee.org/computing/software/why-software-fails

2. https://hbr.org/1986/01/the-new-new-product-development-game

3. http://agilemanifesto.org

4. Learning Agile, A. Stellman and J. Greene, O'Reilly, Nov. 2014

5. This is Lean, N. Modig and P. Ahlstrom, Rheologica Publishing, Nov. 2012

6. http://intenseminimalism.com/2010/the-dot-loop-the-simplest-process-possible/