Catch AgileAntipatterns of using Agile: how to survive

by Yuriy V. Silvestrov

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 yuriy@silvestrov.com.

About lection

Time is counting

⌛ < 60

How many of you using

AgileScrumKanban

I will try to adapt

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

Snowflake men by Max Dorofeev

History of PM Frameworks

Waterfall

Cost of bug fixBy IBM Research

Invention of BDUF

Comprehensive documentation

Tools and processes

Following a plan

Contract negotiation

BDUF Problems

Incremental development

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

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

Agile frameworks

ScrumXPKanbanLeanCrystal

Scrum

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

Solution?

Be Agile!

Catch 1: when Agile wouldn't work

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

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

“DeathMarch” by Edward Yourdon

Catch 2: dealing with conveyor

Why Scrum is not best choice

No releases schedulePriorities changing oftenHard to estimate size of each element

Solution?

Try Kanban

Catch 3: scrum-like

No retrospectives

Should always try to improve

Standup-meeting as speech to PM

No Done-Done criteria

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

Done!

80% done

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

Catch 4: Scrum cargo cult

Catch 5: Common sense bias

Business cases

Questions?

???

Thank you!

yuriy@silvestrov.com