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.

1. Agile in Heads and
Companies
Timofey Yevgrashyn
tim(a)tim.com.ua

2. Sometimes, Software
Development looks like this…

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. 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. Software Development
is the Land of
“Black Swans”

6. Paradigm Shift #2
Quality
Cost Time
Scope
Plan-driven
Fixed
Flexible

7. Paradigm Shift #2
Agile
Fixed
Flexible
Quality
CostTime
Scope

8. Paradigm Shift #3
User
System-centric Design
System

9. Paradigm Shift #3
User-centric Design
User
System

10. Agility
is
a Philosophy

11. Leading Causes of Failed
Agile Projects
* The 9th Annual State of Agile™ Report

12. Barriers to Further Agile
Adoption
* The 9th Annual State of Agile™ Report

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. Hi, we are

15. Our Challenge
Myth
Reality

17. Lean-ing
Slicing
Development Cadence
into 4-Sprints Cycles

18. EPIC
Feature
User
Story
Initiative

19. Clarifying Requirements
Only for Next 4 Iterations

20. Estimate
by Comparing

21. Continuous
Review of
Everything

22. What Can We
Do Better?

23. Expert Groups
*Inspired by Spotify and Henrik Kniberg

24. Customers and Users Analysis

25. Expectations Management

26. Custom Product
Development?

27. Product Goals
Vision
Mappings

28. How About Dedicated Teams?

29. Professional
Services?

30. Tame the Flow

31. Sub-optimization

32. Kanban
Kaizen
Common Sense

33. Takeaways

34. Agility is the Way of Thinking

35. Use Proper Paradigms

36. Changing Industry
is the Mindset Change
of Participants

37. Timofey
Yevgrashyn
http://tim.com.ua
tim(at)tim.com.ua Thankyou!