πŸ§‘πŸ½β€πŸ€β€πŸ§‘πŸ½ day-plan

πŸ”–
  1. Energiser
  2. Morning orientation
  3. Teamwork Project Sprint 1
  4. Lunch
  5. Study Group
  6. Retrospective

πŸ”‹ 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.

  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.

🎑 Morning orientation

Learning Objectives

Planning during the week

🧭 During the week, we create a post on Slack to assign the roles of facilitator and timekeeper. The roles rotate.

πŸ‘£ To Do

πŸŽ™οΈ The Facilitator will:

  1. Assemble the entire group (all volunteers & all students) in a circle
  2. 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}”

  3. 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.
  4. 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 S1

Learning Objectives

Preparation

You must have done the prep work.

Introduction

Collaborative software development equals higher-quality products and efficient development cycles. Team synergy, knowledge, and diverse skills are crucial to achieving this. We are going to talk about these roles and their responsibilities.

Brainstorm about teamwork in the tech industry.

🎯 Goal: Discuss teamwork in the tech industry. (35 minutes)

Think about the teams you will work with in tech. Discuss in your team:

  • What is your dream job?
  • What professional roles will be in your team?
  • What other people/teams will you interact with?
  • What non-technical skills will you bring?
  • What non-technical skills should you develop while at CYF?
  • Which of the Belbin’s tole do you identify strongest with?
  1. Define which team member wο»Ώill be the time keeper for your team.
  2. Work in your teams for about 10 minutes and write down brief answers to each question.
  3. Assign one of the team members as speaker to deliver your answers back to the class in maximum 2 minutes.

Discuss the roles in a product team

🎯 Goal: To discuss the importance of different roles in tech teams. (10 minutes)

The following are the roles typically found within a development team. As you see, there are plenty of roles other than β€˜Full-Stack Developer’.

Discuss as a class the responsibilities of the following tech roles.

Write a brief description for each of them on a post-it and share the post it on a collaborative board:

  • Front-end web developer
  • Back-end web developer
  • UX/UI designer
  • UX researcher
  • Product manager
  • Quality Assurance/Quality Engineer (tester)
  • Tech lead

Team Charter

🎯 Goal: To discuss the importance of setting clear goals and responsibilities within a team. (15 minutes)

You might come across a ceremony called β€œteam charter” in your future work.

Team charters define roles, responsibilities and ways of working. If these are not clear to you when you join a new company, you should ask and seek clarification urgently.

Discuss as a class:

  • Why is it important for your team to understand their main goal?
  • Why is it important for everybody on your team to understand the role each other plays?
  • What is the importance of having clear ways of working?
  • What happens when you are not clear about these three points?

Spend the rest of your time clarifying any questions about the project and the coursework for the first week.

🍽️ 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.

  1. Set a timer for 5 minutes. There’s one on the RetroTool too.
  2. Write down as many things as you can think of that you’d like to start, stop, and continue doing next sprint.
  3. Write one point per note and keep it short.
  4. When the timer goes off, one person should set a timer for 1 minute and group the notes into themes.
  5. 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.
  6. Finally, set a timer for 8 minutes and all discuss the top three themes.