Introduction to Agile Development
4 likes840 views
This document provides an introduction to agile development. It begins by noting some common questions about agile and what will be discussed. The document then covers basic agile concepts like the history of agile, the agile manifesto, and agile principles. It provides a quick comparison of waterfall vs. agile development. Common agile methods like Scrum and Kanban are mentioned. Finally, it discusses some common pitfalls in agile, such as treating sprints like waterfall phases or allowing technical debt to build up.
Introduction to Agile Development
- 2. Why do we discuss this topic today? Because Hai is sida!
- 3. Some noted questions ￭ Why do we need to understand Agile? ￭ Why is Scrum/Kanban agile? ￭ Is Agile hard? ￭ How can Agile be applied to outsourced agencies? ￭ How to measure personal performance with Agile? ￭ Many more ...
- 4. What will we discuss? 1. Basic Concepts of Agile 2. Overview of Scrum and Kanban 3. Common Agile Pitfalls
- 5. Basic Concepts of Agile The history, values, Agile Manifesto, principles 1
- 6. Waterfall vs. Agile - A quick look Source: Scaled Agile, Inc.
- 7. However ... Iterative and incremental development are not Agile.
- 8. You are agile if ... ￭ value the same things as listed in the Agile Manifesto ￭ no standard template or checklist or procedure to "do agile"
- 9. Agile Manifesto ￭ When: Feb 2001 ￭ Where: At Snowbird resort in Utah ￭ Who: 17 software developers from XP, SCRUM, DSDM, ASD, Crystal, FDD, Pragmatic, etc.
- 10. Agile Manifesto
- 12. Principles behind the Agile Manifesto 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
- 13. Principles behind the Agile Manifesto 2. Welcome changing requirements, even in late development.
- 14. Principles behind the Agile Manifesto 3. Working software is delivered frequently
- 15. Principles behind the Agile Manifesto 4. Business people and developers must work together daily throughout the project.
- 16. Principles behind the Agile Manifesto 5. Projects are built around motivated individuals, who should be trusted.
- 17. Principles behind the Agile Manifesto 6. Face-to-face conversation is the best form of communication (co-location)
- 18. Principles behind the Agile Manifesto 7. Working software is the principal measure of progress
- 19. Principles behind the Agile Manifesto 8. Best architectures, requirements, and designs emerge from self-organizing teams Complex Adaptive System Theory
- 20. Common Agile Methods SCRUM, Kanban 2
- 21. SCRUM More detail in Part 2
- 22. Kanban More detail in Part 2
- 23. Common Agile Pitfalls It’s not always working 3
- 24. Common Agile Pitfalls People try to learn Agile to look for some new “practices”, some new “processes” to employ them into their existing systems.
- 25. Common Agile Pitfalls Waterfall of “sprints”
- 26. Common Agile Pitfalls Lack of commitment from business.
- 27. Common Agile Pitfalls Inability of programmers and business people to understand each other.
- 28. Common Agile Pitfalls Lack of overall project design. Failure to pay attention to design can cause a team to proceed rapidly at first but then to have significant rework required as they attempt to scale up the system.
- 29. Common Agile Pitfalls Allowing technical debt to build up.
- 30. Common Agile Pitfalls Developers use the guise of Agile to avoid planning and to avoid creating documentation required for future maintenance.
- 31. Common Agile Pitfalls Student syndrome
- 32. Common Agile Pitfalls Stand-up meeting as report duty.
- 33. Thanks!Any questions? Yes, slide #3 My answers to slide #3 questions are not in these slides. You can find me at http://tuhoang.me See you in part 2
- 34. Credits Special thanks to all the people who made and released these awesome resources for free: ￭ Presentation template by SlidesCarnival ￭ Photographs by Unsplash & Death to the Stock Photo (license)