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