An overview of SCRUM Events

An overview of SCRUM Events

Scrum meetings happen at particular points in the sprint cycle. To simplify our Scrum processes we have outlined the major events as below.

Daily Scrum (Stand-up)

Participants:

• Scrum Master (optionally)
• Dev Team

Meeting run by:

• Scrum Master or Dev Team Leader

Time: 15m Daily

Questions to ask

• What did I do in the last 24h that helped the development team meet the sprint goal?
• What will I do in the next 24h that will help the development team meet the sprint goal?
• Do I see an obstacle that prevents me or the development team from meeting the sprint goal?

Sprint Retrospective

Participants:

• Scrum Master
• Dev Team

Meeting run by:

• Scrum Master

Time: 15m at the end of each sprint

Meeting Agenda

• What are the things we should start doing?
• What are the things we should stop doing?
• What are the things we should continue doing?

More Info

Sprint Review

Participants:

• Scrum Team (SM, PO, Dev Team)
• Stakeholders (CEO, Product Manager if invited)

Meeting run by:

• Product Owner and/or Scrum Master

Time: 1-4h at the end of each sprint

Purpose: A Sprint Review (Demo) provides the platform for the Scrum Team to showcase what they accomplished during the sprint while creating the opportunity for key stakeholders to inspect the increment and adapt the Product Backlog, if necessary.

Meeting Agenda

• Welcome everyone and introduce new people if needed (5m)
• Remind the team of the sprint goal and state what will (and will not) be demonstrated (10m)
• Demonstrate features using screen sharing feature (20m-2h)
  • Create new backlog items if changes are required, new ideas come up or bugs are identified
• Discuss key events and problems faced (20-40m)
• Present upcoming product backlog items and gather feedback from stakeholders (20-40m)
• End meeting (1m)

More Info

Sprint Planning

Participants:

• Scrum Master
• Product Owner
• Dev Team

Sprint Duration: 4 weeks

Meeting Duration: 1h – 4h

Meeting Agenda:

• Close last sprint (5-10m)
  • Acknowledge what was achieved in last sprint
  • Decide what to do with unfinished items
• Clarify team availability (5-10m)
  • Is someone going on holiday
  • Are there public holidays?
  • How much time are you spending on tasks outside sprint?
• Go through backlog items for next sprint one by one (1-3h)
  • Assign Tasks to each developer and give them time to investigate and ask questions
  • Task Description is updated if clarification is needed and developers suggest solutions
  • The How-To of the task is updated based on suggested solutions and developers estimate time for completion
  • Optionally create Sub-tasks, based on time estimation. Sub-tasks also have their own Description and How-To
• Can we pull more work into the sprint? (30m)
• Start Next Sprint

More Info