Presentation from AgileEE 2012 in Kiev (October 2012) and XP Days Ukraine 2012 in Kiev (November 2012) about evolution of Agile processes in team during project lifecycle.

1. Agile Evolution or “On the way to
ideal process”
Mikalai Alimenkou
http://xpinjection.com
@xpinjection
06.10.2012

3. We started with chaos…

4. Ideas was taken from building
architecture

5. Many failed projects

6. Long and unpredictable
cycle from idea to
implementation
Almost no feedback

7. Agile approaches bring changes

8. Agile also brought fear

9. It is easy to go
in wrong direction

10. New way of development with
Scrum

11. Both iterative and incremental

12. Scrum works
as a mirror
for your team

13. Trust
Predictability
Collaboration
Rhythm

14. Short and predictable cycle

15. Focus on project goals
and delivery potentially
shippable product

16. After some time you
are ready to go forward

18. !!!

19. XP style – if
it hurts, do it
more often

20. XP

21. 100% Code Review

22. Pair programming for the
most complex parts

23. Detailed static code analysis

24. Strong definition of DONE
Can I start testing
this new feature?
Yes, it is done!
But I can’t even build
the product…
Ops, I forgot to
commit some files...

25. TDD at all levels
ATDD TDD
Customer’s Tests Programmers’ Tests
Acceptance Fixtures Production Unit Integration
Tests Code Tests Tests

26. Acceptance TDD

27. Evolution never stops,
new methods are
always discovered

28. Lean principles
changed way of
thinking

29. Looking at assembly line and
manufacturing for new ideas

30. Product is seen as
features set, delivered
incrementally

31. How long?

32. Kanban is a
features
production flow

33. !!!

34. Continuous delivery
is the next step

35. “How long would it take your organization to
deploy a change that involves just one single line
of code?
Do you do this on a repeatable reliable basis?”
- Mary and Tom Poppendieck

36. Continuous Delivery
Keeping systems production-
ready throughout development,
so that they can be released to
users at any time

37. ”Continuous delivery is about putting the release
schedule in the hands of the business, not in the hands
of IT.
Implementing continuous delivery means making sure
your software is always production ready throughout
its entire lifecycle – that any build could potentially be
released to users at the touch of a button using a fully
automated process in a matter of seconds or minutes.”
- Jez Humble

38. Short feedback cycle

39. Your typical release

40. Small changes
reduce risks

41. Everybody can deploy to
production

42. Before After
Dev Commit
Monitor Test
Release QA
Deploy
• 2 week release cycles
• code freeze • multiple releases a day
• big events • non-events
• large code changes • small number of changes

43. All intermediate steps
are very important

44. is based on
continuous
improvement

45. @xpinjection
http://xpinjection.com
mikalai.alimenkou@xpinjection.com