Project management
•
0 likes•365 views
This document provides an introduction to agile project management and Scrum. It defines key concepts like the product backlog, sprint backlog, and Scrum roles. It compares the traditional waterfall lifecycle to the iterative nature of agile and Scrum. Key questions are presented around defining tasks as complete and defining project success.
Project management
- 1. Introduction to Agile Project Management Vasilij Savin AACIMP 2011
- 2. What is a project?
- 7. Scrum
- 9. Scrum Roles Scrum Master Product Owner
- 10. Scrum Roles Scrum Team Scrum Master Product Owner
- 11. Questions for discussion When is a task When a project is complete? considered to be a (Definition of Done) failure? (Definition of Success)
- 12. Scrum
- 13. ≠
- 14. Agile (XP) Rules ● Have sustainable pace (no overtime) ● Have people work on different modules to learn ● Pair Programming ● Coding standards ● Integration ● Create automated test suite ● Write a test to replicate the bug
- 15. QUESTIONS?
- 16. Extra Slides
- 17. Waterfall pros ● Produces what is specified ● Supports large teams ● High resource efficiency ● Clear division of labour
- 18. Waterfall cons ● Results delivered by the end of project cycle ● Requires a lot of documentation ● Everyone has very narrow view of the project ● Scope is very inflexible ● Gives an illusion of control
- 19. Scrum ● Alternative project management technique ● 3 main roles – Team (7+-2) – Scrum Master, facilitator, team support – Product Owner, customer representative
- 20. Scrum concepts ● Product Backlog ● Sprint Backlog ● Scrum board / Burndown chart
- 21. Scrum activities ● Sprint planning/planning poker ● Sprint / Daily Scrum ● Demonstration / Retrospective
- 22. Task break down ● User stories ● Story estimate by team ● Story broken down into tasks
- 23. Resources ● http://www.extremeprogramming.org/rules.html ● http://www.implementingscrum.com/
- 24. Laws ● “adding manpower to a late software project makes it later” Brook's law