Skip to content

ITP Data Flows S2: make teamwork workshop standalone with job board scenario#1843

Merged
illicitonion merged 6 commits into
CodeYourFuture:mainfrom
omkarv:fix/itp-s2-teamwork-standalone-job-board
May 14, 2026
Merged

ITP Data Flows S2: make teamwork workshop standalone with job board scenario#1843
illicitonion merged 6 commits into
CodeYourFuture:mainfrom
omkarv:fix/itp-s2-teamwork-standalone-job-board

Conversation

@omkarv
Copy link
Copy Markdown
Contributor

@omkarv omkarv commented Apr 24, 2026

The Sprint 2 teamwork workshop had a broken cross-sprint dependency. Exercise 2 referenced "the product your team defined in the previous week", but Sprint 1 never defines a product. This PR makes the session fully standalone and sharpens the product/BA framing that is the focus of this sprint.

Full context in this Slack thread:
https://codeyourfutur-yov6609.slack.com/archives/C07U0V5A51R/p1776165328432989

Note on scenario choice: The original workshop used the library project, which ties to the Book Library coding exercise trainees do in Sprint 2. This PR switches to a job board scenario to reduce overlap with the Sprint 3 workshop which also uses the library. Happy to revert to the library if the team prefers continuity, the structural improvements (standalone framing, timings, prioritisation focus, wrap-up) apply either way.

1. Fix cross-sprint dependency

Replaced "the product your team defined in the previous week" with an explicit scenario: a job board for people looking for their first role in tech. The scenario is intentionally different from the library website used in Sprint 3 so each session feels distinct.

2. Reframe the introduction around the product/BA lens

The original intro ("we move from theoretical concepts to defining the core of your specific project") implied prior context. The new intro sets the scene: before any code is written, product managers and business analysts work with stakeholders to understand what to build and why.

3. Richer user definition in Exercise 2

Updated the discussion prompts to reflect the job board scenario with more varied user types (first-time jobseeker, recruiter, hiring manager). Added two questions that push into BA thinking: "How might those needs conflict?" and "Which users matter most for your MVP?"

4. Add prioritisation to Exercise 3

Added a step asking teams to pick their top three MVP features and defend the choice. Gives the peer review something more concrete to push back on, and mirrors real product decision-making.

5. Add a break and a wrap-up tab

Added a 15-minute break after Exercise 2, and a wrap-up tab with volunteer discussion prompts focused on product/BA practice (user research, stakeholder disagreements, roadmap decisions).

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 24, 2026

👷 Deploy request for cyf-curriculum pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 5dfcac8

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 24, 2026

👷 Deploy request for cyf-common pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 5dfcac8

Copy link
Copy Markdown
Member

@illicitonion illicitonion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you so much!

It looks like this contains #1842 as well? Happy to merge either or both! Just one comment - let me know what you think :)

Comment thread common-content/en/blocks/teamwork-project-s2/index.md Outdated
Comment thread common-content/en/blocks/teamwork-project-s3/index.md Outdated
@github-project-automation github-project-automation Bot moved this from 📋 Backlog to 👀 In review in Curriculum Planning May 8, 2026
Co-authored-by: Daniel Wagner-Hall <dawagner@gmail.com>
@omkarv
Copy link
Copy Markdown
Contributor Author

omkarv commented May 13, 2026

Updated the PR with latest mainline commits and addressed comments

@omkarv omkarv marked this pull request as ready for review May 13, 2026 13:48
Copy link
Copy Markdown
Member

@illicitonion illicitonion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks so much!

@illicitonion illicitonion enabled auto-merge (squash) May 14, 2026 10:53
@illicitonion illicitonion merged commit 1a62014 into CodeYourFuture:main May 14, 2026
3 checks passed
@github-project-automation github-project-automation Bot moved this from 👀 In review to ✅ Done in Curriculum Planning May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

2 participants