[Template] Feature passport
Feature passport: omschrijving omtrent onderwerp groot of klein obv research, interne bespreking en externe toetsing.
A feature passport should be created per product level of Gelinkt Notuleren (RDFA-editor / Gelinkt Notuleren / Templates (or register). For instance if you create a feature "versioning" that is the same for GN and the editor, it needs 2 FP's (because the usecase + design will be different)
Status
Status of this feature: link to JIRA-epic or story with the status
Status of this feature passport: Not started / In progress / Finished / Outdated
Analysis
This part of the feature passport is owned by the analyst/researcher
Context
Exact product & product area we're talking about:
User & data research
If any quantitative or qualitative research was done, conclusions and insights go here.
Main insights
Insert all insights from research
Link to full user research documentation
Problems to solve for
In this feature passport, we will tackle the problems the current state of the feature has. The PO/PM/analyst/researcher do not provide with solutions. This is the task of the technical and design team.
e.g.
❌ There should be a button in the bottom-left corner so the user can send an email
✅ The user needs the ability to send emails to customer service
Requirements
This section of the FP is owned by the PM/PO
💰 Value streams
After the writer is done with this, there needs to be a Kick-off meeting where the writer talks through the expectations with the technical and design team. The team can then decide which problems are feasible to solve for this feature.
This means that if, for example, the technical team thinks that one of the problems will take a lot longer than the analyst anticipated, the PO can still decide to work on that problem as part of another feature passport (* this then needs to be amended in the Problems section and a new feature passport can be created.)
Once the team has agreed on the scope (usecases + problems to solve) we can start designing / building.
🕵️♂️ Use Cases
Personas
Usecases
Scope + future iterations
In scope
Out of scope
Future versions
🗜️ Constraints
Strategic/business constraints
Legal constraints
Technical constraints
🤔 Questions/Discussion points
This section is to capture any open questions when writing the FP. All answers should be documented in other sections of the FP.
After the writer is done with this, there needs to be a Kick-off meeting where the writer talks through the expectations with the technical and design team. The team can then decide which problems are feasible to solve for this feature.
This means that if, for example, the technical team thinks that one of the problems will take a lot longer than the analyst anticipated, the PO can still decide to work on that problem as part of another feature passport (* this then needs to be amended in the Problems section and a new feature passport can be created.)
Once the team has agreed on the scope (usecases + problems to solve) we can start designing / building.
Product solution
Design
This part of the feature passport is owned by the designer
Mock-ups
link to figma mockups
Any explanation or extra documentation
Usercases / userflows
After the designer finish their task, a technical feasibility meeting follows where the solutions are presented. The team exchanges feedback and amends the feature passport where necessary.
Technical
This part of the feature passport is owned by the technical team
[Information about the technical solutions for expectations that need it - e.g. using mu-search for showing all types of positions in one table.]
Last updated