Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile in Heads and Companies

3,124 views

Published on

You have read about an interesting agile approach and now you want to try it in real-life? Are you ready to make all the needed changes for the approach to work? Are you, project managers, Business Analysts, developers ready to start thinking differently? Are the business representatives ready to communicate with development teams differently?

It is frequent that the changes in one part impact other areas of product development and are greater than just team or department changes.

Let's try to remind ourselves about the main differences of an Agile mindset. This talk will include real life examples from real companies and undocumented items that you don't always find out about when reading about Agile and planning your Agile journey.

Published in: Leadership & Management
  • Be the first to comment

Agile in Heads and Companies

  1. 1. Agile in Heads and Companies Timofey Yevgrashyn tim(a)tim.com.ua
  2. 2. Sometimes, Software Development looks like this…
  3. 3. A brief history overview 1900 1950 1980 1990 2000 Implementation Mass Production Toyota Production System Lean Manufacturing Waterfall Iterative Incremental Development Lean Software Development Agile RUP Scrum XP Your team? J Principles Practices
  4. 4. Paradigm shift #1 Requirements Far from agreement Technology Far from certainty Simple Complicated Complex Anarchy Source: Strategic Management and Organizational Dynamics by Ralph Stacey, in Agile Software Development With Scrum by Ken Schwaber and Mike Beedle.
  5. 5. Software Development is the Land of “Black Swans”
  6. 6. Paradigm Shift #2 Quality Cost Time Scope Plan-driven Fixed Flexible
  7. 7. Paradigm Shift #2 Agile Fixed Flexible Quality CostTime Scope
  8. 8. Paradigm Shift #3 User System-centric Design System
  9. 9. Paradigm Shift #3 User-centric Design User System
  10. 10. Agility is a Philosophy
  11. 11. Leading Causes of Failed Agile Projects * The 9th Annual State of Agile™ Report
  12. 12. Barriers to Further Agile Adoption * The 9th Annual State of Agile™ Report
  13. 13. More Agile Manifesto We encounter possibilities to focus more on effectiveness by working Agile and learning from that. Based upon our experience we value Teamwork & responsibility over Individuals and Interaction Deliver Value over Working software Partnership elaboration over Customer collaboration Embrace change over Respond to Change Inspired by , 2010
  14. 14. Hi, we are
  15. 15. Our Challenge Myth Reality
  16. 16. Lean-ing Slicing Development Cadence into 4-Sprints Cycles
  17. 17. EPIC Feature User Story Initiative
  18. 18. Clarifying Requirements Only for Next 4 Iterations
  19. 19. Estimate by Comparing
  20. 20. Continuous Review of Everything
  21. 21. What Can We Do Better?
  22. 22. Expert Groups *Inspired by Spotify and Henrik Kniberg
  23. 23. Customers and Users Analysis
  24. 24. Expectations Management
  25. 25. Custom Product Development?
  26. 26. Product Goals Vision Mappings
  27. 27. How About Dedicated Teams?
  28. 28. Professional Services?
  29. 29. Tame the Flow
  30. 30. Sub-optimization
  31. 31. Kanban Kaizen Common Sense
  32. 32. Takeaways
  33. 33. Agility is the Way of Thinking
  34. 34. Use Proper Paradigms
  35. 35. Changing Industry is the Mindset Change of Participants
  36. 36. Timofey Yevgrashyn http://tim.com.ua tim(at)tim.com.ua Thankyou!

×