CP3405DT3 · System Intelligence Platform
Prof. Dr. Tan · TR2 '26
SPRINT W3 · SCRUM WISDOM ARCHIVE · Short reminders for Prism builders

Scrum Wisdom for Prism Builders

Short reminders for why this course uses sprints, roles, evidence, public coordination, retrospectives, and weekly prediction defence.

Core Principle

"This week, you are doing manually what your future Prism tool should eventually help automate."

Prism should emerge from the pain of the manual workflow: collecting data, comparing AI outputs, scoring evidence, locking predictions, and learning from mistakes. Every frustration this sprint is a system requirement waiting to be written.

Scrum Nuggets — Sprint W3

Principles That Apply Right Now

Scrum exposes disorder early enough to fix it.
Confusion is data. If your team feels unclear this Sunday, that is not failure — it is the Scrum framework working as designed. Act on it.
Done means evidence exists.
A claim without inspectable evidence in GitHub, Discord, or FigJam is not done. "We did it" with no artefact is not a sprint increment.
The Scrum Master does not command the team.
The Scrum Master protects flow and removes blockers. If your R2 is giving orders instead of clearing paths, the role is being misread.
The Product Owner protects value.
Activity is not enough; usefulness matters. R1 must ask: does this prediction represent our team's best thinking, or just our fastest work?
Planning Poker is a disagreement detector.
Different estimates reveal hidden assumptions. Disagreement in estimation is not conflict — it is information surfacing from different mental models.
A time box protects focus.
The Sunday midnight deadline is a time box. It is not an obstacle. It is what forces decisions and prevents infinite refinement.
A Daily Scrum should change the next 24 hours.
It is inspect-and-adapt, not a long report. Three questions: what did I do, what will I do, what is blocking me. Then act on the answers.
Retrospective is not blame.
It turns frustration into process improvement. The goal is one specific change for the next sprint, not a review of what went wrong for 30 minutes.
Self-organisation is disciplined responsibility.
No passive waiting for rescue. If you are blocked, you surface it. If a team member is silent, you reach out. The sprint does not pause.
GitHub is the team's memory.
The repo tells the sprint story. Commit history, release tags, and folder structure are your evidence trail. Empty repos are invisible teams.
FigJam is the team's thinking wall.
Empty boards mean invisible thinking. If your analysis only exists in a chat log, it cannot be inspected, audited, or built on.
The release tag is your timestamped promise.
A prediction that can be edited after the result is known is not a prediction. vW23 seals your call before the market opens Monday.
System Thinking for Scrum Teams

Beyond the Framework — Thinking Like a Platform Builder

W3
Manual work is specification.
The pain of this sprint is writing the requirements for your future automated system. Every friction point is a use case.
W3
Human Score is the irreplaceable layer.
Four AI models cannot replace R7's judgement. Wild Card insight, contrarian thinking, and news intuition are human advantages. Protect them.
W3
Calibration is your learning engine.
R10's calibration suite is not bookkeeping. It is the feedback loop that makes your team's predictions improve over time.
← Back to Sprint Instructions System Architecture →