From 5714c2300a6fc840912e44fda446efaa6f64be2c Mon Sep 17 00:00:00 2001 From: Daniel Wagner-Hall Date: Tue, 9 Dec 2025 15:20:54 +0000 Subject: [PATCH 1/2] Action items from retro after October run --- .../module/piscine/assessing-demos/index.md | 2 ++ .../en/module/piscine/briefing/index.md | 21 ------------ .../en/module/piscine/expectations/index.md | 4 ++- .../en/module/piscine/goals/index.md | 2 +- .../en/module/piscine/induction/index.md | 17 +--------- .../en/module/piscine/intentions/index.md | 10 +++++- .../piscine/practice-break-down/index.md | 33 ++++++++++++------- .../piscine/pre-piscine-briefing/index.md | 31 +++++++++++++++++ .../en/module/piscine/preparation/index.md | 2 +- .../piscine/project-submission/index.md | 8 ++++- .../content/for-volunteers/index.md | 3 ++ org-cyf-piscine/content/prep/index.md | 3 ++ .../content/sprints/1/day-plan/index.md | 11 ++++--- .../content/sprints/3/day-plan/index.md | 4 +-- org-cyf-piscine/content/success/index.md | 2 +- 15 files changed, 92 insertions(+), 61 deletions(-) delete mode 100644 common-content/en/module/piscine/briefing/index.md create mode 100644 common-content/en/module/piscine/pre-piscine-briefing/index.md diff --git a/common-content/en/module/piscine/assessing-demos/index.md b/common-content/en/module/piscine/assessing-demos/index.md index 6a773cbea..8fa24b396 100644 --- a/common-content/en/module/piscine/assessing-demos/index.md +++ b/common-content/en/module/piscine/assessing-demos/index.md @@ -11,6 +11,8 @@ We assess demos against 6 rubric points. A demo must pass any 5 of the 6 points We give feedback after every demo, including a run-down of each rubric point. +Where possible, we suggest having two assessors in a demo session, to get more opinions and discuss any uncertainty. + These are typically our trainees' first demos. We expect significant improvement through the course. The first sprint is expected not to be good (but sometimes is!).
diff --git a/common-content/en/module/piscine/briefing/index.md b/common-content/en/module/piscine/briefing/index.md deleted file mode 100644 index eaf788912..000000000 --- a/common-content/en/module/piscine/briefing/index.md +++ /dev/null @@ -1,21 +0,0 @@ -+++ -title = "Briefing" -time = 30 -[build] - render = "never" - list = "local" - publishResources = false -+++ - -You probably aren't sure exactly what the Piscine will be like. - -Take this time to discuss any questions you may have with your facilitator and cohort. - -Make sure you know: -* What's expected of you today. -* What's expected of you this week. -* How you should be working as a team. -* How you'll be assessed. - * Which of your projects, demos, and interview you need to pass, and what it means to pass them. -* When you're expected to show up in person or on calls. -* How you'll hand in your projects. diff --git a/common-content/en/module/piscine/expectations/index.md b/common-content/en/module/piscine/expectations/index.md index 19e2f28f9..8cd892490 100644 --- a/common-content/en/module/piscine/expectations/index.md +++ b/common-content/en/module/piscine/expectations/index.md @@ -13,16 +13,18 @@ hide_from_overview="true" ## Trainees, we expect you to: +- Check Slack at least once a day and respond to any messages. - Work in groups and individually, in class and during the week. - Show up on time and participate in all activities, including helping others. - Complete the projects in the way they are specified. +- Not over-focus on styling. We often see trainees fail because they spent most of their time working on beautiful CSS, but then not complete the project. Don't make this mistake. You're allowed to style things as much as you want, but won't get _any_ credit for doing so. - Do your best. ## Trainees, you can expect: - Your team to work _with_ you to complete the projects. - A fair assessment, explained clearly. -- Help from volunteers and other candidates with your code and blockers. +- Help from volunteers and other candidates with your logistical blockers. ## We expect everyone to: diff --git a/common-content/en/module/piscine/goals/index.md b/common-content/en/module/piscine/goals/index.md index bfa31f56a..cd72f690c 100644 --- a/common-content/en/module/piscine/goals/index.md +++ b/common-content/en/module/piscine/goals/index.md @@ -15,7 +15,7 @@ objectives = [ Your goal is to build two group projects and one solo project over the next 22 days. For each project, your goal is to: -- 🎯 Build a complete project that meets the requirements, including tests. +- 🎯 Build a complete project that meets all of the requirements, including tests. - 🎯 Build a complete understanding of all the code in your project, because you will be asked to explain it. _Our_ goal is to find people who are ready to train in the Software Development Course. This means we are looking for people ready to begin working as a professional software engineer within the next 16 weeks. This is why we are looking at your ability to: diff --git a/common-content/en/module/piscine/induction/index.md b/common-content/en/module/piscine/induction/index.md index ad4ee01a2..c45ffd129 100644 --- a/common-content/en/module/piscine/induction/index.md +++ b/common-content/en/module/piscine/induction/index.md @@ -9,25 +9,10 @@ time=15 Welcome to the Piscine. -Before you came to class today, you should have completed the prep and signed the Trainee Agreement and the [Code of Conduct](https://codeyourfuture.io/about/code-of-conduct/). If you haven't done the prep, it's time to leave. Thanks, and try again next time. +Before you came to class today, you should have completed the prep and attended a briefing session. If you haven't done these things, it's time to leave. Thanks, and try again next time. If you have done the prep, you're in the right place. Please make sure you have signed the register. Sign it as soon as you come in. The register isn't just for attendance rules; we need to know who is in the building if there's a fire, so please don't sign in for anyone else. -Next up, we need to choose a timekeeper. The timekeeper is responsible for keeping us on track and making sure we finish on time. Who would like to volunteer? - -
- - -#### ⏰ 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 -
- Today you will kick off your first team project. Everyone will also give a demo about something they did before the Piscine. At the end of the day, we will wrap and people are welcome to stick around to socialise. But first, let's get to know each other. Stand up and find someone you don't know. Introduce yourself and tell them one thing you are looking forward to learning in the Piscine. diff --git a/common-content/en/module/piscine/intentions/index.md b/common-content/en/module/piscine/intentions/index.md index 11e5ab4d6..fe1ef82d1 100644 --- a/common-content/en/module/piscine/intentions/index.md +++ b/common-content/en/module/piscine/intentions/index.md @@ -13,4 +13,12 @@ As a **facilitator**, your goal is _not_ to help the trainees with their project As an **assessor**, your goal is to provide meaningful feedback to help the trainees to grow. For demos, we provide this feedback after each demo. For projects, we provide this feedback after the interview is complete. -There is currently one exception to this: [Breaking down a project to work on as a group is a skill not currently taught in ITP](https://github.com/CodeYourFuture/curriculum/issues/1441). Until this is resolved, we host a single, consistent workshop on this in the first sprint. +If you feel a rubric clarification is needed, coordinate with the other assessors before providing this clarification. We need to make sure everyone gets the same clarification. + +Below is a list of learning objectives that are not currently taught in ITP, and how we handle them in the Piscine: + +| Learning Objective | How we handle it | +| -------------------|------------------| +| [Break down a project to work on as a group in parallel](https://github.com/CodeYourFuture/curriculum/issues/1441) | We teach this in a workshop in sprint 1 | +| [Test a project reasonably thoroughly](https://github.com/CodeYourFuture/curriculum/issues/1616) | We only require one non-trivial test | +| Anticipate and prevent time-zone and daylight-savings bugs | Time-related project briefings, contain warnings and guidance | \ No newline at end of file diff --git a/common-content/en/module/piscine/practice-break-down/index.md b/common-content/en/module/piscine/practice-break-down/index.md index ed572e3bc..3bba4a241 100644 --- a/common-content/en/module/piscine/practice-break-down/index.md +++ b/common-content/en/module/piscine/practice-break-down/index.md @@ -1,6 +1,6 @@ +++ title = "Practice breaking down a requirement" -time = 60 +time = 45 objectives = [ "Break down a requirement into approachable tasks.", "Coordinate multiple team members in executing tasks in parallel.", @@ -19,13 +19,13 @@ Finally, it's important that we arrange tasks so your team isn't blocking yourse We will practice this together on the two of the requirements of the project: -- Selecting a user must display the agenda for the relevant user (see manual testing below) -- Submitting the form adds a new topic to revise for the relevant user only +- Selecting a user must display the list of bookmarks for the relevant user +- Submitting the form adds a new bookmark for the relevant user only To complete these requirements we'd need to build most of the project! So we'll focus on simplified versions of these requirements: -- When the page loads, display one revision date for one topic from in User 1's stored agenda -- When clicking a button, store {{}}Hard-coding refers to when developers directly write values or data into code, often replacing variables or user input with static values.{{}} data for User 1's agenda +- When the page loads, display one bookmark from User 1's stored agenda +- When clicking a button, add a {{}}Hard-coding refers to when developers directly write values or data into code, often replacing variables or user input with static values.{{}} bookmark to User 1 To complete the full requirements, you can build on the tasks we decide on today. @@ -38,17 +38,28 @@ To complete the full requirements, you can build on the tasks we decide on today {{}} -Looking ahead to your coursework for the next week, one of your tasks will be to [Refine a ticket](https://github.com/CodeYourFuture/The-Piscine/issues/6). +Our goal right now is to make sure we refine the tickets so that two different people could be working on tasks at the same time. -{{}} +{{}} -1. Everyone read the [Refine a ticket coursework task](https://github.com/CodeYourFuture/The-Piscine/issues/6), for {{}}3{{}}. -2. Get into pairs. Each pair should then pick 2 of the tasks from the whiteboard (it doesn't matter if multiple pairs do the same task). Spend {{}}10{{}} refining your tickets in your pairs. Make sure you work through **all** of the workflow points. -3. Go around each pair in the group. The pair should pick 1 of their tasks and say what they think the priority, estimate, schedule and type of work the task is, and if there is anything they would need to know before starting the ticket. (Hint: the last point is **important**! Don't skip it!) -4. As a group, pick a task (or two, depending on time) that needs more information. Spend {{}}10{{}} discussing what actions you could take to ensure everyone has what they need to complete this task? +1. Set a timer for {{}}10{{}} + +Work out what blockers would limit the tasks so that only one person could be working at a time. + +Define additional tasks that can be done first to unblock parallel working. {{}} +Discuss as a group how we can unblock parallel work. + +
+ +Tips for volunteers + +The big insight we're looking to drive here is that agreeing a data format in advance means we can work in parallel. + +
+