Register
Energiser
Every session begins with an energiser. Usually there’s a rota showing who will lead the energiser. We have some favourite games you can play if you are stuck.
- Traffic Jam: re-order the cars to unblock yourself
- Telephone: draw the words and write the pictures
- Popcorn show and tell: popcorn around the room and show one nearby object or something in your pocket or bag and explain what it means to you.
Morning orientation
Learning Objectives
Planning during the week
👣 Steps
If you haven’t done so already, choose someone (volunteer or trainee) to be the facilitator for this morning orientation block. Choose another to be the timekeeper.
🎙️ The Facilitator will:
- Assemble the entire group (all volunteers & all trainees) in a circle
- Briefly welcome everyone with an announcement, like this:
💬 “Morning everyone, Welcome to CYF {REGION}, this week we are working on {MODULE} {SPRINT} and we’re currently working on {SUMMARISE THE TOPICS OF THE WEEK}”
- Ask any newcomers to introduce themselves to the group, and welcome them.
- Now check: is it the start of a new module? Is it sprint 1? If so, read out the success criteria for the new module.
- Next go through the morning day plan only (typically on the curriculum website) - and check the following things:
Facilitator Checklist
- Check the number of volunteers you have for the morning
- Check someone is leading each session
- Describe how any new activities works for the group
- Decide how best to allocate trainees and volunteers for a given block - most blocks will make this clear
⏰ The Timekeeper will:
- Announce the start of an activity and how long it will take (check everyone is listening)
- Manage any whole class timers that are used in an activity
- Give people a 10-minute wrap-up warning before the end of an activity
- Announce the end of an activity and what happens next
Teamwork Project Sprint 3
Learning Objectives
Preparation
Post-its and a collaborative board.
Introduction
When mapping a product, we go from the high to the lowest level to plan our delivery. The reason for that is so that the team and stakeholders all have the same knowledge of the strategy of the product and the main end goal.
However, we cannot deliver everything at once. And we also cannot plan every detail. We can prioritise the must-haves and then focus on them.
This process is often called User Journey Mapping or Story Mapping. Because we cannot deliver everything at once, we must prioritize must-have features first.What questions should we ask to identify what was built?
🎯 Goal: To understand the requirements of building a library(5 minutes)
Let’s assume we have been asked to build a library website that allows you to borrow books.
Instructions
Discuss briefly as a class what questions we should ask to understand better what we will build.
Write these questions on post-its and share them on the collaborative board.
Focus is on the questions, not the answers!
🎯 Goal: Learn how to break down a broad product into specific features (10 minutes)
Scenario: Assume we have answers to our product questions. Our goal is to build a website with a catalogue of books that can be borrowed online.
Instructions
In small groups, identify the main features you would expect on this website.
Examples: book search, shopping cart, user accounts.
One person from each group shares the group’s thoughts with the class.
⏱️ Time: 15 minutes
🎯 Goal: Break features into actionable, user-centric stories
Instructions
In small groups, pick one feature from your previous list.
Break it down into at least 2 user stories using the standard format:
“As a [user], I want to [action] so that [value].”
Example (Shopping Cart):
“As a library user, I want to remove items from my cart so that my final checkout is correct.”
“As a library user, I want to pay with a credit card so my books can be delivered.”
Group representatives volunteer to share their stories with the class.
⏱️ Time: 15 minutes
🎯 Goal: Understand technical tasks and dependencies
Instructions
In your groups, choose one user story from Exercise 3.
Identify the tasks needed to deliver that outcome (e.g., “Create database table,” “Build UI search bar”).
Map dependencies:
How does Task A affect other tasks?
Does Task A need to be completed before Task B can start?
Size the tasks based on complexity.
Discuss: When is the right time to assign tasks? What criteria should you follow?
Community Lunch
Every Saturday we cook and eat together. We share our food and our stories. We learn about each other and the world. We build community.
This is everyone’s responsibility, so help with what is needed to make this happen, for example, organising the food, setting up the table, washing up, tidying up, etc. You can do something different every week. You don’t need to be constantly responsible for the same task.
Study Group
Learning Objectives
Trainees
This is time for you to get help with whatever you need help with.
If you didn’t understand something in the prep, ask about it.
If you were struggling with a backlog exercise, get help with it.
If you weren’t quite sure of something in a workshop, discuss it.
If you don’t have any problems, keep working through the backlog until you need help.
It can be useful to get into groups with others facing the same problem, or working on the same backlog item.
Volunteers
Don’t be scared to approach people and ask what they’re working on - see if you can help them out, or stretch their understanding.
If lots of people have the same problems, maybe you can put together a demonstration or a workshop to help them understand.
If absolutely no one needs help, consider reviewing some PRs using the process and guidelines in the #cyf-code-review-team Slack channel canvas.
Breaks
No one can work solidly forever! Make sure to take breaks when you need.
Retro: Start / Stop / Continue
🕹️Retro (20 minutes)
A retro is a chance to reflect. You can do this on RetroTool (create a free anonymous retro and share the link with the class) or on sticky notes on a wall.
- Set a timer for 5 minutes. There’s one on the RetroTool too.
- Write down as many things as you can think of that you’d like to start, stop, and continue doing next sprint.
- Write one point per note and keep it short.
- When the timer goes off, one person should set a timer for 1 minute and group the notes into themes.
- Next, set a timer for 2 minutes and all vote on the most important themes by adding a dot or a +1 to the note.
- Finally, set a timer for 8 minutes and all discuss the top three themes.