Christopher McSpiritt

Below is a high-level overview of the process that occur during a scrum project.

Sprint Planning Meeting

• Timeboxed at 4 hours
• eam negotiates with product owner over what to put in sprint
• Determine the sprint goal (specific, measurable, demonstrable)
  • E.g. make the application run on SQL server in addition to Oracle.
• Translate user stories into “how” a requirements is to be built
• Estimation
• Estimate in ideal days
• Play planning poker
  • Each team member gets a deck of playing cards
  • Put down the card for the number of days a user story would require in development time
  • If a user story takes too long, break it down into sub-stories
  • All team members show cards at same time
  • Discuss discrepancies to arrive at agreed upon duratio

Daily Scrum Meetings

• No more than 15 minutes in length
• Traditionally a stand-up meeting
• Not for problem solving
  • Whole world is invited
  • Only team members, Scrum Master, and product owner can talk
• Each team member answer 3 questions(signify commitment in front of team)
  • What did you do yesterday?
  • What are you going to do today?
  • What is in your way?

The Sprint Review

• Team presents what it accomplished during the sprint
  • Typically takes the form of a demo of new features or underlying architecture
  • Informal meeting
    • 2 hour prep time limit
    • No slides allowed
  • Whole team participates
  • Invite all stakeholders

Sprint retrospective

• Performed after every sprint
• Evaluate what is and is not working
  • Discuss what the team would like to:
    • Start doing
    • Stop doing
    • Continue doing
• Typically 15-30 minutes
• Whole team participates
  • Scrum Master
  • Product Owner
  • Team
  • Possibly stakeholders