Lean agile pt

Joseph W. Yoder

Lean vs Agile Page - 1

Lean – The Foundation for Agility Increase Value, Reduce Waste,

Improve Flow…

Joseph W. Yoder

The Refactory, Inc.

[email protected]

http://www.refactory.com

Lean @ Agile PT – Copyright 2011 Joseph W. Yoder & The Refactory, Inc.

Talk Originally by Dave Thomas

Unfortunately Dave can not be with us.

I’m am not going to give Dave’s talk.

Rather I will do a Karaoke variation where I

take a title and description by someone else

(Dave) and put into my words and

discuss some ideas about the topic.

Joseph W. Yoder



Agile Software Development

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

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

…From the Agile Manifesto


Agile Principles and Practices

Scrum, XP, TDD, Refactoring, Regular Feedback, Testing, More Eyes, …

Good People! Face-To-Face conversation.

Continuous attention to technical excellence!

Motivated individuals with the environment and support they need. Retrospectives!

Allow Requirements to Change! Embraced Software Evolution as needed!

Joseph W. Yoder



Agile Design ValuesCore values:

Design Simplicity

Communication

Teamwork

Trust

Satisfying stakeholder needs

Keep learning

Continuous Feedback

Lots of Testing/Validation


Agile Practices - Scrum

http://upload.wikimedia.org/wikipedia/commons/5/58/Scrum_process.svg

Joseph W. Yoder



Agile Practices - XP

Scrum picture


Test-Driven Development

Requirements Envisioning

(days/weeks)

Architecture Envisioning

(days/weeks)

Iteration 0: Envisioning

Iteration Modeling (hours)

Model Storming

(minutes)

TDD (hours)

Iteration n: Development

a little bit of modeling then a lot of coding

http://www.extremeprogramming.org/

http://www.extremeprogramming.org/map/iteration.html

Joseph W. Yoder



Test-First Development

Re(write)a test

Write production code

Clean up code(Refactor)

Check iftest fails

Checkall testssucceed

test fails

all testssucceed

test succeeds1 or moretests fail


Test-First Development RhythmUser story-by-story:

Write the simplest test

Run the test and fail

Write the simplest code that will pass the test

Run the test and pass

Repeat until a “story” is tested and implemented

Design between the keystrokes

Joseph W. Yoder



Test Driven Development

Write some production code

Check iftest fails

Checkall testssucceed

all tests succeed

test fails

1 or moretests fail

Tests don’t always get written first.Tests written & must pass before checking in production code.

Re(write)a test

Clean up code(Refactor)


Test-Driven (First) DevelopmentTest-Driven Development – work in short cycles of

implementing code with tests and make sure that all tests pass.

Many Unit Tests written along with other tests.

It isn't enough to write tests: you have to run them regularly (many times a day).

Developers get immediate feedback on how they're doing…publish scores and keep track.

Additionally, these tests provide invaluable support as the software design is improved.

Joseph W. Yoder



Continuous Integration

The system is fully integrated at all times.

Daily Integration Tests are ran and only working code is checked into the main code branch.

Testing and Builds are done multiple times per day. Any failures are immediately fixed until all tests pass.


Retrospectives are Key

1) What worked well that we do not want to forget for future iterations?

2) What should we do differently?

Not what are the bad things or what is broken. Do not focus on negative things.

3) What still puzzles us?

Things we can't answer.

4) What did you learn?

5) hopes for the next iteration/release.

Web Sites/ExtremeProgramming/map/iteration.html

Web Sites/ExtremeProgramming/map/iteration.html

Joseph W. Yoder



Lean by Toyota


Lean Development

Increase Value, Reduce Waste, Improve Flow…

A lean organization understands customer value and focuses its core processes to continuously increase it.

Ultimate goal is to provide perfect value to customer and business.

Just in Time Practice – don’t do something before you need it.

Joseph W. Yoder



Kanban (看板)

Signboard / Billboard


Kanban (看板) Principles

The basic principles of Kanban

Limit Work in Process (WIP)

Pull value through (WIP)

Make progress visible

Increase throughput

Fixed Kanban Backlog

Quality is part of the processed (internal)

Continuously monitor the above to improve!!!

Is this similar to a Retrospective?

Joseph W. Yoder



Is Agile the same as Lean

At the core is Lean

Design Simplicity

Communication

Teamwork

Continuous Learning

Early Agilest were influenced by Lean, but:

Many get stuck in the process

Many Misconceptions about Agile


Agile MythsSimple solutions are always best.

Building in flexibility is always over-engineering.

You can change the system fast!!!

You don’t want to change … you are not Agile.

Don’t worry about the architecture .

If I do the Scrum process I will be super productive and it will be easy to duplicate.

We can always easily adapt to changing requirements (next requirements).

Should not have specialists!

http://en.wikipedia.org/wiki/File:Agile_Software_Development_methodology.jpg

Joseph W. Yoder



Lean vs Agile

Common Themes:

People centric approach

Empowered teams

Adaptive planning

Continuous improvement

Retrospective

Core principles of Agile are Lean

Need to continue to learn and evolve!!!


How Lean Can We Get?

Screw It, Let’s Do It!!!

Joseph W. Yoder



Summary

Lean really is the foundation of Agile

Quick in movement, nimble,

Don’t get stuck in the myths

Learning is Important (Retrospective)

It is ok to adapt the process

We should be committed to finding ways to:

Increase Value, Reduce Waste, Improve Flow…


Muito Obrigado!!!

Lean agile pt

Technology

Transcript of Lean agile pt