An agile approach characterized by

• small teams with a few distinct but clearly defined roles
• Development cycles through sprints of 7-30 days
  • Planning meeting at beginning
  • Daily scrum meeting (< 15 min.)
  • Sprint Review meeting at end to review work completed (or not)
  • Sprint Retrospective meeting at end to discuss process

Scrum in Context

As the name suggests, Scrum

• focuses a bit more on the team than on the tools
• envisions a kind of controlled chaos

1 Values

• Transparency

  • Process must be visible to those responsible for the outcome
  • Common standards contribute to understandability

• Inspection

  • Scrum participants inspect one anothers’ work

• Adaptation

  • Inspections lead to adjustment of process (not products)

2 Practices

2.1 Scrum Teams

2 Practices

2.1 Scrum Teams

• Product owner

2 Practices

2.1 Scrum Teams

• Product owner

  • representative or agent of stakeholders

2 Practices

2.1 Scrum Teams

• Product owner

  • representative or agent of stakeholders
  • manages the project backlog (list of unimplemented work)

2 Practices

2.1 Scrum Teams

• Product owner

  • representative or agent of stakeholders
  • manages the project backlog (list of unimplemented work)

• Scrum master

2 Practices

2.1 Scrum Teams

• Product owner

  • representative or agent of stakeholders
  • manages the project backlog (list of unimplemented work)

• Scrum master

  • interface between project owner and development team

2 Practices

2.1 Scrum Teams

• Product owner

  • representative or agent of stakeholders
  • manages the project backlog (list of unimplemented work)

• Scrum master

  • interface between project owner and development team
  • aids project owner in arranging backlog

2 Practices

2.1 Scrum Teams

• Product owner

  • representative or agent of stakeholders
  • manages the project backlog (list of unimplemented work)

• Scrum master

  • interface between project owner and development team
  • aids project owner in arranging backlog
  • ensures that development team adheres to Scrum practices

2 Practices

2.1 Scrum Teams

• Product owner

  • representative or agent of stakeholders
  • manages the project backlog (list of unimplemented work)

• Scrum master

  • interface between project owner and development team
  • aids project owner in arranging backlog
  • ensures that development team adheres to Scrum practices
  • removes impediments to team’s progress

2 Practices

2.1 Scrum Teams

• Product owner

  • representative or agent of stakeholders
  • manages the project backlog (list of unimplemented work)

• Scrum master

  • interface between project owner and development team
  • aids project owner in arranging backlog
  • ensures that development team adheres to Scrum practices
  • removes impediments to team’s progress
  • “facilitates” Scrum events

2 Practices

2.1 Scrum Teams

• Product owner

  • representative or agent of stakeholders
  • manages the project backlog (list of unimplemented work)

• Scrum master

  • interface between project owner and development team
  • aids project owner in arranging backlog
  • ensures that development team adheres to Scrum practices
  • removes impediments to team’s progress
  • “facilitates” Scrum events

• Development team

2 Practices

2.1 Scrum Teams

• Product owner

  • representative or agent of stakeholders
  • manages the project backlog (list of unimplemented work)

• Scrum master

  • interface between project owner and development team
  • aids project owner in arranging backlog
  • ensures that development team adheres to Scrum practices
  • removes impediments to team’s progress
  • “facilitates” Scrum events

• Development team

  • 3–9 members

2 Practices

2.1 Scrum Teams

• Product owner

  • representative or agent of stakeholders
  • manages the project backlog (list of unimplemented work)

• Scrum master

  • interface between project owner and development team
  • aids project owner in arranging backlog
  • ensures that development team adheres to Scrum practices
  • removes impediments to team’s progress
  • “facilitates” Scrum events

• Development team

  • 3–9 members
  • must span required skill set

2 Practices

2.3 Backlogs