behovslista

Behovslista is a document used in Swedish-speaking contexts to record needs and expectations for a product, service, or system. The term combines behov (need) and lista (list). It is commonly created in the early phases of a project to ensure stakeholders’ requirements are captured and communicated across teams. A behovslista typically focuses on user needs, business objectives, and contextual constraints, rather than detailed technical specifications.

Contents and structure include functional requirements (what the system should do), non-functional requirements (quality attributes such as performance, security, accessibility), business rules, regulatory or legal considerations, constraints (budget, timeline), and acceptance criteria. It may also include rationale and source for each item and assigned owners.

Relation to other artifacts: a behovslista serves as input to more formal requirements work, such as a kravspecifikation (requirements specification) or product backlog. It is less binding and often not fully testable in its initial form, serving as a dashboard of needs that can be prioritized (e.g., MoSCoW method) and elaborated into user stories or tasks.

Creation and use: generated via workshops, interviews, observation, and analysis of user journeys. It is prioritized and refined through stakeholder review. In procurement or tendering contexts, the behovslista defines the criteria suppliers must meet.

Example: For a library app, items might include multilingual UI, accessible design, search by title/author, offline reading, secure login, data privacy compliance, and scalable hosting.