Difference between revisions of "Team charter"

From Pearl Language
Jump to navigation Jump to search
(Zeroth version.)
 
(Zeroth version.)
Line 1: Line 1:
{{Oyster
|stage=Sparkle
|theme=Agile, Scrum
|context=a group of people or animals linked in a common purpose.
|wish in a single line=Self-organization is both powerful and efficient and does not require management. How do you steer a swarm, though?
|therefore in a single line=Set up a light-weight and comprehensive document that outlines values, behavior, principles and practices for the crew.
|wish=Self-organization is both powerful and efficient and does not require management. How do you steer a swarm, though?
|therefore=Set up a light-weight and comprehensive document that outlines values, behavior, principles and practices for the crew. Over time, evolve it into one or more {{p|excellence guide}}s and a {{p|codex}}.
}}
==Self-organizing Team==
==Self-organizing Team==
*Team—A group of people or animals linked in a common purpose.
*Team—A group of people or animals linked in a common purpose.
Line 107: Line 116:
*Harrison Owen, Wave Rider: ''Leadership for High Performance in a Self-Organizaing World''
*Harrison Owen, Wave Rider: ''Leadership for High Performance in a Self-Organizaing World''
*A modern English translation of the Magna Carta of 1215
*A modern English translation of the Magna Carta of 1215
{{Source
|author=Martien van Steenbergen,
|coder={{mvs}}
}}

Revision as of 10:44, 2 September 2012

…a group of people or animals linked in a common purpose.

✣  ✣  ✣

{{{wish full}}}


Therefore:

{{{therefore full}}}

✣  ✣  ✣



✣  ✣  ✣

Self-organizing Team

  • Team—A group of people or animals linked in a common purpose.
  • Self-organization is the tendency of an open system to generate new structures and patterns based on its own internal dynamics. Organization design is not imposed from above or outside; it emerges from the interactions of the agents in the system. Facilitating Organization Change: Lessons from Complexity Science
  • Three factors influence the patterns that emerge:
    1. The container sets the bounds for the self-organizing system. It defines the “self” that organizes.
    2. Significant differences determine the primary patterns that emerges (power, level of expertise, gender, …).
    3. Transforming exchanges form the connections between system agents.
  • “Just as a person needs time and space to incubate thoughts before a new Idea can emerge, a system needs a bounded space for the emergence of new patterns.”

What is a Team Charter?

Project Charter vs. Team Charter

  • In classical project management often a project charter is used to define the project goal, scope, and the definition of success. Normally it is defined from upper management.
  • In scrum, it is typically covered by the product vision.

Ownership

  • The team writes, takes responsibility for, and owns its charter.
  • Scrum Master and Product Owner provide input.
  • For a particular organization, there might be mandatory entries, such as:
    • technology choices; and/or
    • governance compliancy requirements; and/or
    • CMMI requirements.

Basic Agreements

Meetings

  • Daily Scrum from 09:30, Malpitas Conference Room
  • Product Backlog Refining: every Tuesday, 10:00–12:00
  • Bi-weekly:
    • Sprint Review: Wednesday 14:00
    • Sprint Retrospective: Wednesday 16:00
    • Sprint Planning: Thursday 10:00
  • Royalty Points for being on time: 10
  • Three times late in same sprint? Bring a home made cake to Retrospective.

Planning & Estimation

  • User Stories in Story Points
  • Tasks in less than 1Ž4 day
  • Tasks no larger than 2 days
  • Planning Poker

Technology Rules

Engineering Rules

  • TDD
  • New Code:
    • Write JUnit before coding
    • Write code until test succeeds
    • Refactor code
  • Bug detected:
    • Write test to reproduce bug
    • Fix code
    • Refactor code
      • Acceptance test in Selenium and FitNesse

Team Norms & Communication Rules

  • Respectful communication
  • Active listening
  • Expectations of PO:
    • Present at ≥ 50% of Daily Scrums
    • Chance for interaction with team directly after
    • Feedback within one workday
    • Response to questions within one workday

Sprint

  • Ready
    • During each sprint
      • Requirement workshop
      • Estimation meeting
      • Time for research
  • Done
    • Task
      • Coded
      • Unit tested
      • Reviewed
      • Documented (Javadoc)
      • Check in in trunk
      • Integrated
      • …
    • Story
      • Acceptance criteria fulfilled (automated test)
      • User documentation updated
      • Integrated (automated tests run in Hudson)
      • Formally accepted by PO
      • …
    • Increment
      • All story tests passed
      • Installation scripts updated
      • Deployed in system integration environment
      • Release Notes updated
      • Regression tests passed

Creating a Team Charter

  • Dedicated workshop before the first sprint, facilitated brainstorm
  • Team decides
  • Integrate organizational needs
  • Multiple teams?

Anti Patterns

  • Dictated by management or Comes from coach
    • Team does not internalize the charter because they don't own it
    • “…organizing a self-organizing system is not only an oxymoron, it will very likely throw a spanner in the works.”—Harrison Owen, Wave Rider: **Leadership for High Performance in a Self-Organizaing World
  • Not enough time
  • Too detailed
  • “Simple, clear purpose…”—Dee Hock
  • “company culture, not rulez”, “Lead DoD”—team members during coaching

Benefits

  • Uncovers unclear expectations and ambiguous goals
  • Common understanding if work
  • Functional communication inside and outside the team
  • Helps forming the team
  • Defines a container so that self-organizing can emerge

Sources

Retrieved from "http://pearllanguage.org/index.php?title=Team_charter&oldid=311"