1 of 17

Intro to Scrum

SDEV

Tina Ostrander

​

2 of 17

  • Scrum is an agile process that allows us to focus on delivering the highest value in the shortest time �
  • Scrum allows us to rapidly and repeatedly inspect actual working software�
  • The client sets the priorities�
  • Teams self-organize to determine the best way to deliver the highest priority features

Scrum in 100 words

3 of 17

The Players: Product Owner

  • Defines the features of the product, which are recorded in the product backlog
  • Prioritizes features
  • Adjusts features and priorities every iteration, as needed 
  • Accepts or reject works results

​

4 of 17

The Players: The Team

  • Cross-functional:
    • Programmers, testers, �designers, etc.
  • Teams are self-organizing
  • Work is never assigned
  • Roles may change and overlap

​

​

5 of 17

The Players: The Scrum Master

  • Responsible for enacting Scrum values
  • Removes impediments
  • Ensures that the team is fully functional and productive
  • Shields the team from unnecessary interference
  • A servant leader, NOT a micro-manager
  • For our purposes, the Scrum Master will rotate each sprint

6 of 17

Discuss

  • Who will be your Scrum Master for Sprint One?

7 of 17

The Team Stand Up�(Also called "The Daily Scrum")

  • These are not status updates for the Scrum Master
  • They are commitments in front of peers

What did you do yesterday?

1

What will you do today?

2

Is anything in your way?

3

8 of 17

Sprints

  • Scrum projects make progress in a series of “sprints”
  • Typical duration is 1–4 weeks
    • Our sprints will be two weeks
  • A constant duration leads to a better rhythm
  • Product is designed, coded, tested, debugged and documented during the sprint
  • The goal of each sprint is to produce a potentially shippable product that is DONE!

​

9 of 17

10 of 17

Product Backlog

​

  • The product requirements
  • Prioritized by the product owner
  • Reprioritized at the start of each sprint
  • Expressed as “user stories”

​

11 of 17

User Stories

  • A user story is a short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.
  • User stories communicate value.
  • User stories communicate WHO, WHAT, and WHY
  • User stories typically follow a simple template:

​

​

​

​

12 of 17

13 of 17

Sprint Planning

​

  • At the beginning of each sprint, the team selects the highest priority items from the Product Backlog into the Sprint Backlog

​

14 of 17

Sprint Review

​

  • Team presents what it accomplished during the sprint
  • Typically takes the form of an informal demo
  • Whole team participates
  • Elicit feedback
  • Welcome criticism

15 of 17

Retrospective

​

  • The whole team gathers and discusses what they’d like to continue to do, and what they'd like to change.

16 of 17

Increment

​

  • The goal is to produce a potentially shippable product at the end of each sprint.

17 of 17

A Scrum reading list

  • Agile and Iterative Development: A Manager’s Guide by Craig Larman
  • Agile Estimating and Planning by Mike Cohn
  • Agile Project Management with Scrum by Ken Schwaber
  • Agile Retrospectives by Esther Derby and Diana Larsen
  • Agile Software Development Ecosystems by Jim Highsmith
  • Agile Software Development with Scrum by Ken Schwaber & Mike Beedle
  • Scrum and The Enterprise by Ken Schwaber
  • Succeeding with Agile by Mike Cohn
  • User Stories Applied for Agile Software Development by Mike Cohn

​