Development Team

A self-organizing, cross-functional team with 2-8 members (architects/developers/testers). In a Sprint the team stays fix, changes can happen with the next Sprint.

Goal (what)

Achieve the Sprints goal and create a valueable, deliverable increment / iteration of a product at the end of every Sprint

 

Main tasks (how)

  1. Estimate effort of user stories (helping the product owner to priotitize the product backlog)
  2. Estimate capacity for a sprint (think of free days, sick days, delays due to late approval, delays due to urgent issues, QA)
  3. Define tasks for each user story
  4. Program (accomplish the different stories of the sprint backlog)
  5. Testing

Artifacts responsible for

Events / ceremonies / activities to attend

by S. Pietsch

Scrum Master

Definition & Goal (what)

The SCRUM Master is responsible for the SCRUM process. He ensures that SCRUM is correctly and efficient used.

Goal:

Ensure the SCRUM methology is used effectively and the team performs at its best

 

Main tasks (how)

  1. Chair & facilitate meetings
  2. Update burn down chart / burn up chart
  3. Communicate SCRUM methology
  4. Remove impediments / road blocks
  5. Coaches the team to its best performance
  6. Ensures close cooperation across the team
  7. Shield the team from external interference

 

Artifacts responsible for

 

Events / ceremonies / activities to attend

 

Details

The Scrum Master is responsible for a working SCRUM process. He works with the Developement Team but is not part of it. He introduces the rules of SCRUM and takes road blocks out of the Development Teams way. He takes care of good and enough communication and cooperation within the Development Team of between the team and the Product Owner.

A Scrum Master is a servant leader. He does not do “command and control”. A SCRUM Master does not judge anyone. He is coaching and educating every member of the SCRUM team in doing SCRUM right and removes impediments.

If a company switches its processes to SCRUM the SCRUM Master will change all processes, procedures and educates everyone in doing SCRUM. A SCRUM Master is a change manager introducing SCRUM in the whole company and is an advocate for the acceptance of SCRUM.

by S. Pietsch

Product Owner

Definition (what)

The Product Owner represents the customer/stakeholders for the product which we are developing.

Goal (what)

Ensure maximum value for the product

 

Main tasks (how)

  1. Create a product vision
  2. Identify and prioritize requirements after talking to executives, stakeholders, team, customers and users
  3. Write User Stories based on these requirements
  4. Describe the scope of a requirement
  5. Defines User Stories for the next sprint in detail (inkl. Acceptance Criteria) – the stories must be easy to understand for everyone
  6. (re-)rioritize the stories
  7. At the end of each Sprint (in the sprint review) the Product Owner (PO) explains which stories are “done” and which not and why – He accepts or rejects work results
  8. Optional: Cancel the current sprint if the goal of the sprint is obsolete now

Artifacts responsible for

 

Events / ceremonies / activities to attend

Details

The Product Owner is responsible for the economic success of the product. He strives to maximize the products benefits (USPs / Unique Selling Points). The PO creates, prioritizes and clarifies the requirements (features) for the product and at the end of each Sprint he judges which User Stories are complete.

He needs to find a balance between requirements, time of delivery and costs.

The Product Owner confers frequently with other stakeholders (e.g. customers, users, management) to understand their needs. It is a challenge to find a balance between all those needs, which may compete with each other.

by S. Pietsch