V_ Introduction to Scrum - 7 Minutes

Notes:

• Scrum

  1. just enough planning to get minimal feature set
     • Build what was planned
     • Test/review and get ready to ship
     • creates potentially shippable product
  2. process repeated every 1 to 3 weeks
     • doing just enough planning to do an incremental release
  3. Incremental releases are called "Sprints"
     • keep doing sprints until product is feature complete

• 3 Key Roles

  1. Product owner
     • defines the features needed for the product
     • has the bright ideas
  2. Scrummaster
     • servant leader to team
     • protecting the team and process
     • running the meetings
     • keeping things going
  3. Development team
     • developers, testers, writers
     • responsible for building the product

• Artifacts

  1. Product Backlog
     • product owner create prioritized list of features
       • also called Stories
     • list envolves and changes priority with every sprint
     • User Stories
       • describes a feature set
         • As a _ I need _ So that _
  2. Sprint Backlog
     • highest priority user story goes into Sprint Backlog
     • estimated for size
     • commited to for the next sprint
  3. Burndown Chart
     • show progress durring a sprint on completion of tasks
     • chart should approach 0 points as work is being completed

• 3 Ceremonies

  1. Sprint Planning
     • where product owner, scrummaster, and team meet to discuss user stories and sizes
  2. Daily Scrum
     • discuss what that have completed since the previous meeting
     • what they are working on
     • anything that might be blocked or need help
  3. Sprint Review/Retrospective
     • happens at end of sprint
     • team demostrates completed product to product owner
     • team discusses what they can do to improve the process going forward

• All Together

  • Product Backlog
    • Product owner creates a list of all the ideas that could go into a product
    • Product owner prioritizes the list & brings top items to the team
  • Sprint Planning
    • Product owner and team discuss top priority user stories
    • determine what can go into the next sprint
  • Sprint Backlog
    • output of Sprint Planning
    • list of user stories commited for the next sprint
  • Sprint
    • 1 to 3 week time box
    • work done to completion
    • durring Sprint Daily Srum occurs
      • what team has completed and what they are working on & blocked items
  • Potentially shippable product
    • Product owner determines if it is ready to ship or needs additional features
  • Sprint Review and Sprint Retrospective Meeting
    • Sprint Review showcases product to product owner
    • Retrospective is meeting on how to improve their process
  • Repeat workflow for each Sprint