what_should_we_consider_when_forming_a_new_team
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
what_should_we_consider_when_forming_a_new_team [2017/03/06 19:40] – [Need To Know More?] hpsamios | what_should_we_consider_when_forming_a_new_team [2017/03/06 19:42] – [Background] hpsamios | ||
---|---|---|---|
Line 10: | Line 10: | ||
If you read the books, the guidelines for team formation include: | If you read the books, the guidelines for team formation include: | ||
- | * Size: Scrum Teams are typically 7 members, plus or minus 2, counting the Scrum Master, but not counting the Product Owner. | + | * Size: Teams are typically 7 members, plus or minus 2, counting the Scrum Master, but not counting the Product Owner. |
* Roles: Specific definition of full time Product Owner and Scrum Master. | * Roles: Specific definition of full time Product Owner and Scrum Master. | ||
- | * Make-up: Teams should be cross-functional, | + | * Make-up: Teams should be cross-functional, |
* Characteristics: | * Characteristics: | ||
- | * Co-location: | + | * Co-location: |
* Team structure: Oriented toward the delivery of value from the end user / customer perspective. | * Team structure: Oriented toward the delivery of value from the end user / customer perspective. | ||
* Consistent: Teams stay together. | * Consistent: Teams stay together. |
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/what_should_we_consider_when_forming_a_new_team.txt · Last modified: 2022/02/23 07:05 by hans