Agile challenges
Download as PPTX, PDF1 like570 views
The document discusses the principles of agile software development, emphasizing customer satisfaction, responsiveness to change, and collaboration among team members. It identifies common challenges faced in agile practices, including business-related issues like budgeting and transitioning from traditional project management, as well as team and individual challenges. Strategies for overcoming these obstacles, such as fostering trust, enhancing team commitment, and employing test-driven approaches, are also outlined.
Agile challenges
- 1. OVERCOMING CHALLENGES IN AGILE David Yancey
- 2. DAVID YANCEY @davidyancey www.david-yancey.com dave@david-yancey.com www.linkedin.com/in/davidyancey about.me/davidyancey
- 3. AGILE MANIFESTO We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
- 4. 12 PRINCIPLES OF AGILE SOFTWARE Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project.
- 5. 12 PRINCIPLES OF AGILE SOFTWARE Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
- 6. 12 PRINCIPLES OF AGILE SOFTWARE Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
- 7. COMMON CHALLENGES Business/Corporate Challenges Team Challenges Individual Challenges
- 8. BUSINESS/CORPORATE CHALLENGES Estimating / Budgeting Transition from traditional project management Documentation Trust
- 10. ESTIMATING / BUDGETING No approved budget with out estimates Estimates are inherently inaccurate Estimate often Adjust Estimations Communicate Estimations
- 11. TRANSITION FROM TRADITIONAL PROJECT MANAGEMENT Understand the differences Given-Choose-Adjust
- 12. DOCUMENTATION It’s in the story
- 13. TRUST Attempts breeds failure Failure breeds Success Success breeds trust Communication of the above ensures trust
- 14. TEAM CHALLENGES Team Commitment Team Involvement Off-shore/Off-site teams
- 15. TEAM COMMITMENT Understand the commitment Own the commitment Stand-up for the commitment
- 16. TEAM RESPONSIBILITIES Understand the team Don’t leave anyone out
- 17. OFF-SHORE/OFF-SITE TEAMS Isolated stories Team Liaison
- 18. INDIVIDUAL CHALLENGES Test Driven approach QA/Developer toss back Silo avoidance Knowing when your done
- 19. TEST DRIVEN APPROACH Start with functional test Let the test drive the design Test => Test.Morf(UnitTest)
- 20. QA/DEVELOPER TOSS BACK Pair QA Pair up to write UAT
- 21. SILO AVOIDANCE Drive-by Pair Programming Story sharing
- 22. KNOWING WHEN YOUR DONE Create Done Chart Create UAT before Coding
Editor's Notes
- #5: Business people and developers must work together daily throughout the project.Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- #6: Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.The most efficient and effective method of conveying information to and within a development team is face-to-face conversation
- #7: Simplicity--the art of maximizing the amount of work not done--is essential.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
- #12: Risk-Tradeoff: Given fixed ____________, we will choose a ___________ and adjust ___________ as necessary.
- #16: The team commits to the prioritized items, when the commitment is pushed onto the team it is no longer the teams commitment
- #17: Who is the team? QA / Dev’s / Skin in the gameTeam is involved in commitment, story development, story sizing, story demo’s