Scrum

Scrum Overview

  • Roles: Scrum Master, Product Owner, Developers

  • Artifacts: product backlog, sprint backlog

  • Activity: setup, sprints

  • Overview:

    • Initially: User stories and scenarios developed, features selected, product backlog created

    • Repeatedly:

      • Sprint planning meeting: select spring backlog

      • Dev sprint: daily standups

      • Review meeting

      • Retrospective meeting

Sprints

  • A sprint is a fixed period for a given project — usually in the 1—4 week range, 2 is probably ideal ("timeboxing")

  • Each sprint should produce a production-ready chunk of code

  • Meetings at start and end

  • Standups at start of each day

  • Direct team communication face-to-face (or via Internet)

Product Backlog

  • Items (PBIs) corresponding to small units of work

  • Every task should be explicit in backlog

  • Dynamic refinement (work breakdown)

Backlog Review

  • During sprint planning meeting

  • Item states: Ready for consideration, ready for refinement, ready for implementation, done

  • Check / change statuses, move things to sprint backlog

  • "Refinement, estimation, creation, prioritization"

  • Estimate effort in person-hours or made-up "story points"

  • In retro meeting — estimate "velocity" as effort / sprint

Team Dynamics

  • Scrum Master — facilitates team self-org, interface w/ management

  • Product Owner — customer / marketing proxy

  • Scrum / Kanban board used to post and distribute sprint backlog items

Last modified: Monday, 5 October 2020, 12:42 AM