Scrum Development Process

Added by Tsuy Ito, last edited by Tsuy Ito on Sep 19, 2009  (view change)

Roles

  • Customer
  • Product Owner
  • Scrum Master
  • Team

Pigs: Product Owner, Scrum Master and Team

Chicken: Customer

Process

0. Init

  1. The Customer and the Product Owner define the general requirements (due date, product, [INTERNALS:technology])
  2. The Product Owner writes user stories for the Product Backlog and prioritize the user stories
  3. The Product Owner and the Scrum Master group the Team.
  4. The Scrum Master schedules meeting
  5. The Product Owner and the Team define a persona (profile of the user who will use the software)
  6. The Team sets the infrastructure up

1. Planning and Estimation Meeting

  1. The Product Owner prioritizes the user stories in the Product Backlog and defines what should be done in the next Sprint (if necessary add new user stories to the product backlog)
  2. The Team discusses the user stories in the Product Backlog and estimates the effort for the high-prioritized user stories (best case and worst case estimation)
  3. The Team calculates Velocity and make suggestions about the team constellation for the next Sprint
  4. The Scrum Master and the Team assign the available resources for the next Sprint

2. Team Meeting

  1. Each (high-level) user story in the Sprint Backlog is discussed by the Team (create Sprint Backlog Entries: How to use jira (workflows))
  2. If necessary the Team defines Work Entries for the Sprint Backlog Entries
  3. If necessary the Team creates task forces (task group)
  4. The Team estimates the effort for each user story in the Sprint Backlog

Sprint Backlog Entries (SBE) are high level user stories/issues based. SBEs are decomposed into smaller issues called Work Entries (WEs). This does not exclude an SBE to be a WE if the SBE is small enough.

3. Retrospektive

  • The Goal of this meeting is to improve the Scrum development process
  • The Scrum Master and the Team make suggestions to improve the development process (Product Owner can join the meeting)

4. Sprint Meeting (the Customer can join the Sprint Meeting)

  1. One of the team members writes a protocol
  2. The Team gives an introduction (what was done, explaining decisions)
  3. The Team presents the work
  4. Feedback from Customer and Product Owner
  5. The Product Owner and the Team define the Sprint Backlog
  6. The Team commits what should be done in the next Sprint

5. Project Closeout

  • The Team presents the delivery
  • The Team, Product Owner and the Customer discuss improvements for further collaborations

Overview Sprint

Daily Standup
Each day during the sprint, a status report meeting occurs.

  • The meeting starts at 1:00 pm sharp
  • Punishments for tardiness have to be defined by the team
  • Only Pigs are allowed to speak
  • The meeting is timeboxed at 15 minutes
  • Questions, which should be answered
    • What have you done since yesterday?
    • What are you planning to do by tomorrow?
    • Do you have any problems preventing you from accomplishing your goal?

Notes:

  • 30 day period for a Sprint 
  • One day before the Sprint Meeting the Planning and Estimation Meeting takes place
  • In the last week of the Sprint the Retrospective takes place
  • Nobody works on issues (incl. tasks and new features), which are not defined in jira
  • During a Sprint the Sprint Backlog could not be changed
  • The Product Owner or Customer can abort the current Sprint

Labels

 
(None)