🧑🏽‍🤝‍🧑🏽 day-plan

🔖
  1. Energiser
  2. Morning orientation
  3. Teamwork Project Sprint 2
  4. lunch
  5. Study Group
  6. Code Review
  7. Afternoon break
  8. Study Group
  9. Retro

✍🏽 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.

  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, create a post on Slack and get some people to take on the roles of facilitator and timekeeper. Nominate new people each time.

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

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

  3. Ask any newcomers to introduce themselves to the group, and welcome them.
  4. 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.
  5. 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 S2

Learning Objectives

Preparation

Have post-its and pens and a collaborative board

Introduction

You will work together through these exercises to ensure everyone understands and can apply the concepts your read about.

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.

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

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

🛎️ Code waiting for review 🔗

Below are trainee coursework Pull Requests that need to be reviewed by volunteers.

Glasgow | May-2025 | Mansoor Munawar | Data Groups| Sprint 2 🔗

Learners, PR Template

Self checklist

  • [ y] I have committed my files one by one, on purpose, and for a reason
  • [y ] I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
  • [y ] I have tested my changes
  • [y ] My changes follow the style guide
  • [y ] My changes meet the requirements of this task

Changelist

Briefly explain your PR. I completed the exercises for sprint-2 which included degbugging programs, implementing function and test based on set requirement, and leaving comments detailing program execution and where the bug is located within the program.

Questions

Ask any questions you have for your reviewer.

Start a review
London | 25-ITP-May | Houssam Lahlah | Sprint 3 | Slide show 🔗

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

## Changelist

What I did:

  • Built a JavaScript-powered image slideshow.

  • Implemented manual navigation using Next and Previous buttons.

  • Added automatic slideshow functionality that cycles through images at a set interval.

  • Ensured the slideshow loops correctly when reaching the start or end.

  • Used setInterval and clearInterval to manage timing and prevent conflicts.

## Questions

  • Do you think the code handles both manual and automatic slideshow smoothly?

  • Is the interval management clear and easy to maintain?

  • Any improvements for better accessibility or responsiveness?

Start a review
London | ITP-May-25 | Houssam Lahlah | Sprint 3 | Reading List 🔗

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

## Changelist

What I did:

  • Implemented a reading list that dynamically displays a list of books using JavaScript.

  • Displayed book title and author, and added book cover images.

  • Highlighted books that are already read by changing their background color.

  • Structured the page using semantic HTML (ul, li, p, img).

  • Followed best practices for DOM manipulation and accessibility.

## Questions

  • Do you think the logic for marking books as read is clear and maintainable?

  • Is there anything I could improve in how I structure the list items or apply styles?

  • Is my use of JavaScript efficient and clear?

Start a review
London | 25-ITP-May | Houssam Lahlah | Sprint 3 | Alarm Clock 🔗

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

## Changelist

What I did:

  • Implemented the alarm functionality in alarmclock.js, including countdown logic and triggering audio when the timer reaches zero.
  • Ensured the alarm display updates every second in the format Time Remaining: MM:SS.
  • Connected the “Set Alarm” button to trigger the setAlarm() function.
  • Made functions (setAlarm, playAlarm) testable by exporting them.
  • Ensured compatibility with the test runner by checking typeof document.

## Questions

  • Do you see any potential bugs or improvements in the setAlarm() function structure?

  • Is there a cleaner way to format the MM:SS display?

  • Would you suggest improvements for accessibility or code readability?

Start a review
London | 25-ITP-May | Houssam Lahlah | Sprint 3 | Quote-Generator 🔗

Self checklist

  • I have committed my files one by one, on purpose, and for a reason
  • I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
  • I have tested my changes
  • My changes follow the style guide
  • My changes meet the requirements of this task

## Changelist

What I did:

  • Updated the button text from “Generate Quote” to “New quote” in the HTML to match the expected value in the test.

  • Updated quote.js to ensure clicking the button triggers a new quote.

  • Verified functionality works as expected and tests pass.

Why:

This change ensures the UI aligns with the test cases, maintaining consistency and passing all automated checks.

Questions for Reviewer

  • Is the button label “New quote” the best choice, or would a different label be more clear or accessible?

  • Should I make any further style changes to improve readability or usability?

  • Is the function in quote.js structured well, or would you suggest any improvements?

Start a review
See more pull requests

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

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