Agile Method Report

1. Agile Method Report 黃柏軒 MIAT Lab., CSIE, NCU 2012/05/21

2. Title: A Capstone Course on Agile Software Development Using Scrum • Author(s): MahnicViljan • Source: IEEE TRANSACTIONS ON EDUCATION • Volume: 55 Issue: 1 Pages: 99-106 • Published: FEB 2012

3. Outline • Background • Course Design • Project Setting • Evaluation • Comparison • Learned and Recommendations

4. Background • Capstone Courses • Agile method vs. traditional plan-driven approach • XP vs. Scrum

5. Course Design

6. Project Setting • Product Owner and Scrum Master • Initial Product Backlog (60 user stories) • Divide into four groups (priority) • Planning poker estimation

7. General Evaluation

8. Result of the First Part

9. Result of the Second Part

10. Comparison • planned, reported and actual achievement

11. Comparison • estimated and actual effort

12. Learned and Recommendations • Teaching Agile Methods Is Best Done Through Projects and Practical Work • Role of the Product Owner Is Crucial for the Success of a Scrum Project • Scrum Master Largely Performs Guardian Tasks • Notion of “Done” Should Be Imparted to Students as Soon as Possible

13. Learned and Recommendations • Concepts of User Stories Are Best Imparted to Students Through Practical Work, but Only if Good Communication Is Established Between the Product Owner and the Team • Daily Scrum Meetings Must Not Be for Reporting to the Scrum Master, but for the Team Members to Inform Each Other About the Current State of the Project

14. Learned and Recommendations • Estimating and Planning Is a Difficult Task, but Can Improve Through Practice • Conducting the Course as an Observational Study Is Beneficial for All Parties Involved • Traditional Disciplined Approach Can Be Incorporated, but in an Appropriate Way That Preserves Agility

15. Thanks for your attention!