1. Obstacles on agility path

2. Dusan Kocurek @didierkoc

3. Agile is if…. ……requirements and solutions evolve through collaboration between self-organizingcross-functionalteams

4. First look, experience Scrum seems to be easy Just 3 roles and a few ceremonies Why is it hard to implement it?

5. Because change is done by PEOPLE

6. Change Standards & processes save usfrom thinking about change Change of process is blocked by process itself Resistance to change is normal and healthy

7. Resistance stages It was difficult, but … Nothing makes sense… Ok, how about… No, I won’t… Nice but...

8. “Agile is reason why we fail.” Ok, let’s cancel agile! How would you work tomorrow? What would be different? Answer that question to help yourself

9. Resistance to agile Missing reason whyto be agile Missing shared goal Fear of responsibility Personal goals (career risk) Low courage Bad experience

10. We always repeat: ‘collaboration and self-organization’ It’s a chance to drive, not just tobe driven Chance to pull, not to be pushed But it means responsibility

11. Not just TEAM should transform…

12. If Pippi Longstocking would be on your project, what would she do? Jan 19th #AROTD @Retroflection

13. Pippi would ask impertinent questions, helpher team to identify assumptions, and energize the team room! Every team needs Pippi

14. Model 7:00:15:30

15. ‘I can’bug <X> told me vs. I can do

16. Test your team Ask: We need to prepare a new release. WHO IS GOING TO DO IT?

17. Test your team

18. Answer of THE TEAM? “We need a leader”

19. Leader necessity Decision maker or leader? Leaders are born Why? Why? Why? Why? Why? What? What? What? Fear of responsibility in team

20. Agile crossing chasm Dr. Dobbs magazine, 2006 The picture is about companies, but isn’t it about every team too?

21. The Satir Change Model

22. People resist a lot of changes Shrink the change!

23. How to change First instinct is toeducate people John Cutter (Harvard)

24. How to change It almost never happened

25. How to change that makes people to that gives fuel to

26. Agility is acceptationof failures

28. More people in company

30. Self-organization

31. Do retrospective

32. Common planning

33. Common estimationPREPARE

34. Doing Agile Why? Why? Why?Why?Why?Why? Check over-commitment Retrospective Identify waste ‘Just’ improve REPEAT

35. Typical problems Workflow Constant failure to deliver Guerilla work without product owner Tasks outside of sprint Forgotten priorities Collaboration Non-productive meetings We & They Self-organization Process Velocitynot measured Not eliminating waste Scrum Master Not a manager Problems not tracked Techniques Preparation for planning Efficient code review Demo preparation Not implemented retrospective ideas

37. How to stay on the road Yes, there are teams not using burn-down chart! Yes, there are teams not using taskboard! Should be Scrum Master 100% committed? Priority is not just a number, it is RULE! Know your velocity! We do not have time to think what, how and whywe are doing Bla, bla, bla in meetings

38. How to stay on the road Define pilot timeframe & exit criteria Couch can help, but not manage Help yourself Discipline Openness Creativity Think out of box Conferences, books, blogs, twitter, groups

39. Myths No documentation Story is requirement and nothing else Product is planned once If we will improve … then we will be better Precise estimation Catching hours More locations makes agile impossible You have 3 sprints to prove it! Agile as silver bullet Fail, fail, fail, fail Too many problems because of agile

40. Agile is not just Scrum