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
Twitter: @ysilvestrov
3. Based on my own and About lection
team experience
and a lot of interviews
conducted
Have been presented in
Ciklum Donetsk,
Vinnitsa and Odessa last
month
but reworked a
afterwards.
9. Cockburn
Scale
L L6 L20 L40 L100 The closer the
project is to the
E E6 E20 E40 E100
right-top, the
D D6 D20 D40 D100 more formal
process you
C C6 C20 C40 C100 need.
21-4 41-1
1-6 7-20 0 00
10. 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 back
Solution?
11. Customer collaboration over contract
negotiation
Responding to change over following a
plan
Individuals and interactions over processes
and tools
Working software over comprehensive
documentation
Catch 2: Agile principles violation
12. 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 J
Solution?
20. Code Complete ✔
Unit Tested
e! ✔
Peer Reviewed ✔
QA Complete o n ✔
Documented D ✔
Scrum-like symptoms:
No Done-Done criteria
21. Pareto rule:
80% of task value
takes 20% time.
Another 20% takes
another 80% of time.
Scrum-like symptoms:
80% done
22. Try to review your process against the
agile manifesto and checklists
If something is missing, think if you could
benefit from bringing it back.
Solution?