Scrum is a proven development methodology to quickly respond to vision changes. It is the defacto development methodology for software companies.
Scrum is now spreading beyond IT to other fields. It’s essential to adopt Scrum when everything is changing so fast.
In this Crash Course, you will learn the basics of Scrum and involve in exercises to bring them into practice. You'll also work on improvements for your team and learn how to apply scrum in remote or distributed teams. You'll learn the materials you need to start your assessments for the professional scrum master certification.
• Scrum masters
• Product Owners
• Project managers
• Business stakeholders
A. Scrum fundamentals
• Learning backlog: prioritized overview of learning goals of participants
• Scrum Theory:
• Scrum overview
• Scrum versus waterfall
• Agile Manifesto
• Scrum Roles, Events, and Artifacts
• Additional concepts : Velocity, burndown/up chart, estimates
The goal is to get everyone on the same level of knowledge about scrum. We'll start the day with an interactive scrum game in which teams create a learning backlog. This backlog is prioritized by a product owner. This will be our vehicle throughout the training. We will go through all the concepts in interactive breakouts. You'll learn from both the trainer and the other participants, share what you know and work on visuals and action plans to ingrain the learning goals.
B. Practice Scrum
Lego city simulation : practice scrum concepts
We will build a city of lego using the concepts we learned in the morning. Building something with lego is a neutral way to practice scrum applicable to both software development and other fields. We will split up in teams. The product owner (the trainer) has created a prioritized product backlog. During pre-planning teams can clarify requirements and we'll use planning poker and swimlanes to make estimates. The game itself consists of 3 iterations (5 minutes planning, 7 minutes sprints and 5 minutes retrospective). The end goal is a city of lego (all teams work on the same product).
C. Retrospective day 1
We close the day with a group retrospective. People can indicate what they learned / loved / lacked / longed for, so we can make the experience even better on day 2.
A. Scrum guide study
We will work in teams to create a presentation about the scrum guide. Everyone gets a printout and reads the whole guide. Then within the team you discuss what you found in the guide that you :
1. can apply right away in your team
2. recognized as an improvement for your team
3. didn't know before or missed out on day 1
Each team creates a visual board and presents it to the other groups.
B. Design your own scrum
recap and visualization of the scrum framework
In teams, we will build an overview of the scrum framework and flow. By cutting and pasting icons that are provided, each team will capture and summarize their views on scrum. Each group will present.
C. Applying agile in your organization
what does that mean for us ?
In this exercise, we will study the agile manifesto and principles in groups. Each group will create an overview of how their company already works according to the principles and where they need improvement. Each team will also create an action plan and presentation.
D. Test exam : test the basic knowledge of scrum
All participants will go through a test exam. Using the questions, you will deepen your knowledge, play with the materials and you also get prepared for a possible certification assessment.
E. Case study
Those who don't want to prepare for the exam, will work in groups to find case studies (online / in the room). The groups will create a presentation and share with the others.
F. Applying Scrum : design how the organization and team can apply scrum
We gather in teams. If you came with your full team, that's the case you will work on. If the team has members from different companies, 1 real team situation will be chosen. The teams create a visual map of how scrum will be applied to a real project. Your team discusses how each of the elements is applied within the team. You work out who gets what role, what events are planned, when and attended by whom. We also create an action plan for the implementation of this scrum setup. The goal is to have a tangible plan of implementation which can be started upon returning to office.
G. Learning breakout : discussion in groups about questions from the backlog
In the last part of day 2, we break out into different teams. Each team takes some of the user stories from the learning backlog created in the morning. Teams discuss the user stories and present their conclusions to the rest of the group.
Wrap up of the training. We'll discuss any remaining issues and discuss how everyone can make actions from what they've learned.