Debunking Four Myths of Agile Development Webcast
Download as PPTX, PDF2 likes1,491 views
The document debunks four myths surrounding agile development, emphasizing that it is not a rigid methodology but a philosophy that requires holistic organizational change and executive support. It highlights the importance of business agility, effective collaboration, and cultural shifts rather than solely focusing on IT. Additionally, it discusses the need for agile practices to improve efficiency, enhance communication, and foster a feedback-rich environment across all parts of the organization.
Debunking Four Myths of Agile Development Webcast
- 1. 1 Debunking Four Myths of Agile Development June 2015
- 2. 2 Why is Agility Needed in the Mainframe World Today?
- 3. 3 Why is Agility Needed in the Mainframe World Today?
- 4. 4 Four Myths About Agile Development There is only one way to do Agile development Agile development means faster development Only the IT organization is impacted Organizational procedures and structures don’t have to change
- 5. 5 THERE IS ONLY ONE WAY TO DO AGILE DEVELOPMENT
- 6. 6 • Agile values: – Individuals and interactions over processes and tools – Working software over comprehensive documentation – Customer collaboration over contract negotiation – Responding to change over following a plan • Don’t confuse “Agile” with its implementation Agile: Methodology, Framework or ? When we wrote the agile manifesto, we knew it was not a methodology, and not a framework, either. It was and is a value center, a way of looking at situations and thinking about how to proceed … Scrum, on the other hand, is a framework … Not a methodology, because it doesn’t even have enough in it to qualify as a methodology. -Alistair Cockburn (via blog post)
- 7. 7 Agile for Software Engineering
- 9. 9 Scrum Team Cross-functional Representation The Scrum team is critical to Agile’s success. It must be comprised of the right members from all disciplines that are needed to release the software product.
- 10. 10 Training • Formal Change Management training for key positions • Agile certification – Product Owner – Scrum Master • Agile team – Led by Scrum Master – Two day, self-paced • Agile frameworks – Kanban: maintenance – Scrum: enhancements • Scrum teams – Size: 7 ± 2 – Team > members • Dedicated Scrum room • Master Scrum Master – Pseudo Agile coach Agile Change at Compuware Organization
- 11. 11 AGILE DEVELOPMENT MEANS FASTER DEVELOPMENT
- 12. 12 • Set of minimum capabilities that a user would accept • Demonstrates future benefit to retain early adopters • Provides Agile team maximum amount of feedback MVP – Minimum Viable Product
- 13. 13 Efficient Task Execution Source: Multitasking Gets You There Later http://www.infoq.com/articles/multitasking-problems • Realize value sooner • Reduce context switching • Decrease total elapsed time
- 14. 14 Agile Testing • Integrated into design and development • Automated testing – At each build, sprint and milestone – Unit, integration and system testing • Applications designed for testing – Component architecture (Lego architecture) – Testing each component
- 15. 15 Agile Feeds DevOps DevOps is a culture of communication, collaboration, integration, automation and measurement of cooperation between software Development and Operations.
- 16. 16 • Fail safe vs. safe to fail • Small failures, recover quickly • Learn from failures and never repeat them • Align with 99.999 mainframe reliability – Requires CI (Continuous Integration) – Fail in development and test, not production! Fail Fast, Succeed Faster
- 17. 17 ONLY THE I.T. ORGANIZATION IS IMPACTED
- 18. 18 Business Agility is the Goal!
- 19. 19 Business Needs Are Met With Agility Source: The Agile Advantage, CMG Partners – Sixth Annual CMO Agenda
- 20. 20 It’s More Than Just Engineering
- 21. 21 ORGANIZATIONAL PROCEDURES AND STRUCTURES DON’T NEED TO CHANGE
- 22. 22 Agile Requires Executive Sponsorship Seriously, Agile requires changes in culture, processes and tools. It cannot succeed without executive management support.
- 23. 23 • Agility, flexibility and ability to embrace (constant) change • Continuous stakeholder feedback • Transparency and collaboration • Break down into granular initiatives • Automation of manual steps • Common instead of customized • Fail fast – learn and adapt Embrace Change Change is difficult, but essential! People embrace change differently. Implement change training, not just Agile development training.
- 24. 24 Culture Change at Compuware
- 25. 25 Myths Debunked Agile is a software development methodology
- 26. 26 Myths Debunked Agile is a software development methodology Agile is a philosophy, select the right methodology
- 27. 27 Myths Debunked Agile is a software development methodology Agile is a philosophy, select the right methodology Agile development means faster development
- 28. 28 Myths Debunked Agile is a software development methodology Agile is a philosophy, select the right methodology Agile development means faster development Agile development is about efficiency rather than speed
- 29. 29 Myths Debunked Agile is a software development methodology Agile is a philosophy, select the right methodology Agile development means faster development Agile development is about efficiency rather than speed Only the IT organization is impacted
- 30. 30 Myths Debunked Agile is a software development methodology Agile is a philosophy, select the right methodology Agile development means faster development Agile development is about efficiency rather than speed Only the IT organization is impacted Agile success requires agility throughout the business
- 31. 31 Myths Debunked Agile is a software development methodology Agile is a philosophy, select the right methodology Agile development means faster development Agile development is about efficiency rather than speed Only the IT organization is impacted Agile success requires agility throughout the business Organizational procedures and structures don’t have to change
- 32. 32 Myths Debunked Agile is a software development methodology Agile is a philosophy, select the right methodology Agile development means faster development Agile development is about efficiency rather than speed Only the IT organization is impacted Agile success requires agility throughout the business Organizational procedures and structures don’t have to change Agile requires a change in culture, tools and processes
- 33. 33 • Agile Software Development is Engineering’s contribution to Business Agility • Focus on creating alignment with the rest of the business • Quality is the responsibility of the team: win or lose as a team • Collaborate and be transparent throughout the entire business, not just within IT Final Thoughts: Keys to Success
- 34. 34 © 2015 Compuware Corporation. All rights reserved.
Editor's Notes
- #3: The mainframe is an integral part of an enterprise’s digital economy strategy
- #4: The mainframe is an integral part of an enterprise’s digital economy strategy
- #10: Key Roles: Product Owner and ScrumMaster Two week Sprints Solely focused on delivering objectives per Sprint Autonomy for the Success or Failure of the team Team first, no individuals Does whatever is needed for the team to win
- #12: It’s about focus and frequency.
- #21: Pre-Agile: Release Planning - Backlog Product Management: What, When, Why MVP: Minimum Viable Product EPIC Breakdown Post-Agile: Go-To-Market (GTM) Training of Sales, FTS, Support, etc… Awareness: Analysts, Media, etc… Collateral: Brochures, Presentations, Whitepapers, etc… This is from a software vendor perspective. Companies that do internal software development will have similar concepts.