🎯 Goal: Let’s wake up and have a laugh (15 minutes)1. Interviewer: Cold call a random person and ask them an interview question. Choose an ordinary question.
2. Interviewee: You must give a terrible answer to this question (keep it clean, please!). Then cold call another person to be the interviewer.
3. Interviewer: Give absolutely straight-faced feedback. If you laugh, you’re out and must nominate another player to complete your feedback and return the game to step 1.
You have two main goals for today:
Make your demo in 5 minutes
Appraise your peers’ demo, asking questions if you have any.
🎯 Goal: Present your achievements in a 5-min demo (5 minutes)
- Identify what your slot is for presenting.
- Make sure your presentation is up and running.
- Do some nerve-calming exercises so you feel more confident.
- Present amazingly.
A quick break of fifteen minutes so we can all concentrate on the next piece of work.
Identify clear examples of positive and negative points you want to discuss.
Define which board you want to use to capture the feedback. Miro, Figjam, EasyRetro, etc.
You can open the board and ask people to add examples beforehand (steps 1 and 2 of the exercise).
🎯 Goal: Assess the positive and negative traits in your team’s (60 minutes)
Open the chosen board.
Give everyone 5-10 minutes to add their examples. Make sure you use 1 post-it/ticket per example.
Start reviewing the examples.
- Usually, we start with the positive ones first.
- Ask the person who wrote the example to give more input to the group
- Open it up for questions and detailing
Agree on an action for that example, if applicable.
- Write the action on the board
- Define who in the team will be responsible for delivering it
- Agree on a deadline.
Cooling period (optional)
🎯 Goal: Solving conflicts as part of a team (30 minutes)
Conflicts are part of life. It can occur more often in high-pressure moments, such as delivering a product in a short period. It might happen at any moment in the week, but the retrospective usually brings them up more clearly.
If you see that you and your team struggle to collaborate, communicate or work together positively, and conflict is getting heated, you can use this cooling technique.
- Stop working and take a 5-minute break.
- Reflect on what you think is working well and what is not working.
- Discuss your preferred ways to communicate.
- Re-establish how you will work together as a team.
- Create a 5-step action plan about how they will resolve further challenges.
If the conflict is about one specific individual, they must talk to a volunteer about the following:
- Their strengths and weaknesses.
- Reflections on how they will work together with the team.
- Clear action plan to resolve further challenges.
This must be done so the trainee can work on the team again.
Every Saturday at CYF 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.
Agile software teams often work in ‘sprints’ - specific chunks of time where we commit to a development goal, like “Goal: Get the homepage working”. We try to set a single goal and focus on reaching it together as a team.
This helps ensure we’re working on the most important thing (we’ll have lots of ideas for different things we can build, and we don’t want to get distracted). And it should encourage us to work together as a team.
For this project, we’ll be doing 1 week sprints. So, we should plan and start a new sprint at the start of each week.
Sprint planning is the process of planning our week, specifically focused on our development backlog and picking which user stories to include.
Plan the sprint
🎯 Goal: We have a 1 sprint of work planned in our project board (45 minutes)
- As a group, review the Backlog of user stories on your Project Board
- Discuss the user stories - make sure they all have a detailed description of what you need to build and check that everyone in the team understands them. You can check this by asking everyone - would you feel comfortable implementing this yourself? (if no, check why not and add more information)
- Arrange the user stories in priority order - put the most important ones first. These stories should help us reach our MVP and solve customer problems faster.
- Start moving the user stories from your Backlog column to the Prioritised column. Keep going until you have enough for a week of work - this is your ‘sprint’. Estimating how much you can do in a week might be tricky. Tip: not enough is better than too much. We can always add more later.
- Describe your week of work as a goal in a single sentence. Keep it focused on your product, not the technology. For example, “Goal: Get the homepage working” is better than “Goal: Setup the SQL database.”
- Post your goal to the class Slack channel, e.g. “This week’s sprint goal for the Amazing Coderz team is: Get the homepage working!”
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.
This time is set aside to work as a team on your project.
Use this time wisely
You will have project time every Saturday. Don’t waste it. Use it to: