π§πΎβπ€βπ§πΎ day-plan
βπ½ Register
Blockers!
Learning Objectives
π Traffic Jam Gameplay
In groups or breakout rooms of 4 trainees maximum.
One person will share their screen and be the driver. The driver can only move the pieces where you are told by the navigators. The driver cannot make any decisions!
The others will be the navigators. Together, the navigators must figure out a strategy to unblock the car, and tell the driver how to do it!
Each person must drive so set a timer for and then swap.
You can do this energiser in person, online, or a mix of both. You can play this completely offline using this kit: Rush Hour.
Start on Level 6 or above and get everyone to load the page before you go into breakout rooms/groups. Put your adblocker on!
Facilitator Check in questions
- Which car is the blocker? Everyone guess!
- What shall we do first?
- What do you notice about the cars? Are they different sizes?
- What do you notice about the board? What does this mean for our choices?
- Is it frustrating being the driver?
- Are we there yet? Shall we play another round?
- What one thing shall we say we noticed about this game, back in the main room?
Evolve the game
- Round 2: You must discuss for 1 minute before you make any moves
- Round 3: A single navigator can make no more than three moves in one go
- Round 4: Try to solve the puzzle in as few moves as you can
More resources
- Backup alternative online game
- Physical version of this game
Demo
Learning Objectives
At CYF we expect you to demo your work to the class. You must have many opportunities to practice how to clearly and simply explain your work to others. This is really important for interviews and career success.
β° Timekeeper
The timekeeper will keep the groups on track.
Split randomly into groups of no more than 4 people. Mix up your teams. Each person will have 2 minutes to demo their work to the group. After the demo, the group will ask questions or give feedback for 5 minutes. Then the next person will demo their work.
π§πΌβπ Trainees
1. Demo
You will demo something about your work to the group.
You will have 2 minutes to explain what you did and why. It’s ok to show broken code or a system that doesn’t work yet. Just make sure your demo is interesting.
2. Feedback
After the demo, the group will give you feedback for up to 5 minutes. It’s smart to suggest what kind of feedback you want by asking some “generative” questions. For example:
- I wasn’t sure if it makes sense to try X. What do you think?
- I liked the way I did X, but I know there are other approaches, what did you do?
- I found X really confusing, did anyone else have the same problem?
π‘ Tips:
- Practice the format of demos before class.
- Keep it simple. Don’t try to show everything you did. Just show one interesting thing.
- Keep it short. Two minutes is enough.
- Explain what you did and why.
- Show your code, system, or other artefacts of work.
- Ask for feedback.
Morning Break
A quick break of fifteen minutes so we can all concentrate on the next piece of work.
Workshop π
Learning Objectives
SAP Financial Document Processing
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.
Project π
Learning Objectives
Challenge: The Returns Team is Drowning
“We’re getting too many small returns and can’t keep up!”
Task:
Afternoon Break
Please feel comfortable and welcome to pray at this time if this is part of your religion.
If you are breastfeeding and would like a private space, please let us know.
Team Development
Learning Objectives
This time is set aside for you to work together as a team to make progress on your project.
Remember: At your interview, you may be asked about any code in your project, not just the code you wrote. You need to understand and be able to explain the code your team mates wrote. Make sure you read their code, review it, and talk to them about it.
Wrap
You are done for the day. Take a moment to reflect on what you have learned and achieved.
Stand in a circle and share:
- π your name
- πͺπ½ one thing you built today
- π·πΎ the task you are going to work on next
- π one thing you need help with
Give yourselves a round of applause. Now you have earned your rest. Usually people go for a cup of tea or a pint after class. You are welcome to join and wind down together.