Differences

This shows you the differences between two versions of the page.

--- what_should_we_consider_when_forming_a_new_team [2017/03/02 06:17] – [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:
-  * 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.
-  * Make-up: Teams should be cross-functional, containing development, certification, documentation and subject matter experts.
+  * Make-up: Teams should be cross-functional, containing development, certification, documentation and subject matter experts, whatever is required to deliver value.
   * Characteristics: The best initial Scrum Teams are formed with people who have worked together previously, people who understand the problem or domain and people who know how to use the technology.
-  * Co-location: Scrum Teams work best when co-located.
+  * Co-location: Scrum Teams work best when co-located. And if you cannot do co-location, then at least ensure that team members are in the same time zone - co-timezone?
   * Team structure: Oriented toward the delivery of value from the end user / customer perspective.
   * Consistent: Teams stay together.
@@ Line 51: / Line 51: @@
   * [[what_is_the_role_of_the_scrum_master|What is the Role of a Scrum Master?]]
   * [[why_shouldn_t_we_set_up_dedicated_defect_teams|Why Shouldn't We Set Up Dedicated Defect Teams?]]
+  * [[why_do_we_form_teams_when_we_transition_to_agile|Why Do We Form Teams When We Transition To Agile?]]
+Also see:
   * [[self_forming_teams|Self-Forming Teams]] is an alternative approach to this problem
-  * [[https://www.mountaingoatsoftware.com/blog/cross-functional-doesnt-mean-everyone-can-do-everything|Cross-finctional Doesn't Mean Everyone Can Do Anything]] - A note by Mike Cohn. We are not trying to create a team where everyone is a generalist.
+  * [[how_do_we_get_all_the_work_addressed_when_our_specialists_cannot_be_everywhere|How Do We Get All the Work Addressed When Our Specialists Cannot Be Everywhere?]]