Catch AgileAntipatterns of using Agile: how to survive by Yuriy V. Silvestrov
About meYuriy V. Silvestrov10+ years record in IT, 8+ years devoted to managingprojects. Now working for Ciklum, managing a teamof 30+ persons making different software for Danishfinancial organizations.Please visit my websitehttp://yuriy.silvestrov.comfor more info or contact me firstname.lastname@example.org.
Based on my own and About lection team experience and a lot of interviews conducted Have been presented in Ciklum Donetsk last month but changed a bit afterwards.
Cockburn ScaleL L6 L20 L40 L100 The closer theE E6 E20 E40 E100 project is toD D6 D20 D40 D100 the right- top, the moreC C6 C20 C40 C100 formal process 21- 41- you need. 1-6 7-20 40 100
Start creating procedures May be even to become more formal and less agile When the project and team became more mature, you could bring agility backSolution?
Customer collaboration over contract negotiation Responding to change over following a plan Individuals and interactions over processes and tools Working software over comprehensive documentationCatch 2: Agile principles violation
Try to keep agility inside, and be formal seen from outside Actually, it’s rather political then project management problem, and you need to solve it with the political tools Solution?