Small things that make your Scrum smarter

Work in progress by Andre Ullmann

Daily Scrum

  • All events are timeboxed. therefore it is important to be right on time or a minute before the daily starts. If all have the same mindset what timeboxed ment all team members have enough time to communicate in that meeting about their work.
  • Must have - Development and Scrum Master
  • Can have - silent Product Owner
  • Max 15 Minuten

Refinement Meeting

  • Pre-Planning for the next Sprint or up to 3 Sprint.
  • PO introduced the Stories and bugs the Dev. team have to resolve
  • Dev. Team is doing the estimation in front of the Sprint Planning 1

Sprint Planning 1

  • The PO announced the Sprint Goal
  • Backlog needs to be prioritized in front of the meeting by PO
  • PO structured connected User Stories and connect those in Jira
  • Must have - Po, SM and Dev.

Sprint Planning 2

  • Dev team is doing the final estimation
  • Dev team is creating tasks that makes the work transparent
  • Dev team validates the User Stories and if all Dev have a common understanding of the Sprint Goal
  • Must have - Scrum Master and Dev Team

Sprint Review

  • Scrum Master has to present the Sprint Goal and the achievement
  • Dev team has to present the solution to the PO (User Stories)
  • Dev team has to inform the PO about resolved bugs (only info)
  • Must have - Dev. Team, Scrum Master, PO

Sprint Retrospective

  • Dev team has to discuss the impediments and has to find a solution
  • Scrum Master can support if needed.
  • Scrum Master is going to moderate the meeting
  • Must have - Dev. Team, Scrum Master, PO
  • Can have - PO

Backlog

  • EPIC
  • Big stories or multiple user stories that are very closely related are summarized as epics. A common explanation of epics is also: a user story that is too big for a sprint.
  • Feature Story
  • A feature is a distinct element of functionality which can provide capabilities to the business.
  • User Story
  • A story is a small aspect of a feature which you can use to get feedback from your stakeholders and find out if you're doing anything wrong.

Sprint Backlog

  • This is comparable to a backlog but only contains the prioritized user stories for the next sprint period.
  • The Dev team can select the amount of user stories they can resolve in a sprint period
  • Only Devs can decide what the are able to do.
Previous

Unterschied zwischen einer Arbeitsgruppe und einem Team

Next

Rollen im Scrum – Das Team