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.

1. Traffic Jam: re-order the cars to unblock yourself
2. Telephone: draw the words and write the pictures
3. 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.

👣 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.

• Share solutions to exercises → share code, talk through what you’ve done to the group, ask questions and discuss alternative solutions / tradeoffs etc
• Discuss reflections for each exercise (these are listed under Reflections sections in Prep) → there is no right or wrong answers here, this is a chance to consolidate what you’ve learnt and analyse / challenge the various patterns and principles covered in this sprint.
• Please write your answers to the reflection questions as you are completing the corresponding exercises - don’t wait until the last minute before class!

Come prepared to discuss:

• What is automated testing? what types of automated test are there and how do they differ?
• What JUnit is for? What is a suite? When would you use a parameterised test?
• What are annotations, what annotations are used by JUnit? What are their purpose?
• On what program elements will we find javadoc?
• Why would we use javadoc from an external framework or library?

Every Saturday, we 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 let’s work together. These are the roles we need help with.

• Food shopping: ensure enough food is available for all courses running in your region, respecting the dietary requirements and the budget (you might not be the one buying the food, but you should ensure whoever buys or cooks the food knows what should be bought)
• Setting up the table: organise the food so that everyone has access to it and invite people to join lunch
• Washing up & tidying: your location should be as clean as it was before you all arrived in the morning. This can include washing up, taking the litter outside, hoovering, etc.

You can do something different every week or every two weeks. You shouldn’t have to be constantly responsible for the same task. Agree as a cohort on how you will manage this.

Questions you can use to help this organisation:

1. How long should each person (group of people) be responsible for each goal? 1 week? 2 weeks?
2. How will we communicate to our community who is the person responsible right now?
3. Is there any role missing?

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-volunteer-team Slack channel canvas.

Breaks

No one can work solidly forever! Make sure to take breaks when you need.

Finished everything?

If you have finished everything in the backlog you can use this time to practice some other skills which will be useful in your future careers. We have some suggestions below: