ITP Data Flows S3: improve teamwork workshop clarity and structure#1842
Draft
omkarv wants to merge 2 commits intoCodeYourFuture:mainfrom
Draft
ITP Data Flows S3: improve teamwork workshop clarity and structure#1842omkarv wants to merge 2 commits intoCodeYourFuture:mainfrom
omkarv wants to merge 2 commits intoCodeYourFuture:mainfrom
Conversation
✅ Deploy Preview for cyf-curriculum ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
👷 Deploy request for cyf-common pending review.Visit the deploys page to approve it
|
illicitonion
approved these changes
May 8, 2026
Member
illicitonion
left a comment
illicitonion
left a comment
There was a problem hiding this comment.
This looks great, thanks so much for putting it together!
| {{<tabs name="Teamwork Project Sprint 3" >}} | ||
|
|
||
| ===[[👉🏽 PD Session]]=== | ||
| ⏱️ **Time:** 15 minutes |
Member
There was a problem hiding this comment.
WDYT about:
Suggested change
| ⏱️ **Time:** 15 minutes | |
| ⏱️ **Time:** 15 minutes (for this section - 90 minutes for the whole workshop) |
To avoid someone thing the whole workshop is 15 minutes?
github-project-automation
Bot
moved this from 📋 Backlog
to 👀 In review
in Curriculum Planning
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Improvements to the Sprint 3 teamwork workshop block based on observations from delivering the session. Full context in this Slack thread:
https://codeyourfutur-yov6609.slack.com/archives/C07U0V5A51R/p1776165328432989
1. Fix inconsistent framing in Exercise 1
The tab title asked "what questions should we ask to identify what was built?" but the exercise itself is about a product not yet built. Renamed to "what questions should we ask to understand what we need to build?" to match the actual instructions and avoid confusing trainees.
2. Add explicit timing throughout
The PD Session intro and Exercises 1 and 2 had no ⏱️ timing markers, making it hard for facilitators to pace the session. Added timings for all tabs, and added a 15-minute break between Exercises 2 and 3 (the full morning block is ~2h20 with only one break previously).
3. Clarify the user story → task transition in Exercise 4
A couple of groups struggled to move from user stories to concrete tasks and ended up writing more stories instead. Added:
4. Add a wrap-up tab
The real-world discussion with volunteers at the end of the session worked particularly well but was unscripted. Added an explicit wrap-up tab with prompts to anchor the conversation (how teams manage backlogs, who writes stories, how dependencies are handled in a sprint).