Confirmed users
1,193
edits
Scrum/Guide: Difference between revisions
no edit summary
(→Roles) |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
These notes provide additional thoughts on [http://www.youtube.com/watch?v=Q5k7a9YEoUI Scrum Master in Under 10 Minutes], an instructional video which provides a surprisingly good overview of the methodology. Topics are discussed in the order that they are presented in the video. | These notes provide additional thoughts on [http://www.youtube.com/watch?v=Q5k7a9YEoUI Scrum Master in Under 10 Minutes], an instructional video which provides a surprisingly good overview of the methodology despite a 90s-era techno soundtrack. Topics are discussed in the order that they are presented in the video. | ||
==Product Backlog== | ==Product Backlog== | ||
| Line 16: | Line 16: | ||
* It is sometimes useful to create subteams within large development groups. In such a setup, high-level requirements might be communicated to a team lead ("Users must be able to visit the site homepage"), with lower-level requirements communicated by the team lead to individual developers ("Users must be able to identify the site by reading the header", "Users must be able to get more information by reading the footer", etc.). | * It is sometimes useful to create subteams within large development groups. In such a setup, high-level requirements might be communicated to a team lead ("Users must be able to visit the site homepage"), with lower-level requirements communicated by the team lead to individual developers ("Users must be able to identify the site by reading the header", "Users must be able to get more information by reading the footer", etc.). | ||
In general, teams tend to be organized | ===Responsibilities=== | ||
In general, teams tend to be organized such that each role has the following responsibilities. | |||
* Everyone | * Everyone | ||