Skip to content

Project Setup

In this project the framework scrum is applied. This document contains the way Scrum is implemented for this project.

Events

Based on the way the project is handled in this module, only all meaningful Scrum ceremonies are held. This includes the following:

Sprint Planning

  • Attendees: Scrum Team, Project Coach
  • Goal: Initiates the Sprint by laying out the work to be performed for the Sprint.
  • When: Every two weeks
  • Procedure: Together with the PO, who represents the customers interests, a Sprint goal is defined. For this purpose, tickets are moved from the Product Backlog to the current sprint.
  • Outcome: Sprint Backlog

Sprint Review

  • Attendees: Scrum Team, Project Coach
  • Goal: Inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
  • When: Every two weeks
  • Procedure: The Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment.

Sprint Retrospective

  • Attendees: Scrum Team
  • Goal: Plan ways to increase quality and effectiveness.
  • When: Every two weeks
  • Procedure: The Scrum Team inspects how the last Sprint went in regard to individuals, interactions, processes, tools, and their Definition of Done. Discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.

"Daily" Scrum

  • Attendees: Scrum Team
  • Goal: Discuss stories that are being worked on. Help each other out when needed.
  • When: When need arises. Around two times per week.
  • Procedure: Each team member shortly explains on what they were and are working on. Asking for help and pairing up. General infos from PO / ScM at the end.

Bi-Weekly

  • Attendees: Scrum Team, Project Coach
  • When: Every two weeks (Shifted one week)
  • Goal: Discuss the progress of the running Sprint.
  • Procedure: Show the Project Coach what is being worked on and clarify questions if they arise.

Backlog Refinement

  • Attendees: PO, Project Coach/Customer
  • When: When the Backlog needs to be refined
  • Goal: Discuss future Epics and User Steps. Prioritise the work.
  • Procedure: Extend and add more cards on StoriesOnBoard in accordance to the Customers wishes.
  • Outcome: Epics/User Steps that are Backlog Ready and can be planned in a sprint.

Team & Roles

Role Project Member(s)
Product Owner (PO) Bigler Andy
Scrum Master Fuhrer Jan
Developers Bigler Andy, Fuhrer Jan, Lauber Jan
Customer/ Project Coach Mowers Anthony Alexander

Artefacts

Product Backlog

The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.

Sprint Backlog

The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).

Impediment Backlog

The impediment backlog is kept in the following document: Impediment Backlog