Introduction to Agile for SIPA
1 like1,133 views
This document discusses an alternative software development methodology called Agile. It describes some issues with traditional waterfall methods, such as inflexibility to change, and advocates for adopting Agile practices like Scrum which emphasize adaptability, working software, and responding to change. The document outlines Agile principles including iterative development, collaborative team structures, and an emphasis on individuals and interactions over processes and tools.
Introduction to Agile for SIPA
- 1. An Alternative Software Development Methodology By @roofimon Scrum Master Opendream™ Tuesday, June 12, 12
- 2. 2001 Tuesday, June 12, 12
- 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 12, 12
- 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 12, 12
- 5. Tuesday, June 12, 12
- 6. Tuesday, June 12, 12
- 7. Software Development ? Tuesday, June 12, 12
- 8. Construction Architect Engineering Labor Work Tuesday, June 12, 12
- 9. Construction Software Architect Software Engineering Software Worker (programmer) Tuesday, June 12, 12
- 10. We were forced to believed in that. Tuesday, June 12, 12
- 11. How many ways can we construct the building? Tuesday, June 12, 12
- 12. How many ways can we construct software? Tuesday, June 12, 12
- 13. As long as, user can change , adjust software to fit into their requirements. Tuesday, June 12, 12
- 14. Software Development is Craftsmanship Tuesday, June 12, 12
- 16. Methodology • Team Structure • Team Discipline • Individual Discipline Tuesday, June 12, 12
- 17. The greatest waterfall Tuesday, June 12, 12
- 18. The greatest waterfall Tuesday, June 12, 12
- 19. Team Discipline • Document Oriented • Each step has clearly definition of document standard • Timeline is king • Change is bad !!!!! Tuesday, June 12, 12
- 20. Team Structure • Silo • Clearly responsibility Tuesday, June 12, 12
- 21. 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 12, 12
- 22. Finally • Our software is same as building. Once it done you can’t change it. Tuesday, June 12, 12
- 23. We need change! Tuesday, June 12, 12
- 24. Agile Tuesday, June 12, 12
- 25. Agile Tuesday, June 12, 12
- 26. Tuesday, June 12, 12
- 27. Team Structure • One single team • Break the damn silo Tuesday, June 12, 12
- 28. Team Discipline • Change is good • We love change • Eliminate unchangeable modules Tuesday, June 12, 12
- 29. Individual Discipline • Super Clear and have to follow • Test : Code : Refactor Tuesday, June 12, 12
- 30. The beginning of agile • Choose few agile practices and adopted into your team. Tuesday, June 12, 12
- 31. Agile Methods Extreme Programming Scrum Kanban Tuesday, June 12, 12
- 32. Scrum • is a framework for running projects • defines a set of activities for moving faster Tuesday, June 12, 12
- 33. Tuesday, June 12, 12
- 34. User Story Tuesday, June 12, 12
- 35. User Stories Tuesday, June 12, 12
- 36. Tuesday, June 12, 12
- 37. Tuesday, June 12, 12
- 38. Tuesday, June 12, 12
- 39. Tuesday, June 12, 12
- 40. Whole Team? • Same Mind set for the whole team Tuesday, June 12, 12
- 42. We need tools Tuesday, June 12, 12
- 43. Tools • Project Management • Software Development • Software Testing • Software Delivery Tuesday, June 12, 12
- 44. Tuesday, June 12, 12
- 45. Agile PM tool Tuesday, June 12, 12
- 46. Version Control Software Tuesday, June 12, 12
- 47. Tuesday, June 12, 12
- 49. Tuesday, June 12, 12
- 50. Tuesday, June 12, 12
- 51. Tuesday, June 12, 12
- 52. C U on July 12-14 Tuesday, June 12, 12