Agile Software Development Methodology
•
0 recomendaciones•2,198 vistas
The document discusses an alternative software development methodology called Agile. It provides an overview of Agile principles and practices like test-driven development, continuous integration, and user stories. It compares Agile methods like Scrum and Extreme Programming (XP) to traditional waterfall methods. The document also discusses tools that support Agile development like project management, version control, IDE, and testing tools.
Recomendados
Más contenido relacionado
Similar a Agile Software Development Methodology
Similar a Agile Software Development Methodology (20)
Más de ทวิร พานิชสมบัติ
Más de ทวิร พานิชสมบัติ (20)
Último
Último (20)
Agile Software Development Methodology
- 1. An Alternative Software Development Methodology By @d4jens @9tae and @roofimon Tuesday, June 28, 2011
- 2. 2001 Tuesday, June 28, 2011
- 3. Hybrid Theory was a massive commercial success; it sold more than 4.8 million copies during its debut year, earning it the status of best-selling album of 2001, while singles such as "Crawling" and "One Step Closer" established themselves as staples among alternative rock radio play lists during the year. Tuesday, June 28, 2011
- 4. In February 2001, 17 software developers met at the Snowbird, Utah resort, to discuss lightweight development methods. They published the Manifesto for Agile Software Tuesday, June 28, 2011
- 5. Tuesday, June 28, 2011
- 6. Tuesday, June 28, 2011
- 7. Agenda • Morning Session • Agile Development Methodology • Agile Development Life Cycle • Agile Development Tools • Afternoon Session • Agile Development Best Practice Tuesday, June 28, 2011
- 8. Software Development ? Tuesday, June 28, 2011
- 9. Construction Architect Engineering Labor Work Tuesday, June 28, 2011
- 10. Construction Software Architect Software Engineering Software Worker (programmer) Tuesday, June 28, 2011
- 11. We were forced to believed in that. Tuesday, June 28, 2011
- 12. How many ways can we construct the building? Tuesday, June 28, 2011
- 13. How many ways can we construct software? Tuesday, June 28, 2011
- 14. As long as, user can change , adjust software to fit into their requirements. Tuesday, June 28, 2011
- 15. Software Development is Craftsmanship Tuesday, June 28, 2011
- 16. Methodology Tuesday, June 28, 2011
- 17. Methodology • Team Structure • Team Discipline • Individual Discipline Tuesday, June 28, 2011
- 18. The greatest waterfall Tuesday, June 28, 2011
- 19. The greatest waterfall Tuesday, June 28, 2011
- 20. Team Discipline • Document Oriented • Each step has clearly definition of document standard • Timeline is king • Change is bad !!!!! Tuesday, June 28, 2011
- 21. Team Structure • Silo • Clearly responsibility Tuesday, June 28, 2011
- 22. Individual Discipline • Mostly make something “done” but not “right” • Mostly said “please don’t change it” • Mostly make it for last, not for change Tuesday, June 28, 2011
- 23. Finally • Our software is same as building. Once it done you can’t change it. Tuesday, June 28, 2011
- 24. We need change! Tuesday, June 28, 2011
- 25. Agile Tuesday, June 28, 2011
- 26. Agile Tuesday, June 28, 2011
- 27. Discipline • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan Tuesday, June 28, 2011
- 28. Team Structure • One single team • Break the damn silo Tuesday, June 28, 2011
- 29. Team Discipline • Change is good • We love change • Eliminate unchangeable modules Tuesday, June 28, 2011
- 30. Individual Discipline • Super Clear and have to follow • Test : Code : Refactor Tuesday, June 28, 2011
- 31. The beginning of agile • Choose few agile practices and adopted into your team. Tuesday, June 28, 2011
- 32. Agile Methods Extreme Programming Scrum Kanban Tuesday, June 28, 2011
- 33. eXtreme Programming XP is a set of practices that conform to the values and principles of Agile. XP is a discrete method, whereas Agile is a classification. Tuesday, June 28, 2011
- 34. Tuesday, June 28, 2011
- 35. Question? • Developers, Do you write automate test? • Why do you write test? • What is the benefit of testing? Tuesday, June 28, 2011
- 36. Pin XP on TDD Tuesday, June 28, 2011
- 37. Tuesday, June 28, 2011
- 38. Why TCR? • Confident to change • Quality is good • Executable document • Continuous delivery • Customer happy :) Tuesday, June 28, 2011
- 39. Tuesday, June 28, 2011
- 40. Tuesday, June 28, 2011
- 41. Whole Team? • Same Mind set for the whole team Tuesday, June 28, 2011
- 42. “Sustainable” Tuesday, June 28, 2011
- 43. Continuous Integration Tuesday, June 28, 2011
- 44. We need tools Tuesday, June 28, 2011
- 45. Tools • Project Management • Software Development • Software Testing • Software Delivery Tuesday, June 28, 2011
- 46. User Story Tuesday, June 28, 2011
- 47. User Stories Tuesday, June 28, 2011
- 48. Tuesday, June 28, 2011
- 49. Agile PM tool Tuesday, June 28, 2011
- 50. Tuesday, June 28, 2011
- 51. Agile PM tool Tuesday, June 28, 2011
- 52. Version Control Software Tuesday, June 28, 2011
- 53. Software Development • Maven2 : Project Lifecycle Management • Version Control Software • IDE • Framework Tuesday, June 28, 2011
- 54. • Project Structure • Build • Dependency Management • Test • Style Checking • Code Coverage Tuesday, June 28, 2011
- 55. Maven 2 Providing a uniform build system ๏ Providing quality project information ๏ Providing guidelines for best practices development ๏ Allowing transparent migration to new features ๏ Making the build process easy Tuesday, June 28, 2011
- 56. IDE doesn’t matter as long as it has maven plugin Tuesday, June 28, 2011
- 57. Framework is matter • Structure, Definition and Rules • Provide Complete Test Cycle Tuesday, June 28, 2011
- 58. Let’s see how TCR work? Tuesday, June 28, 2011
- 59. Tuesday, June 28, 2011