Add 'Breaking down a project to work in parallel' workshop (ITP, #1441)

[abdishakoor-dev]

First pass for #1441

An ITP workshop on breaking a project into tickets for parallel work (so it's taught in ITP, not Checkpoint). Reflects on how Tic-Tac-Toe was broken down, teaches the steps, then groups practise on a fresh localStorage requirement. Added to the Data-Groups Sprint 2 day-plan (~50 min, from Study Group).

Preview: /itp/data-groups/sprints/2/day-plan/

Questions/conerns:

• Is Sprint 2 + ~50 min the right placement/budget? Morning sessions already have some workshops/handson, and this one feels heavy and it's after lunch
• It assumes trainees (and volunteers) having completed or being familiar with the Tic-Tac-Toe exercise. Is this a safe assumption.
• It assumes they have knowledge to work with localStorage.

[netlify]

✅ Deploy Preview for cyf-common ready!

Name	Link
🔨 Latest commit	7d499b5
🔍 Latest deploy log	https://app.netlify.com/projects/cyf-common/deploys/6a4ff3a8c690ee0008c7b341
😎 Deploy Preview	https://deploy-preview-1939--cyf-common.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for cyf-curriculum ready!

Name	Link
🔨 Latest commit	7d499b5
🔍 Latest deploy log	https://app.netlify.com/projects/cyf-curriculum/deploys/6a4ff3a7037aab000845d509
😎 Deploy Preview	https://deploy-preview-1939--cyf-curriculum.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 90 (🟢 up 5 from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 100 (no change from production) PWA: - View the detailed breakdown and full score reports
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[illicitonion]

Content-wise, this looks great, I left a couple of small comments.

Location-wise... In theory they start the tic-tac-toe this week, and finish it the next week. They also won't have interacted with the DOM yet, so may struggle with the to do list break-down slightly. I'd suggest moving this to data-flows sprint 2 (where they've just learnt about rendering based on state) and just completely replacing the "Teamwork Project Sprint 2" workshop (which feel quite low value) with this. WDYT?

[abdishakoor-dev]

Thanks. Done:

• Moved to Data-Flows Sprint 2, replacing Teamwork Project Sprint 2 (Study Group → 180 to keep the day the same length).
• Un-bolded that line.
• Reframed the practice to a global variable instead of localStorage.

Also inlined the stub/hardcode definitions (they were tooltip-overlapping).

[illicitonion]

Looks great, thanks!

Just one more thing - we typically try to always have lunch start at 1pm - how about we extend the demo-qa session by 15 minutes, and add a 15 minute morning break between workshops, so that lunch gets back to 13:00?

[abdishakoor-dev]

Good catch! Lunch is now 13:00. Bumped Demo Q&A to 75 and added a 15 min break; also put Study Group back to 150 so the day ends on time.