Basics of Agile Methodology
•Download as PPTX, PDF•
0 likes•106 views
This PPT can be used to demonstrate basic methodologies of Agile. Its Pros and Cons over Waterfall and the terminologies used within it.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Basics of Agile Methodology
Similar to Basics of Agile Methodology (20)
Recently uploaded
Recently uploaded (20)
Basics of Agile Methodology
- 2. Topics to be covered.. What is Agile? Historical development model vs Agile Agile Terminologies Framework Usage/Benefits
- 3. What is Agile? Agile proponents believe ◦ Current software development processes are too heavyweight or cumbersome Too many things are done that are not directly related to software product being produced ◦ Current software development is too rigid Difficulty with incomplete or changing requirements Short development cycles (Internet applications) ◦ More active customer involvement needed CMM focuses on process Agile methods are considered ◦ Lightweight ◦ People-based rather than Plan-based
- 5. Communication Modes Always Strive to Use the Most Effective Approach
- 6. Agile Software Requirements Management
- 7. Scrum characteristics • Iterative and incremental agile software development method • Self-organizing teams • Product progresses in a series of month-long “sprints” • Requirements are captured as items in a list of “product backlog” • One of the “agile processes”
- 8. Sprint • Scrum projects make progress in a series of “sprints” • Typical duration is 2–4 weeks or a calendar month at most • A constant duration leads to a better rhythm • Product is designed, coded, and tested during the sprint • No changes during the sprint
- 9. Scrum Framework Roles • Product Owner • Scrum Master • Team Ceremonies • Sprint Planning • Sprint Review • Sprint Retrospective • Daily Scrum Meeting Artifacts • Product Backlog • Sprint Backlog • Burn down Charts
- 10. Sprint Burn down Chart Progress 752 762 664 619 304 264 180 104 200 100 200 300 400 500 600 700 800 900 5/3/2002 5/5/20025/7/2002 5/9/2002 5/11/2002 5/13/2002 5/15/2002 5/17/2002 5/19/2002 5/21/2002 5/23/2002 5/25/2002 5/27/2002 5/29/2002 5/31/2002 Date RemainingEffortinHours
- 11. Pros/Cons Advantages Drawbacks Completely developed and tested features in short iterations “Undisciplined hacking” (no written documentation) Simplicity of the process Violation of responsibility Increasing productivity Currently mainly carried by the inventors Self-organizing Each team member carries a lot of responsibility Improved communication
- 12. Thank You!!