catch agile

37
Catch Agile Antipatterns of using Agile: how to survive by Yuriy V. Silvestrov

Upload: yuriy-silvestrov

Post on 13-Jan-2015

250 views

Category:

Technology


1 download

DESCRIPTION

History of Agile frameworks and examples of it's misusing.

TRANSCRIPT

Page 1: Catch agile

Catch AgileAntipatterns of using Agile: how to survive

by Yuriy V. Silvestrov

Page 2: Catch agile

About me

Yuriy V. Silvestrov10+ years record in IT, 8+ years devoted to managing

projects. Now working for Ciklum, managing a team of 30+ persons making different software for Danish financial organizations.

Please visit my website http://yuriy.silvestrov.comfor more info or contact me at [email protected].

Page 3: Catch agile

About lection

Page 4: Catch agile

Time is counting

⌛ < 60

Page 5: Catch agile

How many of you using

AgileScrumKanban

I will try to adapt

Page 6: Catch agile

Content

History of Project Management Frameworks◦Waterfall◦BDUF◦Incremental◦Agile

Catches◦Waterfall problems◦When Agile wouldn’t work◦Dealing with Conveyor◦Scrum-like◦Scrum cargo cult◦Common sense bias

Business casesQ&A

Page 7: Catch agile

Snowflake men by Max Dorofeev

Page 8: Catch agile

History of PM Frameworks

Page 9: Catch agile

Waterfall

Page 10: Catch agile

Cost of bug fixBy IBM Research

Page 11: Catch agile

Invention of BDUF

Comprehensive documentation

Tools and processes

Following a plan

Contract negotiation

Page 12: Catch agile

BDUF Problems

Page 13: Catch agile

Incremental development

Page 14: Catch agile

Agile

Page 15: Catch agile

Agile manifesto: 2001

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Page 16: Catch agile

Agile manifesto 2.0: 2011

Teamwork & responsibility over Individuals and Interaction

Deliver Value over Working softwarePartnership elaboration over Customer

collaborationEmbrace change over Respond to Change

Page 17: Catch agile

Agile frameworks

ScrumXPKanbanLeanCrystal

Page 18: Catch agile

Scrum

Page 19: Catch agile

Catch 0: problems of Waterfall

“Many of the [system's] details only become known to us as we progress in the [system's] implementation. Some of the things that we learn invalidate our design and we must backtrack.

David Parnas, A Rational Design Process

Page 20: Catch agile

Solution?

Be Agile!

Page 21: Catch agile

Catch 1: when Agile wouldn't work

Page 22: Catch agile

Team size and bug-critical soft

The more is your team size and the more a bug in your product would cost, the less you’d to benefit from Agile.

Alastair Coburn

Page 23: Catch agile

Agile principles violation

Customer collaboration over contract negotiation

Responding to change over following a plan

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Page 24: Catch agile

“DeathMarch” by Edward Yourdon

Page 25: Catch agile

Catch 2: dealing with conveyor

Page 26: Catch agile

Why Scrum is not best choice

No releases schedulePriorities changing oftenHard to estimate size of each element

Page 27: Catch agile

Solution?

Try Kanban

Page 28: Catch agile

Catch 3: scrum-like

Page 29: Catch agile

No retrospectives

Should always try to improve

Page 30: Catch agile

Standup-meeting as speech to PM

Page 31: Catch agile

No Done-Done criteria

Code Complete ✔Unit Tested ✔Peer Reviewed ✔QA Complete ✔Documented ✔

Done!

Page 32: Catch agile

80% done

Pareto rule: 80% of task value takes 20% time. Another 20% takes another 80% of time.

Page 33: Catch agile

Catch 4: Scrum cargo cult

Page 34: Catch agile

Catch 5: Common sense bias

Page 35: Catch agile

Business cases

Page 36: Catch agile

Questions?

???