User stories

Last modified: 2026-11-21 02:10by Erik Hagen ID: 34bd5d8b-c124-43c0-bb51-08ffd6505cf4 SAMT-X/samt-bu-pilot-6
Work in progress

The roles and actors in pilot 6, some personas, and the needs broken down into user stories in the form “As a … I want … so that …”. The user stories are the basis for prioritising what the pilot should show, and for testing the solution.

Everything on this page is a first draft. The roles are kept here until there is a common role register across the cases. They should then be moved there, and this page should link to the register (see samt-bu-architecture#38).

Roles and actors

The roles are taken from case 6, About pilot 6 and the solution concept. One actor can have several roles, and one role can be filled by several actors.

End users

RoleWhoWhat the role does in pilot 6
Parent or guardianPerson with parental responsibility for the pupilFollows the pupil’s academic progress. The most important user and the one who benefits.
PupilChild in primary or lower secondary school, under 18Sees their own information in pupil mode, and has the right to participate.
Other carerFor example foster parents, a guardian, or a parent without parental responsibilityMay need access, but does not necessarily have the right to it. Must be clarified legally.

Public actors and data holders

RoleWhoWhat the role does in pilot 6
SchoolContact teacher, subject teacher, head teacherRecords assessments and absence, and follows up the pupil together with the parents.
School ownerThe municipalityResponsible for the school, the school systems and the archive. Controller for much of the data.
Norwegian Directorate for Education and Training (Udir)National data holderHolds results from national tests and assessments.
Population RegisterThe Norwegian Tax AdministrationSource of who has parental responsibility.
Other data holdersFor example sportsPossible sources later. Outside the scope at first.

Vendors and common solutions

RoleWhoWhat the role does in pilot 6
School system vendorVendors of school administration systems (OAS)Holds much of the data and must be able to pass it on.
Channel providerKS (Min Kommune), app developers, AltinnBuilds the end-user service. Is the organisation that asks for the data.
BrokerDigdir (data.altinn.no, Altinn Events, Dialogporten)Brokers data, events and dialogues between the sources and the channels.
Rule ownerSAMT-BU, later a permanent managerManages the information model and the rulebook.

Personas

The personas are made up. They are not based on user research, and must be validated, for example through interviews with parents, as case 6 suggests. Amir is taken from the presentation of the solution concept.

PersonaRoleSituationWhat matters most
Amir, 12PupilIn year 7. Likes maths, struggles with reading.Seeing his own results, and knowing what his parents see.
Mona, Amir’s motherParentWorks full time, used to digital services, uses Min Kommune.One overview, and a notification when something new arrives.
Piotr, father of twoParentShift work, Norwegian as a second language, does not know the school system well.Understanding what the results mean, and what he can do.
Lise and ErlendParentsDivorced, the children live with both. Both have parental responsibility.That both see the same thing, without going through each other.
Nora, 15PupilIn year 10.Having more say in what is shared with her parents.

User stories

The Source column shows where the story comes from: Case 6, About pilot 6, Concept (the presentation of the solution concept) or Proposal (our own, not in the sources). Priority will be set later.

Parent or guardian

IdAs a …I want …so that …Source
F1parentto see results from national tests and assessments, evaluations and grades for my child in one placeI do not have to search several systems and put the picture together myselfCase 6
F2parentto see progress over time, also across school years and changes of schoolI understand whether my child is progressing as expectedCase 6
F3parentto see my child’s absence in the same overviewI see absence and results togetherConcept
F4parentto be notified when new results are readyI can follow up while it is relevantConcept
F5parentto log in with ID-porten and only see children I have parental responsibility forI can trust that nobody else sees my child’s dataConcept
F6parentto get the overview in a service I already use, for example Min KommuneI do not have to start using yet another serviceCase 6
F7parent who does not know the school system wellto have the results explained in plain languageI can follow up my child as well as other parentsCase 6, Proposal
F8parent with shared custodyboth parents with parental responsibility to see the same informationwe have the same basis when following up our childProposal
F9parentto see who has retrieved my child’s data, and whenI can trust that the data is not misusedAbout pilot 6
F10parentto see where each piece of information comes from, and where to report errorserrors are corrected at the sourceProposal

Pupil

IdAs a …I want …so that …Source
E1pupilto see my own results and progressI can keep track of how I am doingCase 6
E2pupilto know what my parents can see about meI know what is sharedCase 6
E3older pupilto have more say in what is shared with my parents as I get oldermy right to participate is taken seriouslyConcept, to be clarified legally

School and school owner

IdAs a …I want …so that …Source
S1contact teacherparents to have the overview before the progress meetingthe meeting can be about follow-up, not about going through resultsProposal
S2school ownerthe data to be shared from the school systems we already haveschools do not have to record the same thing in several placesProposal
S3school owneraccess to the data to follow the same rules in all channelswe meet our responsibility as controllerAbout pilot 6

Data holders and vendors

IdAs a …I want …so that …Source
D1data holder (Udir)to share the data once through data.altinn.noI do not need separate integrations with each channelConcept
D2data holderonly organisations with legal authority or consent to retrieve data, and the retrieval to be loggedI know who has received the data, and on what basisConcept
D3school system vendora common information model and API descriptionI can deliver data in the same format to everyoneAbout pilot 6
D4channel providerone API for all the sourcesI can build the service without integrating with each sourceConcept
D5channel providerto subscribe to events about new resultsI can notify parents without constantly asking for new dataConcept
D6rule ownerthe requirements for legal authority, consent, representation, data minimisation and logging to be in one rulebookall channels follow the same rulesAbout pilot 6

Next steps

  • Validate roles, personas and stories with parents, pupils and schools.
  • Prioritise the stories and link them to the user journeys in the target picture.
  • Clarify the legal questions: the role other carer, F8 and E3.
  • Consider a common role register across the cases.