Scrum Roles

Product Owner

A single individual responsible for the project and the overall quality/success of the project. They manage the Product Backlog, manages expectations of the project and has the final word on which tasks are "done" during sprint review meetings.

Scrum Development Team

The team which is responsible for the actual development of the project. Generally team size will be from 5-10 people and all of which will have their specialities, however as a whole will contain all of the expertise that would generally be found in several departments.

Scrum Master

The Scrum Master facilitates the Scrum, they are responsible for keeping the process current, shields the team from external distractions and manages the process quality of the teams output. While the scrum master is responsible for these items along with many more, the scrum master is not senior to the team and the team does not report to the Scrum Master, they are simply there to ensure the scrum runs effectively. They do not have authority to make business, technical or resource decisions as they may cloud that true role of Scrum master.

Flow of a Sprint

Scrum Flow

The flow of a scrum is as follows

  1. Sprint Planning Meeting
  2. Daily Scrum
  3. Sprint Review Meeting
  4. Sprint Retrospective Meeting
  5. Backlog Refinement Meeting
The above is some what iterative and keeps looping until the entire project is complete.

Sprint Planning Meeting

Previous to starting the Sprint Planning Meeting, the Product Owner will have worked on producing a Product Backlog (see lingo). The planning meeting should generally be one full day split in two.
  • The first half has the development team concentrating solely on the product backlog and deciding on the tasks and committing to completing those tasks. The Product Backlog will be discussed through out the sprint.
  • The second half includes the development team and the Product Owner. The team decide how to build and also decide on tasks based on the Product Backlog and allocate the tasks to a Sprint Backlog (see lingo)

Daily Scrum

This is a short (max 15 min) meeting which occurs every day of the sprint. It should
generally be held where development takes place and all member should stand as to ensure it's quick. The main aim is to have each member answer 3 basic questions
  1. "What have I done since the last scrum"
  2. "What will I do before the next scrum"
  3. "What issues are stopping my progress"
The Scrum Master is responsible for ensuring the meeting sticks to these items, and if something needs to be discussed more then that happens after the meeting.

Sprint Review Meeting

The team show all "done" tasks to the Product Owner. Feed back will be given from the Product Owner and they may decide to re-prioritize on-coming sprints. The Scrum master schedules the next Sprint Review Meeting.

Sprint Retrospective Meeting

This is a formal meeting including the full team, including the Scrum Master, although the Project Owner is optional. The aim of the meeting is to talking through what went well and what didn't go well. The scrum Master is there to push the questions, however not there to provide the answers.

Backlog Refinement Meeting

During this meeting the Project Owner has the opportunity to re organise the Product Backlog based on customer needs. This impact is then discussed.

Agile Lingo

Sprint Backlog
To-Do list for the sprint.
Defined by the full team.
Product Owner order's tasks priority.
    Product Backlog:
    List of desired product features/bugs/issues.
    Owned and organized by the Product Owner.
    Items can be added by any one/any time.
      Time Box:
      The amount of time task should take.
      People who are not committed and not responsible to the project.
      People who will be accountable for the success of the project.