The next step
0 likes174 views
The document discusses how to achieve expected business value through agile practices. It notes that gains are not always consistent and explores why, such as agile being perceived only as project management, organizations not supporting agile teams, and a focus on practices over principles. Both business and development perspectives are presented, along with suggestions like exploring hypotheses faster, deciding later, and viewing agile as continuous learning. The overall message is that changing perspectives and consciously improving can help achieve expected business value through agile.
The next step
- 1. The Next Step How to reach the expected Business Value Agilia Budapest 2017
- 4. Agile Works
- 5. Gains are not consistent
- 6. Expectation
- 7. Reality
- 8. Why so?
- 10. Organization
- 11. Agile Team
- 12. PO is Squeezed in the middle
- 13. Focus on Practices instead of Principles
- 14. How we are doing things
- 15. Why we are doing them
- 16. Let’s Assess the Situation
- 19. Online in 6 Months with All Feature 2°
- 20. Tell me when This Feature Will be implemented 3°
- 21. User Stories were not well written 4°
- 22. It’s a Legacy Rewrite We need to preserve All Features first 5°
- 23. What Dev Say
- 26. It can’t be Technically Done 3°
- 27. 4° User Stories were not well written
- 36. Only Market validates the needs
- 37. “Make Impacts not software” Gojko Adzic
- 38. Validation must be fast
- 40. Deliver as Fast as Possible Lean Software Development
- 44. Decide as Late as Possible Lean Software Development
- 45. Don’t focus on Jira Discuss Stories first
- 47. Explain domain
- 49. Reserve space for different Technical Solution
- 50. Next Steps?
- 51. Consciousness
- 57. Listen to People and Choose a Topic
- 59. “If you want to get different result, start do thing differently” Albert Einstein
- 62. Expected Value