Scrum
  An agile Overview
Introduction

   Scrum
       Simple framework for project management
       Is Agile
       Is Iterative

   Values
...
The Framework
Roles

   Product Owner
     Keep update the Product Backlog

     Add business value to user stories

     Certify th...
Chickens & Pigs

   Chickens
       Can not talk in the daily meetings
       Involved in the project
   Pigs
       ...
Artifacts - Product Backlog

   Keep updated by the Product Owner
   Divided in user stories
   User stories are sorted...
Artifacts – Sprint & Sprint Backlog

   Always same duration (1-4 weeks)
   User stories are split in small tasks (ideal...
Artifacts – Task Board

   Visible to all team
   Columns
       ToDo
       Doing
       Done




   Also Burn down...
Meetings – Sprint Planning

   Participants
       Team, SM, PO, others stakeholders
   User stories are split into sho...
Meetings – Daily Meeting

   All days meeting
   All team involved in the meeting
   Reporting to the team, rather to a...
Meetings - Retrospective

   Take place to the end of the sprint
   All people can talk
   The team reflects on its own...
Conclusion

   Scrum..
       Is Easy
       Is Hard
       Works
Links

   http://www.scrumalliance.org/
   http://www.implementingscrum.com/
   http://www.controlchaos.com/
   http:/...
Upcoming SlideShare
Loading in …5
×

Scrum

549
-1

Published on

Scrum, an agile overview

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
549
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Scrum

  1. 1. Scrum An agile Overview
  2. 2. Introduction  Scrum  Simple framework for project management  Is Agile  Is Iterative  Values  Focus on people  Empowered and committed teams  Self-Managed
  3. 3. The Framework
  4. 4. Roles  Product Owner  Keep update the Product Backlog  Add business value to user stories  Certify the final product  ScrumMaster  Maintains the processes  Facilitator  Help to resolve impediments  No authority on the team  Team  Cross functional  Involved in tasks  Self-Managed
  5. 5. Chickens & Pigs  Chickens  Can not talk in the daily meetings  Involved in the project  Pigs  Can talk in daily meetings  Committed in the project
  6. 6. Artifacts - Product Backlog  Keep updated by the Product Owner  Divided in user stories  User stories are sorted by business value  The team estimates the effort of user stories (usually in points)  Large items are split and clarified
  7. 7. Artifacts – Sprint & Sprint Backlog  Always same duration (1-4 weeks)  User stories are split in small tasks (ideally 1 day effort)  Visible increments  Task “Done”
  8. 8. Artifacts – Task Board  Visible to all team  Columns  ToDo  Doing  Done  Also Burn down chart is used
  9. 9. Meetings – Sprint Planning  Participants  Team, SM, PO, others stakeholders  User stories are split into short tasks  The team committed the tasks
  10. 10. Meetings – Daily Meeting  All days meeting  All team involved in the meeting  Reporting to the team, rather to a boss  15 minutes duration  Team must answer  What they did?  What they are doing?  Do they have problems?
  11. 11. Meetings - Retrospective  Take place to the end of the sprint  All people can talk  The team reflects on its own process  Idea is do better what is wrong and improve what is right
  12. 12. Conclusion  Scrum..  Is Easy  Is Hard  Works
  13. 13. Links  http://www.scrumalliance.org/  http://www.implementingscrum.com/  http://www.controlchaos.com/  http://www.jeffsutherland.com/

×