π§π½βπ€βπ§π½ day-plan
π 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
π£ To Do
ποΈ The Facilitator will:
- Assemble the entire group (all volunteers & all students) in a circle
- Briefly welcome everyone with an announcement, like this:
π¬ “Morning everyone, Welcome to another Saturday at MigraCode, this week we are working on Module X Sprint 3 and we’re currently working on {summarise what the topic of the week is}”
- 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 add one thing you hope to find out or learn about today.
β° 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 S2
π€π½ FeedbackLearning Objectives
Preparation
Introduction
Discuss the theory you read about
π― Goal: To explain the product, MVP, feature, and user story concepts (20 minutes)
Create a collaborative board with the following concepts
- Product
- MVP
- Feature
- User story
Briefly discuss as a class what we mean by each concepts.
Each trainee should write 1 phrase/word per Post-it (e.g. The first working software) and put it in against the concept (in this example, MVP) on the collaborative board
Review the posts as a group
Ensure any questions are clarified
Who will use your product?
π― Goal: To identify the users of a product (20 minutes)
During the previous week’s coursework, you defined your team’s product.
Discuss the following questions as a team to identify your product’s users.
- Who are your users?
- What different user profiles will be?
- What user needs does your product try to address?
Write down a a short description of your product, users, and user needs, which will be played back to the wider group.
One speaker will represent the team (ideally not the same person that talked in the previous lesson). Each speaker has only 1 minute to describe the product, user and user needs.
Make sure someone is the time keeper so all groups have the same amount of time.
Brainstorming about your users' problems
π― Goal: To identify how products achieve user needs (20 minutes)
In your teams, brainstorm the following questions to understand your product better.
- What is the functionality of your product?
- How does it address the user’s needs / solve their problem?
Pair with another team.
Share your answers to the questions above in turns.
Provide feedback, opinions, and additional suggestions to each other.
π½οΈ Lunch
At MigraCode, there will be scheduled community lunches throughout the year during which all of MigraCode team will joing and would like to invite you to eat with us. The MC team will let you know when the upcoming community lunch will be. Bring your home-cooked food or buy some food across the street at Glories (e.g., at the Carrefour Supermarket or pick up some to-go meal from one of the restaurants there). We share our time, food and our stories. We learn about each other and the world. We build community.ππ¬
On days where there is no community lunch planned you can still stay to socialise here and use the terrace to meet you peers and connect (this goes especially for class days that are longer than just until 2pm.)
Adevinta allows us to use their beautiful space, cutlery, plates, microwaves etc - please make sure to leave everything exactly as it was before so they keep lending their precious space to us βΊοΈ. Ah and make sure to check out the foosball table on the terrace.
π Study Group
Learning Objectives
What are we doing now?
You’re going to use this time to work through coursework. Your cohort will collectively self-organise to work through the coursework together in your own way. Sort yourselves into groups that work for you.
Use this time wisely
You will have study time in almost every class day. Don’t waste it. Use it to:
- work through the coursework
- ask questions and get unblocked
- give and receive code review
- work on your portfolio
- develop your own projects
π 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.