ITP Data Flows S3: improve teamwork workshop clarity and structure

[omkarv]

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:

• A brief callout distinguishing user stories (what/why) from tasks (how)
• A worked example showing one user story broken into tasks with dependencies mapped in a table, and a note on sizing approaches (story points vs days)

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

[netlify]

👷 Deploy request for cyf-curriculum pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	d127a60

[netlify]

👷 Deploy request for cyf-common pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	d127a60