Skip to content
To start the training, we will explain the basis of Agile and the Agile Manifesto. We will discuss the differences between Agile and Waterfall.
In an interactive exercise rich session, we will go through the 3 roles in Scrum:
- Scrum Master: The coach/facilitator in scrum
- Product Owner: The leader of the product, empowered by stakeholders to build a valuable product
- Development team: Cross functional, self organized team with developers, testers, designers, etc.
We will explain in detail what the three main artifacts in scrum are about and what information they contain:
- Product Backlog: a prioritized list of user stories, depicting what needs to be built
- Sprint Backlog: Owned by the scrum team, shows what the team committed to finished in the sprint
- Increment: The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.
The scrum events or ceremonies are the (physical) meetings the team does. There is an order and time-box to every event. The events (in chronological order) are:
- Sprint planning: a collaborative effort involving a Scrum Master, who facilitates the meeting, a Product Owner, who clarifies the details of the product backlog items and their respective acceptance criteria, and the Entire Agile Team, who define the work and effort necessary to meet their sprint commitment.
- Daily Stand up: In Scrum, on each day of a sprint, the team holds a daily scrum meeting called the “daily scrum.”Meetings are typically held in the same location and at the same time each day. Ideally, a daily scrum meeting is held in the morning, as it helps set the context for the coming day’s work.
- Sprint: No changes come in that would affect the end goal and that would upset the team rhythm. Sprint goal does not change. So does quality standard. Sprint scope can be re-negotiated between the Product Owner and the rest of the team. Only the product owner has the right to cancel a sprint.
- Sprint Review: At the end of each sprint, a sprint review meeting is held. During this meeting, the Scrum team shows what they accomplished during the sprint. Typically this takes the form of a demo of the new features.
- Sprint Retrospective: The sprint retrospective is usually the last thing done in a sprint. Usually the teams will do it immediately after the sprint review. The entire team, including both the Scrum Master and the product owner should participate. You can schedule a scrum retrospective for up to an hour, which is usually quite sufficient.
We will go through some additional concepts that are often used in scrum teams:
- Estimation: we will explain how planning poker, swim-lanes and other estimation techniques work.
- Fixed price versus waterfall: how to use scope to make iterative work work.
- Velocity: the prime measure of productivity in scrum: how many story points can the team ‘burn down’ during a sprint
- Burn down chart: a graph showing the amount of work burnt down versus the planned amount of work in the sprint (or release).
- Release planning: how do we plan a project from beginning to end in scrum, answering the question ‘when will this be finished’?
scrum applied to your team
In this exercise, you will design the scrum flow for your own team. Using a real product, project or team, you will think through the roles, events and artifacts. You will assign names to the roles. You wil plan days/times for the events. And you may even develop your initial product backlog.
Agile principles applied
In your team, you will study and discuss the agile principles underlying the agile manifesto. Together, you will discuss what princinples you are already ‘living’ in your company (or team). You will also identify the principles you are ‘not living yet’. This gives a good idea of what to change in order to implement the agile principles in your organization.
In this simulation, we will build a city or zoo. The product owner is the trainer. He has a backlog with user stories, based on the requirements from the investors. The group will split up into teams of 4-5 people. We simulate the whole scrum cycle, doing 3 sprints. In those 3 sprints, the teams need to deliver the ‘zoo’ or ‘city’ as agreed with the product owner. This simulation is used to demonstrate ‘scrum in action’. It teach people how to be self-organized, how to work in short sprint cycles, how to do retrospectives, how to do backlog grooming, estimation, release planning, creating a burn down chart.
We will do a final learning breakout to address any remaining questions. At the beginning of the training, we have created a learning backlog, listing all questions from participants. In this final session, we will go through all of them to ensure everybody goes back to work ‘prepared for scrum’.