Image by Philly Gryphons RFC Scrum
What is it?
An agile development methodology
Details?
Scrum has three primary areas of focus
1) Definition of roles
2) Existence of backlogs
3) Time-boxed meetings
Know your role
Two classes of people
Image by KB35
Image by rumpleteaser
A chicken and pig start a breakfast shop called “Bacon & Eggs”
The chicken has an interest in the project
But the pig has skin in the game
Core roles
Scrum Master
Enforces Scrum practices
Removes roadblocks
Closest role to a project manager
Product owner
Maintains the product backlog
Creates user stories
Sets preferred order of completion
Business owner for the project
The team
Designers, Developers, QA, etc.
Own workload for a given cycle
Set expectations
Deliver on promises
Artifacts of Scrum
Product backlog
Prioritized list of user stories
Created and ranked by product owner
Sprint backlog
List of user stories selected from the product backlog
Selected by the team, not the product owner
All tasks in the sprint backlog should fit into one sprint cycle
What is this sprint thing?
A sprint is a 30 day work cycle
At the beginning of a sprint user stories are selected
Selected by the team, not the product owner
This is the most difficult transition for an organization to make
At the end of the sprint these same user stories are demonstrated
Demonstrated as fully-functional, shippable, unit-tested deliverables
Shippable
in 30 days
The team controls the workload
And must be honest and accurate in estimates
Constant feature delivery builds trust
And makes it easier for the business to buy-in to scrum
Time-boxed meetings
Sprint planning meeting
8 hours
First four hours for the product owner presenting the product backlog
Final four hours for the team deciding on workload and doing initial design and estimation
Daily sprint meeting
15 minutes
What did you do?
What are you going to do?
Do you have any roadblocks?
Sprint Expo
4 hours
End of sprint show-and-tell
Sprint retrospective
4 hours
What went wrong this sprint?
What went right this sprint?
That seems like a lot of meetings
8 + (.25*20) + 4 + 4 = 21 hours of meetings
21 hours of 176 hours = 17% overhead
21 hours of 176 hours = 17% overhead
Significant, but workable
That's Scrum
Upcoming SlideShare
Loading in …5
×

Lightning Talk: An Introduction To Scrum

9,144 views
8,349 views

Published on

Josh McAdams presents an introduction to Scrum at the Nordic Perl Workshop 2007.

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

No Downloads
Views
Total views
9,144
On SlideShare
0
From Embeds
0
Number of Embeds
56
Actions
Shares
0
Downloads
284
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Lightning Talk: An Introduction To Scrum

  1. Image by Philly Gryphons RFC Scrum
  2. What is it?
  3. An agile development methodology
  4. Details?
  5. Scrum has three primary areas of focus
  6. 1) Definition of roles
  7. 2) Existence of backlogs
  8. 3) Time-boxed meetings
  9. Know your role
  10. Two classes of people
  11. Image by KB35
  12. Image by rumpleteaser
  13. A chicken and pig start a breakfast shop called “Bacon & Eggs”
  14. The chicken has an interest in the project
  15. But the pig has skin in the game
  16. Core roles
  17. Scrum Master
  18. Enforces Scrum practices
  19. Removes roadblocks
  20. Closest role to a project manager
  21. Product owner
  22. Maintains the product backlog
  23. Creates user stories
  24. Sets preferred order of completion
  25. Business owner for the project
  26. The team
  27. Designers, Developers, QA, etc.
  28. Own workload for a given cycle
  29. Set expectations
  30. Deliver on promises
  31. Artifacts of Scrum
  32. Product backlog
  33. Prioritized list of user stories
  34. Created and ranked by product owner
  35. Sprint backlog
  36. List of user stories selected from the product backlog
  37. Selected by the team, not the product owner
  38. All tasks in the sprint backlog should fit into one sprint cycle
  39. What is this sprint thing?
  40. A sprint is a 30 day work cycle
  41. At the beginning of a sprint user stories are selected
  42. Selected by the team, not the product owner
  43. This is the most difficult transition for an organization to make
  44. At the end of the sprint these same user stories are demonstrated
  45. Demonstrated as fully-functional, shippable, unit-tested deliverables
  46. Shippable
  47. in 30 days
  48. The team controls the workload
  49. And must be honest and accurate in estimates
  50. Constant feature delivery builds trust
  51. And makes it easier for the business to buy-in to scrum
  52. Time-boxed meetings
  53. Sprint planning meeting
  54. 8 hours
  55. First four hours for the product owner presenting the product backlog
  56. Final four hours for the team deciding on workload and doing initial design and estimation
  57. Daily sprint meeting
  58. 15 minutes
  59. What did you do?
  60. What are you going to do?
  61. Do you have any roadblocks?
  62. Sprint Expo
  63. 4 hours
  64. End of sprint show-and-tell
  65. Sprint retrospective
  66. 4 hours
  67. What went wrong this sprint?
  68. What went right this sprint?
  69. That seems like a lot of meetings
  70. 8 + (.25*20) + 4 + 4 = 21 hours of meetings
  71. 21 hours of 176 hours = 17% overhead
  72. 21 hours of 176 hours = 17% overhead
  73. Significant, but workable
  74. That's Scrum

×