V Skill HF-D7.8-003 cross-sector 9 kompetenser
Defining and managing requirements
Elicits requirements from users and clients, records them testably, tracks changes and checks whether the result meets them.
Hur hrmforce mäter detta
- Bedömningsmetod
- Work sample test · rho 0.33 (SD 0.09)
- hrmforce instrument
- Work sample test, Structured interview
- Kompetens (50-ramverk)
- Problem Analysis
- Utbildningsbarhet
- high
- Prognos för efterfrågan 2026–2030
- rising
The candidate performs a representative work sample under standardised conditions.
Beteendeankare
| Nivå | Beteende på denna nivå |
|---|---|
| N1 Guided | Records user needs in the agreed format and probes until every need is concrete. works under supervision and follows instruction · routine, one variable at a time · own task |
| N3 Proficient | Elicits requirements from various stakeholders, makes them testable, prioritises together with them and manages changes traceably. sets own approach and seeks input proactively · several variables, some ambiguity · own team or process |
| N5 Leading | Determines the requirements practice in the organisation and decides which requirements prevail when interests conflict. sets the standard and the policy · strategic, under high uncertainty · organisation, value chain or profession |
N2 och N4 är medvetet inte förankrade. Bedömarna placerar dem mellan förankringarna, i enlighet med konventionen O*NET.
Grundläggande kompetenser
Dessa kompetenser ärver bedömningsvägen och beteendeankarna för detta konstrukt.
| T | Kompetens | Definition | Prognos för efterfrågan 2026–2030 |
|---|---|---|---|
| V | Writing a user story User story | Describes a need from the user perspective with role, goal and reason in one short, understandable statement. | rising |
| V | Writing acceptance criteria Acceptance criteria | Formulates testable conditions a solution must meet before it counts as done. | rising |
| V | Applying MoSCoW prioritisation MoSCoW prioritisation | Divides requirements into must, should, could and will not and discusses that split with client and team. | stable |
| V | Eliciting requirements from users Requirements elicitation | Elicits requirements through interviews, observation and workshops and translates what people say into what they need. | rising |
| V | Recording non functional requirements Non functional requirements | Records requirements for performance, availability, security, accessibility and maintainability in measurable form. | rising |
| V | Describing a use case Use case | Describes the main scenario and exceptions of an interaction between user and system step by step. | stable |
| V | Keeping requirements traceable Requirements traceability | Links every requirement to design, test and delivery so it is demonstrable that nothing was lost. | stable |
| V | Managing a backlog Backlog management | Maintains an ordered list of work, refines what comes first at the top and removes what no longer applies. | rising |
| V | Controlling changes to requirements Requirements change control | Assesses the consequences of a changed requirement for planning, cost and coherence and records the decision. | stable |