Scrum/Guide: Difference between revisions

Jump to navigation Jump to search
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 as such:
===Responsibilities===
 
In general, teams tend to be organized such that each role has the following responsibilities.


* Everyone
* Everyone
Confirmed users
1,193

edits

Navigation menu