day-plan
Automated testing and deployments group work
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.
- 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.
Group Discussion
- ποΈ Nominate a facilitator (trainee or volunteer)
- β° Nominate a timekeeper (trainee or volunteer)
ποΈ Facilitator
Your role is make sure that everybody gets the chance to speak. Start the discussion by asking the group:
- What are the key ideas in this sprint that you want to discuss?
- What’s the biggest blocker you have right now?
Invite the group to spend β° 5 minutes writing down key ideas and blockers on a board.
π‘Use what works for your team
Vote on the focus
Give the group β° 2 minutes to vote on what to discuss. +1 on the question is fine.
π Begin with the most popular topic
Give the group β° 10 minutes to discuss the most popular topic. Move the discussion on if it gets stuck. If the group is struggling to come up with ideas, ask them to think about:
- What documentation relates to this topic?
- What other problem is this problem like, that you have met before?
- Is there another way to solve this problem?
π³οΈ Move on to the next topic
Keep the discussion moving and help the group to stay on track. Your job is to prevent “rabbit holing” on one topic.
β° Timekeeper
Keep the discussion on track by keeping an eye on the time. Use a stopwatch and give the group a 30 second warning before the end of the session.
Agenda
-
00:00 - 02:00: Nominate a facilitator and timekeeper -
02:00 - 07:00: Write down key ideas and blockers -
07:00 - 10:00: Vote on the focus -
10:00 - 20:00: Topic 1 -
20:00 - 30:00: Topic 2 -
30:00 - 40:00: Topic 3 -
40:00 - 50:00: Topic 4 -
50:00 - 60:00: Topic 5
Morning Break
A quick break so we can all concentrate on the next piece of work.
Demo
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 both for interviews and for getting promoted later on.
β° Timekeeper
The timekeeper will keep the groups on track.
Split randomly into groups of no more than 5 people. Each person will have 2 minutes to demo their work to the group. After the demo, the group will give feedback for 5 minutes. Then the next person will demo their work.
π§πΌβπ Trainees
1. Demo
You will demo 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 code 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?
- I wasn’t sure if I explained what an X was very clearly, how could I have explained it better?
More tips: A Good Question Can Be the Key to a Successful Presentation.
π‘ Tips:
- Practice your demo 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.
- Ask for feedback.
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
Trainees
This is time for you to get help with whatever you need help with.
If you didn’t understand something in the prep, ask about it.
If you were struggling with a backlog exercise, get help with it.
If you weren’t quite sure of something in a workshop, discuss it.
If you don’t have any problems, keep working through the backlog until you need help.
It can be useful to get into groups with others facing the same problem, or working on the same backlog item.
Volunteers
Don’t be scared to approach people and ask what they’re working on - see if you can help them out, or stretch their understanding.
If lots of people have the same problems, maybe you can put together a demonstration or a workshop to help them understand.
If absolutely no one needs help, consider reviewing some PRs using the process and guidelines in the #cyf-code-review-volunteer-team Slack channel canvas.
Breaks
No one can work solidly forever! Make sure to take breaks when you need.
Finished everything?
If you have finished everything in the backlog you can use this time to practice some other skills which will be useful in your future careers. We have some suggestions below:
Pair programming
Pair programming is very common in industry so it’s good to practice it now! Find a partner and choose a problem to work on, for example a Codewars kata. One person will be the “driver” and the other will be the “navigator”. Both of you will use the same laptop to complete the activity.
- The “driver” is the person typing on the keyboard, just thinking about what needs to be written
- The “navigator” reviews what the driver is doing and is thinking about to write next
- Switch between driver and navigator roles after
- Don’t dominate - this is teamwork
Code review
You will receive regular reviews of your work from volunteers when you submit a PR, but how comfortable are you giving a review? Find a partner and give each other feedback on one of the PRs you submitted this week. After you have given your feedback you should consider:
- How did you understand what the goal of the PR is? Did you read the title and description, look at the coursework exercises, etc.
- How did you use the different tabs in the PR:
Conversation,Commits,Files changed. - What made a PR easy or hard to review:
- Where unrelated files/lines changed?
- Was code consistently formatted? Did indentation help or hurt understanding?
- How did you review the code? Did you read top-to-bottom? Did you jump around into and out-of functions? Did you look at tests? Did you clone the code locally and try running it?
Prepare for your next demo
You need to give regular demos to complete the course. Use this time to work on your next one. You could:
- Prepare your slides
- Discuss topics
- Practice presenting
Share resources you have found
CYF aren’t the only resource available to you! If you have discovered a new book, YouTube channel or anything else you are using to help you learn this is an excellent time to share it with your cohort.
ποΈ 0 PRs available. Open some 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.
Experts AMA
π§πΌβπ Trainees
(If you don’t have a guest expert, do study group instead.)
Share your questions in a Slack thread by Friday 10am. This is an
π¦ΈπΎ Expert(s)
Read over the questions and prepare your answers before class if possible.
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.