"Scrum does not change. The complexity of the system changes." — This is not a cliché. Every role on your team has two lenses: a Scrum responsibility and a system intelligence responsibility. Both must be fulfilled.
Diagram 4 — Role-System Mapping
Scrum Roles → System Responsibilities
Each standard Scrum role carries additional system intelligence responsibilities in CP3405. The Dev Team roles (R3–R10) are internal specialisations, not separate entities.
SCRUM ROLES
Product Owner
R1
Guards sprint value. Confirms Definition of Done. Owns the prediction call narrative.
↔ Sprint Goal Owner
Scrum Master
R2
Removes blockers. Protects team flow. Facilitates retrospective. Does NOT command the team.
↔ Process Health Guardian
Development Team
R3 – R10
Self-organising. Cross-functional. Builds and delivers the sprint increment. Internal specialisation below.
↔ Intelligence Pipeline Operators
↔
↔
↔
SYSTEM RESPONSIBILITIES
Sprint Intelligence Lead
System Layer: Output
Defines the prediction quality bar. Approves the final locked prediction. Narrates the system story on Monday.
↔ Final release sign-off
Pipeline Integrity Lead
System Layer: Process
Ensures the pipeline runs end-to-end. Identifies where the process broke down. Proposes system improvements in retro.
↔ Process → System feedback loop
Agent + LLM Operators
System Layer: Processing
Almanac R3, Macro R4, Technical R5, Data R6, LLM R8, Calibration R10 — each owns one stage of the pipeline.
↔ Manual → Automated pipeline
All Ten Roles — Sprint 4 Responsibilities
Sprint Contributions & Monday Presentation
If your automation is working, the pipeline collects the data — you review, judge, and lock. That is the Human Score, not data entry. The sprint contribution below shrinks every week as your system matures.
📓 A1 Workbook reminder — Your sprint contributions map directly onto your Weekly Workbook Tasks (W1–5, due Sun 28 Jun). Each role you perform this sprint is Application Task material. Each retrospective observation is a Micro Reflection. Record them as you go — don't leave it to Week 5.
R1 — Product Owner
Sprint Goal Guardian
Sprint contribution: Confirm the W4 sprint goal. Validate the Definition of Done. Make the final call on which prediction represents the team's best work.
Monday presentation: State the sprint goal. Announce DoD status. Deliver the final W4 prediction with confidence level.
Monday presentation: State the sprint goal. Announce DoD status. Deliver the final W4 prediction with confidence level.
R2 — Scrum Master
Process Flow Protector 📓 Micro Reflection
Sprint contribution: Coordinate deadlines across the team. Identify and remove blockers. Ensure every role participates. Run a brief Sunday retrospective check.
Monday presentation: Present the retrospective: what failed, what improved, and one specific process change for Sprint W4.
Monday presentation: Present the retrospective: what failed, what improved, and one specific process change for Sprint W4.
R3 — Almanac Agent
Historical Pattern Analyst
Sprint contribution: Pull seasonal patterns, historical analogues, and calendar-based signals (Fed meetings, options expiry, earnings seasons). Produce a written analysis before LLMs are queried.
Monday presentation: Present key seasonal insight and confidence contribution to final call.
Monday presentation: Present key seasonal insight and confidence contribution to final call.
R4 — Macro Agent
Macro-Economic Analyst
Sprint contribution: Analyse macro environment: inflation signals, Fed language, bond yields, dollar strength, sector rotation from Yahoo 5D / Finviz. Produce written output independently.
Monday presentation: Present the macro thesis supporting or undermining the team prediction.
Monday presentation: Present the macro thesis supporting or undermining the team prediction.
R5 — Technical Agent
Chart & Pattern Analyst
Sprint contribution: Analyse SPX, NDX, IWM charts. Identify key levels, trend structure, momentum signals, and volume patterns. Write independent technical output before LLMs.
Monday presentation: Present chart evidence and explain why the technical picture supports (or contradicts) the prediction.
Monday presentation: Present chart evidence and explain why the technical picture supports (or contradicts) the prediction.
R6 — Data / Actuals Agent
Evidence & Calibration Tracker
Sprint contribution: Record W2 actual outcomes against predictions. Calculate accuracy. Identify model disagreement vs. actual. Feed actuals into the calibration file.
Monday presentation: Present the W2 outcome vs. prediction and calibration score update.
Monday presentation: Present the W2 outcome vs. prediction and calibration score update.
R7 — Human Score Analyst ⭐ Most Important
Wild Card & Override Lead 📓 Application Task
Sprint contribution: After all agents and LLMs have reported, the R7 lead reviews the synthesis. Applies the Human Score. Decides whether to confirm, adjust, or override the AI consensus. Must justify the Wild Card observation.
Monday presentation: Present the Human Score reasoning. This is the primary marks differentiator. Weak R7 = weak team score.
Monday presentation: Present the Human Score reasoning. This is the primary marks differentiator. Weak R7 = weak team score.
R8 — LLM Operator
Multi-Model Comparison Lead
Sprint contribution: Query the three LLMs (ChatGPT, Gemini, DeepSeek) with identical prompts. Claude is optional — include it if you have access. Save raw responses. Build comparison table showing agreement, disagreement, and credibility assessment.
Monday presentation: Present which models agreed, which diverged, and what that reveals about the prediction uncertainty.
Monday presentation: Present which models agreed, which diverged, and what that reveals about the prediction uncertainty.
R9 — GitHub Lead
Evidence & Release Manager
Sprint contribution: Commit all evidence files. Ensure folder structure is clean. Create the correct release tag:
Monday presentation: Open GitHub live in the presentation. Show the release tag. Walk through the evidence folder structure.
vW24. Verify the release link is accessible before the Sunday deadline.Monday presentation: Open GitHub live in the presentation. Show the release tag. Walk through the evidence folder structure.
R10 — Calibration Lead
Accuracy & Learning Tracker
Sprint contribution: Maintain the calibration suite. Track directional accuracy per model and per agent over time. Identify systematic biases. Feed findings into R7's Human Score input.
Monday presentation: Present calibration trend. Are predictions improving? Which model has the best track record so far?
Monday presentation: Present calibration trend. Are predictions improving? Which model has the best track record so far?
Monday 15 June — Who Says What
| Role | Speaking Point | Evidence to Show |
|---|---|---|
| R1 Product Owner | Sprint goal, DoD status, final W4 call | Prediction file, DoD checklist |
| R2 Scrum Master | Retrospective: fail / improve / change | Sprint board or retro notes |
| R3 Almanac | Seasonal pattern and calendar signal | Written Almanac output file |
| R4 Macro | Macro thesis supporting the call | Macro analysis file with sources |
| R5 Technical | Chart evidence and key levels | Chart screenshots + technical file |
| R6 Data | W2 outcome vs. prediction, accuracy | Actuals vs. predictions comparison |
| R7 Human Score ⭐ | Human Score reasoning + Wild Card | Human Score file with justification |
| R8 LLM Operator | Agreement, disagreement, credibility | LLM comparison table (all 3 models, + Claude if available) |
| R9 GitHub Lead | Live repo walk-through + vW24 tag | GitHub open on screen |
| R10 Calibration | Accuracy trend + model biases | Calibration suite file |