Agile and Lean - Maikal Vandorpe and Elke Matthijs

7/28/2019 Agile and Lean - Maikal Vandorpe and Elke Matthijs

1/57

Agile & Lean

@ MediaGeniX

Elke Matthijs

Makel Vandorpe

[email protected]

[email protected]


2/57

Contents

Introducing MediaGeniX

Agile development XP

SCRUM

Kanban

Lean Thinking

Conclusion


3/57

Contents



SCRUM

Kanban

Lean Thinking

Conclusion


4/57


Introducing ourselves: ElkeAgile software engineer

MakelCompetence Manager Software Engineering

Agile/Lean practitioners, not gurus Talking from personal experience


5/57


Product company: WhatsOn

Planning software for TV-broadcasters

100 Employees

20 Years


6/57



7/57

http://upload.wikimedia.org/wikipedia/de/8/88/ProSiebenSat1.svghttp://www.tvnorge.no/http://upload.wikimedia.org/wikipedia/de/c/ce/MTV-Logo.svg


8/57


50 Customers worldwide

Different workflows & customisations

Offer maximum value to our customer

Short time to deliver

Flexible

Frequent communications


9/57


Project duration

Weeks up to years

Project team composition

Ad hoc

Cross-functional

1-2 Project manager

1-4 Functional analysts

1-6 Developers

1-2 Customer service


10/57

Contents



SCRUM

Kanban

Lean Thinking

Conclusion


11/57

Agile development

What came before


12/57

Waterfall Methodology


13/57


Requirements Implementation MaintenanceValidationDesign

Sequential

Large time to market

Late feedback


14/57



Requirements are set at the beginningand remain fixed


15/57


Time

Well defined process

Good for small or stable projects

Management makes all the decisions


16/57

Agile development


17/57


18/57


19/57

Agile development


Iteration 2

Prioritization of requirements


20/57

Agile development


Iteration n

Prioritization of requirements


21/57

Agile development


Not all requirements are in the same

phase at the same time

Requirementsdelivered after

iteration 1

Requirementsto be delivered

In iteration 2


In iteration


In iteration n


22/57

Agile development

Time

Iterative & incremental

Adaptive planning Deliver more value

React fast to changes

Self-organizing & cross-functional teams


23/57

Contents


Agile development

XP

SCRUM

Kanban

Lean Thinking

Conclusion


24/57

XP (eXtreme Programming)

On-site customer

User stories

Communication

Simple Design Pair programming

Unit testing

Test Driven Development

Continuous Integration Refactoring

Collective code ownership

Iteration planning

Quality

ScopeTime /

Speed


25/57

XP (eXtreme Programming)

At MediaGeniX we like User stories

Collective code ownership

Continuous integration

Simple design + Refactoring

Code reviews and pair programming for difficult parts


26/57


27/57

Contents


Agile development

XP

SCRUM

Kanban

Lean Thinking

Conclusion


28/57

SCRUM

Focus is on project management &team

Time-box deliveries => sprints

A sprint

A period of 2, 4, 6 or 8 weeks

Sprint definitionthe worksprint retrospective

delivery

Assumes fixed team


29/57


30/57

SCRUM

Team velocity

Measures story points/sprint

Pro: less overestimation

Con: Team and project should be fixed


31/57


32/57


33/57


34/57

Daily stand-up

What am I working on?

How long will it take tocomplete?

Am I stuck?


35/57


36/57

Contents


Agile development

XP

SCRUM

Kanban

Lean Thinking

Conclusion


37/57


38/57

Limit WIP (Work In Progress)

Prioritization of work items

WIP is directly proportional to lead time

3

Kanban

Design ImplementationBuffer

2

1

2

2 max

3

Average

demand

4 max 35 max


39/57

Kanban

Create flow - Cadence

Buffer size trade-off

Design ImplementationBuffer

4 max 2 2 max 5 max 3

Average

demand

Idle time

~

Lead time


40/57


41/57


42/57


43/57


44/57


45/57


46/57


47/57


48/57


49/57


50/57


51/57


52/57


53/57


54/57


55/57

Conclusion

You have to make it work!


56/57


57/57

Agile and Lean - Maikal Vandorpe and Elke Matthijs

Documents

Transcript of Agile and Lean - Maikal Vandorpe and Elke Matthijs