ScrumImpulz 2014 - Kris D'Exelle, How to fail Agile projects

1,254
-1

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,254
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

ScrumImpulz 2014 - Kris D'Exelle, How to fail Agile projects

  1. 1. How to fail agile projects? - yes, we can! - Kris D’Exelle, April 2014
  2. 2. Krdexelle@csob.sk Kris D’Exelle manager ICT development CSOB agile pioneer innovation enabler, product developer
  3. 3. What is CSOB? • Part of KBC Bank and Insurance Group • 11.000.000 customers • 51.000 employees • International – Significant position in the markets of Central and Eastern Europe. Key markets include: Slovakia, Czech Republic, Hungary, Bulgaria. – Represented in: Ireland, Luxemburg, Serbia, Slovenia, USA, Russia, Romania, Holland, Switzerland, France, UK, Asia,…
  4. 4. Success… •Agile as standard •Improved •quality •T2M •cost efficiency •Enabled innovation •t&m, ft/fp and offshore
  5. 5. Agile is a mature, powerful and professional methodology Can lead to results beyond your imagination…
  6. 6. Classical pitfalls…
  7. 7. I read a book….
  8. 8. Without experience, reality can be hard…
  9. 9. Product owner • Problem: • Not (enough) available • Several product owners, • No mandate, lack of vision, no decision maker • “scrum master can do this as well”
  10. 10. Changing team composition
  11. 11. Unrealistic scope management
  12. 12. Inefficient or no stand up meetings
  13. 13. Retrospective meeting skipped No retrospective meeting
  14. 14. No acceptance criteria, no definition of done No acceptance criteria, definition of done
  15. 15. Just start without plan, preparation or time estimate
  16. 16. Incremental approach
  17. 17. Incremental coding, without incremental feedback
  18. 18. Unfinished sprints, incremental snowball effect
  19. 19. People make the difference
  20. 20. Tools over verbal communication
  21. 21. Documentation…
  22. 22. Silver bullet expectations
  23. 23. Being agile is great!

×