amigos — the story card
What the story looks like in JIRA
Here is what the developer actually sees before the amigos session — the complete story card with all five sections filled:
Epic: Grade exam results and publish to the school system · STORY-05
Gal marks an open-answer response (basic — no rubric)
Person Gal — science teacher, AMIT network, nine years' experience. Same person from the Feature Brief.
Moment Wednesday afternoon, after the last bell. Gal has 28 exam submissions waiting. She has already seen the auto-computed MCQ scores (the all-students overview). She opens the first student who needs open-answer marking. She has roughly 40 minutes before she needs to leave; marking all 28 open-answer responses is the task she described as "the part that takes the longest."
What done looks like Gal marks each student's open-answer response with a numeric score, moving student-to-student without switching tabs or losing context. She can scroll back to a previously-marked student and change the score. Each score is saved the moment she moves to the next student. When she reaches student 28, she can see all scores — MCQ and open-answer — already totalled.
Out of scope (this story) Rubric-based marking (release 2). Side-by-side answer comparison. Annotation or written feedback on the response. Submission to the school system (separate story, same Epic).
Brief: Gal grading · States: per-student-marking, save-confirm · API: POST /exam-results · ADR-011
Every section is traceable. The person is from the brief. The moment is from the observation. The done condition is from the journey. The out-of-scope is from the PDR. The links connect to every upstream artifact. A developer reading this card — without having attended the kickoff, without having read the brief — can picture the situation.