This document discusses antipatterns when using Agile project management frameworks. It begins with an introduction by Yuriy Silvestrov and then covers the history of frameworks like waterfall, incremental development, and Agile. It identifies five common "catches" or antipatterns when using Agile: 1) when Agile wouldn't work well for large or safety-critical teams, 2) dealing with conveyor belt prioritization, 3) using Scrum processes incorrectly, 4) lack of retrospectives or clear definitions of done, 5) bias against common sense practices. The document aims to help organizations avoid these pitfalls and better implement Agile.

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

2. About me
Yuriy V. Silvestrov
10+ 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.com
for more info or contact me at
yuriy@silvestrov.com.

3. About lection

4. ⌛ < 60
Time is counting

5.  Agile
 Scrum
 Kanban
 I will try to adapt
How many of you using

6.  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 cases
 Q&A
Content

7. Snowflake men by Max Dorofeev

8. History of PM Frameworks

9. Waterfall

10. By IBM Research
Cost of bug fix

11.  Comprehensive
documentation
 Tools and
processes
 Following a plan
 Contract
negotiation
Invention of BDUF

12. BDUF Problems

13. Incremental development

14. Agile

15.  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: 2001

16.  Teamwork & responsibility over
Individuals and Interaction
 Deliver Value over Working software
 Partnership elaboration over Customer
collaboration
 Embrace change over Respond to Change
Agile manifesto 2.0: 2011

17.  Scrum
 XP
 Kanban
 Lean
 Crystal
Agile frameworks

18. Scrum

19.  “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
Catch 0: problems of Waterfall

20. Be Agile!
Solution?

21. Catch 1: when Agile wouldn't work

22.  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
Team size and bug-critical soft

23.  Customer collaboration over contract
negotiation
 Responding to change over following a
plan
 Individuals and interactions over
processes and tools
 Working software over comprehensive
documentation
Agile principles violation

24. “DeathMarch” by Edward Yourdon

25. Catch 2: dealing with conveyor

26.  No releases schedule
 Priorities changing often
 Hard to estimate size of each element
Why Scrum is not best choice

27.  Try Kanban
Solution?

28. Catch 3: scrum-like

29.  Should always try to improve
No retrospectives

30. Standup-meeting as speech to PM

31. Code Complete ✔
Unit Tested ✔
Peer Reviewed ✔
QA Complete ✔
Documented ✔
No Done-Done criteria

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

33. Catch 4: Scrum cargo cult

34. Catch 5: Common sense bias

35. Business cases

36. ???
Questions?

37. yuriy@silvestrov.com
Thank you!