Scrum

Michael L. Collard, Ph.D.

Department of Computer Science, The University of Akron

Scrum

  • Iterative agile software development framework
  • Holistic: one team performs multiple functions across overlapping phases
    • Note: This doesn’t mean that developers don’t specialize in technology, e.g., database, UI, etc.

Scrum: Roles

  • Product Owner - business owner, voice of the customer
  • Development Team - self-organizing team of 3 - 9 members
  • Scrum Master - ensures that the scrum process is followed, but not the team leader

Scrum: Sprint

  • Scrum unit of development
  • Fixed duration of 1 week to 1 month
  • Always ends on time, but which features are completed may change
  • timebox fixed amount of time allocated, and when done the activity is finished

Scrum: Backlog

  • set of requirements in user story format
  • product backlog list of requirements ordered by business values and needs
  • sprint backlog list of work the development team will attempt in the next sprint
  • Sprint begins with selecting sprint backlog from the product backlog

Scrum: Sprint Planning Meeting

  • At the start of a sprint
  • Select what work is to be done
  • Put together the sprint backlog
  • These meetings:
    • Entire team works on prioritizing the product backlog (4 hours)
    • Development team creates a plan for the sprint (4 hours)

Scrum: Story Time

  • Estimation for backlog using planning poker or other methods
  • These meetings:
    • Should not be longer than an hour
    • Does not include breaking stories into tasks
    • Team decides number of meetings per week

Scrum: Daily Scrum Meeting

  • Everyone on the development team has an update
  • Same location and time everyday, limited to 15 minutes
  • Meeting always starts on time, even if some are missing
  • Convenient location so people can get started right away on work

Scrum: Daily Scrum Meeting Questions

  • What have you done since yesterday?
  • What are you planning to do today?
  • What obstacles are in your way?

Scrum: Burn Down Chart

  • Remaining work in the sprint backlog
  • Typically readable by all members (not just development team)

Scrum: Documents/Artifacts

  • product backlog - ordered list of requirements, typically in a user story format: title, description, estimate, priority
  • sprint backlog - requirements to be implemented in a sprint
  • increment - all the product backlog completed during a sprint
  • burn-down chart - status of work on sprint backlog

Scrum: Sprint Review Meeting

  • Review what was done, and left undone, during the sprint
  • Demo the completed work
  • 4 hour time limit

Scrum: Sprint Retrospective

  • What went well?
  • What could be improved?
  • Entire team reflects on the past sprint
  • Time for making continuous process improvements
  • 3 hour time limit