Stakeholder Interview Guide: [Engagement or initiative name]
Guide and record for structured one-to-one or small-group interviews
with the stakeholders of a change: sponsors, process owners, users,
operators, data owners, security and compliance staff, and external
partners. It contains the interview programme, a privacy information
and agreement script, a timed interview structure, a core question bank organised by
topic, role-specific modules, probing techniques, a notes sheet, a
coding scheme for synthesis, and a coverage log. The structure follows
the Interviews technique and the Elicitation and Collaboration knowledge
area of the IIBA BABOK Guide v3; non-functional probes use the quality
characteristics of ISO/IEC 25010:2023. Where interviews involve personal
data, the privacy section refers to the transparency duties of the EU
General Data Protection Regulation (Regulation (EU) 2016/679, Article
13). This is a documentation format, not legal advice. Replace every
[bracketed] value and every row marked Example.
Document control
| Field | Value |
|---|
| Document ID | [SIG-001] |
| Engagement or initiative | [Name] |
| Version | [0.1] |
| Status | [Draft / Approved for use / In progress / Closed] |
| Owner (lead interviewer) | [@lead-interviewer] |
| Solution architect | [@solution-architect] |
| Approvers/reviewers | [@engagement-lead], [@business-sponsor], [@privacy-officer] |
| Last updated | YYYY-MM-DD |
| Classification | [Confidential: contains personal data once notes are added] |
| Retention of notes | [Retention rule, for example deleted 90 days after the requirements baseline] |
| Related documents | [Stakeholder register], [Discovery workshop plan], [Current-state assessment] |
Approvals
| Role | Name | Approves | Date |
|---|
| Engagement lead | [@name] | Programme, question set | YYYY-MM-DD |
| Business sponsor | [@name] | Interviewee list and objectives | YYYY-MM-DD |
| Privacy officer or data protection officer | [@name] | Information and agreement script, legal basis, recording and retention | YYYY-MM-DD |
Revision history
| Version | Date | Author | Change summary |
|---|
| 0.1 | YYYY-MM-DD | [@name] | First draft |
| 0.2 | YYYY-MM-DD | [@name] | Example: Added IT operations module after pilot interviews |
| 1.0 | YYYY-MM-DD | [@name] | Example: Approved for use; information and agreement script reviewed by privacy officer |
Contents
1. Purpose and interview programme
1.1 Objectives
| Objective ID | What the interviews must establish | Used for |
|---|
| IO-01 (Example) | Business goals and success measures as each senior stakeholder sees them | Business case, solution principles |
| IO-02 (Example) | How the current process actually runs, where it fails and what it costs | Current-state assessment, pain point list |
| IO-03 (Example) | Constraints and non-negotiables: regulation, contracts, timing, budget | Scope and options analysis |
| IO-04 (Example) | Quality expectations: availability, response times, security, accessibility | Quality attribute scenarios |
| IO-05 (Example) | Readiness for change and likely resistance | Change and communication plans |
| [IO-NN] | [Objective] | [Used for] |
1.2 Interviewee selection
Select interviewees so that every stakeholder group with a stake in the
outcome is heard at least once, and every critical process is described
by at least two people (one who manages it and one who does it).
| Stakeholder group | Why they matter | Planned interviews | Selection rule |
|---|
| Executive sponsors (Example) | Set goals and funding | 3 | All sponsors |
| Process owners (Example) | Decide how processes work | 6 | One per in-scope process |
| End users and practitioners (Example) | Know how work is really done | 10 | Two per critical process (5 of the 6 in-scope processes), mix of sites and seniority |
| IT operations and support (Example) | Run current systems and incidents | 3 | Service owners of in-scope systems |
| Data owners and analysts (Example) | Know data meaning and quality | 2 | Owners of master data domains |
| Security, risk and compliance (Example) | Know obligations and controls | 2 | Information security and compliance leads |
| External partners or customers (Example) | Experience the process from outside | 3 | Largest partners by volume |
| [Group] | [Reason] | [Number] | [Rule] |
1.3 Programme plan
| Item | Plan |
|---|
| Interview window | YYYY-MM-DD to YYYY-MM-DD |
| Interviewers | [@lead-interviewer], [@second-interviewer] (note taker) |
| Format | [In person / Video / Mixed] |
| Standard duration | [60 minutes; 30 minutes for executives] |
| Interim synthesis | [After every 5 interviews] |
| Final synthesis due | YYYY-MM-DD |
2. Privacy, consent and recording
Interview notes and recordings that identify people are personal data in
most jurisdictions. Where the GDPR applies, the organisation collecting
the data must tell interviewees, at the time of collection, at least who
is collecting it, why, on what legal basis, who will receive it, how long
it will be kept and what rights they have (Article 13); collect only what
is needed for the purpose (Article 5(1)(c), data minimisation) and keep
it no longer than needed (Article 5(1)(e), storage limitation). Check the
consolidated text and your local law with your privacy officer; this
section is a documentation format, not legal advice.
| Decision | Choice |
|---|
| Controller of interview data | [Organisation name and contact] |
| Purpose | Example: Understanding current processes and needs for the [initiative] |
| Legal basis (as decided by the privacy officer) | [Basis] |
| Recording | Example: Audio only, only with explicit agreement, used by the note taker to complete notes, deleted within 10 working days |
| Who sees raw notes | Example: The two interviewers and the lead business analyst |
| What is shared | Example: Anonymised themes and requirements; quotations only with permission and without names |
| Retention of raw notes | [Rule] |
| Storage location | [Engagement workspace with access control] |
| Privacy notice reference | [Link to the notice given to interviewees] |
2.1 Information and agreement script
Read or adapt at the start of each interview, after the introductions:
"Thank you for your time. We are talking to about [number] people to
understand how [process or area] works today and what you need from
[initiative]. There are no right or wrong answers, and you can skip any
question. I will take notes. [With your agreement, I would also like to
record the audio so that my notes are accurate; the recording will be
deleted by [date] and only [names] will hear it.] We will share themes
from all interviews, not who said what, and we will only quote you with
your permission. [Our privacy notice is at [link].] Is that all right
with you?"
Record the answer in the notes sheet (section 10). If the interviewee
declines recording, take notes only and do not ask again.
Agreement to take part, to be recorded or to be quoted is a courtesy and
a fairness measure; it is not necessarily the GDPR legal basis for
processing the notes. For employees, consent is rarely an appropriate
basis because of the imbalance of power between employer and employee
(see the EDPB Guidelines 05/2020 on consent), so confirm the basis
(often legitimate interests or another basis chosen by the privacy
officer) and record it in the table above before the first interview.
3. Interviewee profile
| Field | Value |
|---|
| Interview ID | [INT-NNN] |
| Name and role | [Name], [Job title] |
| Stakeholder group | [Group from section 1.2] |
| Organisation unit and site | [Unit], [Site] |
| Relationship to the initiative | [Sponsor / Owner / User / Operator / Partner] |
| Processes and systems used | [Processes], [Systems] |
| Known concerns or history | [Summary from stakeholder register or previous contact] |
| Objectives this interview serves | [IO-01, IO-02] |
| Question set selected | [Core questions and module, for example Q-GOAL-01 to 03, Q-PROC-01 to 05, module 7.2] |
| Documents to review beforehand | [Documents] |
4. Interview structure and logistics
| Part | Time in a 60-minute interview | Interviewer | Note taker |
|---|
| Opening and agreement (section 5) | 5 minutes | Leads | Records agreement to notes, recording and quotation |
| Role and context | 5 minutes | Leads | Captures role facts |
| Core questions (section 6) | 30 minutes | Leads, follows the interviewee's thread | Captures answers verbatim where possible |
| Role module (section 7) | 12 minutes | Leads | Same |
| Closing (section 9) | 8 minutes | Leads | Reads back actions |
Logistics checklist, in original wording for this template:
- Send the invitation with the purpose, duration and privacy notice at
least five working days ahead.
- Book a private room or ask the interviewee to join from a quiet place.
- Prepare the profile (section 3) and print or open the selected
questions.
- Agree roles between interviewer and note taker; the note taker does not
lead questions but may ask for clarification at the end of a topic.
- Test recording equipment if recording was agreed.
- Leave 15 minutes after each interview to complete notes while memory is
fresh.
5. Opening script
- Introduce yourselves and your roles in one or two sentences each.
- State the purpose and how long the interview will take.
- Explain why this person was chosen ("You run the credit process in
North region, so you know where it works and where it does not").
- Read the information and agreement script (section 2.1) and record
the answer.
- Say what will happen with the results and when they will see them.
- Ask an easy opening question: "Could you describe your role and a
typical week?"
6. Core question bank
6.1 Business goals and outcomes
| ID | Question | Probe |
|---|
| Q-GOAL-01 | What would make this initiative a success for you, a year after it goes live? | How would you measure that? |
| Q-GOAL-02 | Which business results are you accountable for that this area affects? | Which of them is under most pressure now? |
| Q-GOAL-03 | What happens if nothing changes? | Who notices first, and when? |
| Q-GOAL-04 | Which outcomes matter most if we cannot deliver everything at once? | What would you give up first? |
6.2 Current process and pain
| ID | Question | Probe |
|---|
| Q-PROC-01 | Walk me through the last time you handled [a typical case], from start to finish. | What did you do next? Who else was involved? |
| Q-PROC-02 | Where does work wait, and for whom? | How long does it usually wait? |
| Q-PROC-03 | Tell me about the last time something went wrong. | What did it cost in time or money? How often does it happen? |
| Q-PROC-04 | Which steps do you do outside the system, for example in spreadsheets or email? | Why there and not in the system? |
| Q-PROC-05 | Which exceptions or special cases take the most effort? | How many per week or month? |
| Q-PROC-06 | What workarounds have you invented that others rely on? | What would break if you stopped? |
6.3 Data and information
| ID | Question | Probe |
|---|
| Q-DATA-01 | Which information do you need to do this work, and where do you get it? | How do you know it is correct? |
| Q-DATA-02 | Which data do you create or change that others use? | Who uses it, and what do they do with it? |
| Q-DATA-03 | Where do you see the same data held differently in two places? | Which one do you trust? |
| Q-DATA-04 | Which reports or numbers do you rely on for decisions? | How late or wrong are they at times? |
| Q-DATA-05 | Does this work involve personal, financial or otherwise sensitive data? | Who is allowed to see it? |
6.4 Systems and integrations
| ID | Question | Probe |
|---|
| Q-SYS-01 | Which systems do you use for this work, and for which steps? | Which one could you not work without? |
| Q-SYS-02 | Where do you copy information from one system to another by hand? | How often and how much? |
| Q-SYS-03 | Which systems are slow, unavailable or hard to use, and when? | What do you do when that happens? |
| Q-SYS-04 | Which external parties exchange information with you, and how? | Files, portals, email, interfaces? |
6.5 Quality expectations (non-functional probes)
The probes follow the product quality characteristics of ISO/IEC
25010:2023. Ask only those relevant to the interviewee, and always ask
for a concrete situation and a number.
| ID | Characteristic | Question |
|---|
| Q-NFR-01 | Performance efficiency | How quickly must [the key screen or step] respond for you to work without frustration? What happens at month-end or peak? |
| Q-NFR-02 | Reliability | If the system were unavailable for an hour on a working day, what would happen? For a day? |
| Q-NFR-03 | Security | Who must never see or change this information? Have there been incidents or audit findings? |
| Q-NFR-04 | Interaction capability | Who uses this with limited training, on mobile, or with accessibility needs? |
| Q-NFR-05 | Compatibility | Which other systems or devices must this work with? |
| Q-NFR-06 | Maintainability | How often do rules, prices or forms change, who changes them today, and how long does a change take? |
| Q-NFR-07 | Safety (where relevant) | Could an error here harm people, property or the environment? |
| Q-NFR-08 | Functional suitability | Which results must be exactly right, and how do you check them now? |
| Q-NFR-09 | Flexibility | Which changes will come in the next two years: new sites, volumes, channels or products? |
Turn every answer into a measurable scenario later, in Quality Attributes
(requirements/quality-attributes) or the NFR Catalogue
(requirements/nfr-catalogue).
6.6 Constraints, risks and change readiness
| ID | Question | Probe |
|---|
| Q-CON-01 | Which rules, regulations or contracts limit how this work can be done? | Where are they written down? |
| Q-CON-02 | Which dates cannot move, and why? | What depends on them? |
| Q-CON-03 | What has been tried before to fix this, and what happened? | Why did it stop? |
| Q-CON-04 | Who will find this change hardest, and why? | What would help them? |
| Q-CON-05 | What worries you most about this initiative? | What would reduce that worry? |
6.7 Success measures and priorities
| ID | Question | Probe |
|---|
| Q-MEAS-01 | Which number would you look at to know things have improved? | What is it today? |
| Q-MEAS-02 | If you could change one thing about how this works, what would it be? | Why that one? |
| Q-MEAS-03 | Who else should we talk to? | What will they tell us that you cannot? |
7. Role-specific modules
7.1 Executive sponsor
| ID | Question |
|---|
| Q-EXE-01 | Which strategic goals does this initiative serve, and how does it rank against your other priorities? |
| Q-EXE-02 | What budget and timeline are you prepared to commit, and what would make you stop it? |
| Q-EXE-03 | Which decisions do you want to take yourself, and which do you delegate? |
| Q-EXE-04 | How will you judge the solution team at the first steering meeting? |
7.2 Process owner
| ID | Question |
|---|
| Q-OWN-01 | Which policies and rules govern this process, and which of them are you willing to change? |
| Q-OWN-02 | How do the sites or regions differ, and which differences are justified? |
| Q-OWN-03 | Which measures do you report on for this process today? |
| Q-OWN-04 | Who must approve a change to how this process works? |
7.3 End user or practitioner
| ID | Question |
|---|
| Q-USR-01 | Show me, on your screen if possible, how you handle a typical case. |
| Q-USR-02 | Which part of your day is wasted, and on what? |
| Q-USR-03 | What do new colleagues struggle with when they learn this work? |
| Q-USR-04 | What must the new way of working keep, because it works well today? |
7.4 IT operations and support
| ID | Question |
|---|
| Q-OPS-01 | Which incidents and problems recur for these systems, and what causes them? |
| Q-OPS-02 | How are these systems monitored, backed up, patched and released today? |
| Q-OPS-03 | What are the support hours, escalation paths and contractual service levels? |
| Q-OPS-04 | Which components are end of life or depend on one person's knowledge? |
7.5 Security, risk and compliance
| ID | Question |
|---|
| Q-SEC-01 | Which regulations, standards and internal policies apply to this area? |
| Q-SEC-02 | What open audit findings or risk acceptances relate to these processes or systems? |
| Q-SEC-03 | How is access granted, reviewed and removed today? |
| Q-SEC-04 | Where must data be stored and processed, and who may access it from where? |
7.6 Data owner or analyst
| ID | Question |
|---|
| Q-DOW-01 | Which data do you own, and which definitions are disputed? |
| Q-DOW-02 | How is data quality measured, and what are the known problems? |
| Q-DOW-03 | How much history must be kept and migrated, and why? |
7.7 Finance and procurement
| ID | Question |
|---|
| Q-FIN-01 | What does the current solution cost to run, including licences, contracts and staff? |
| Q-FIN-02 | Which contracts renew or expire in the next three years, and with what notice periods? |
| Q-FIN-03 | How are capital and operating costs approved for this initiative? |
7.8 External partner or customer
| ID | Question |
|---|
| Q-EXT-01 | How do you exchange information with us today, and what goes wrong? |
| Q-EXT-02 | What would make working with us easier? |
| Q-EXT-03 | Which changes on our side would cost you effort, and how much notice do you need? |
8. Probing and questioning techniques
| Technique | How to use it | Example |
|---|
| Ask about a specific past event | Anchor on the last real case instead of "usually" | "Tell me about the last order that got stuck." |
| Follow the thread | Let the interviewee's answer decide the next question, then return to the plan | "You mentioned the spreadsheet. Who else uses it?" |
| Ask for numbers and ranges | Turn "often" and "slow" into frequencies and durations | "Roughly how many times a week? Is it closer to 5 or 50?" |
| Ask why, carefully | Ask "what makes that necessary?" rather than a blunt "why?" to find the underlying need | "What makes the second approval necessary?" |
| Ask for a demonstration | Ask to see the screen, form or spreadsheet | "Could you show me where you check that?" |
| Summarise and confirm | Restate the answer in your words and ask whether it is right | "So the hold is released only after a phone call. Is that correct?" |
| Use silence | Pause after an answer; people often add the most useful detail | Count to five before the next question |
| Separate need from solution | When a feature is requested, ask what problem it solves | "If you had that button, what would it let you do?" |
- Leading questions ("Wouldn't it be better if the system did X?").
- Double questions (two questions in one sentence).
- Jargon and internal project names the interviewee does not use.
- Promising features or dates.
- Arguing with the interviewee's view; record it and test it later.
9. Closing script
- "Is there anything important that I have not asked about?"
- "Who else should we talk to, and is there a document or report we
should see?"
- Read back any follow-up actions with owners and dates.
- Confirm whether quotations may be used, and in what form.
- Explain when and how they will see the synthesis, and thank them.
10. Notes sheet
| Field | Value |
|---|
| Interview ID | [INT-NNN] |
| Date, time and format | YYYY-MM-DD, [hh:mm], [In person / Video] |
| Interviewee | [Name or code], [Role] |
| Interviewer and note taker | [@names] |
| Agreement to notes, recording, quotation | [Notes yes; recording yes or no; quotation yes, no or anonymous only] |
| Objectives covered | [IO-01, IO-02] |
| Question ID | Answer (facts, numbers, quotations in quotation marks) | Interpretation (interviewer) | Codes |
|---|
| Q-PROC-01 (Example) | Last stuck order on Tuesday: credit hold, controller on leave, released after 2 days by phone from the sales manager | Single point of failure in credit release | PAIN, PROC-CREDIT, ROLE-DEPENDENCY |
| Q-PROC-04 (Example) | "Every hold goes into my spreadsheet, because the system does not let me add a reason." About 15 per week | Audit trail gap; candidate requirement | PAIN, COMPLIANCE, REQ-CANDIDATE |
| Q-NFR-02 (Example) | If the order system is down for an hour at month-end, about 200 orders are delayed to the next day | Month-end availability matters more than average availability | NFR-RELIABILITY |
| [Q-ID] | [Answer] | [Interpretation] | [Codes] |
| Follow-up | Owner | Due |
|---|
| Example: Send copy of the credit hold spreadsheet with personal data removed | Interviewee | YYYY-MM-DD |
| [Follow-up] | [Owner] | YYYY-MM-DD |
11. Coding and synthesis
11.1 Code book
| Code | Meaning | Example |
|---|
| GOAL | A stated business goal or success measure | Reduce order lead time |
| PAIN | A problem in the current process, with its effect | Orders wait for credit release |
| PROC-[name] | Relates to a named process | PROC-CREDIT |
| DATA | Data quality, ownership or availability issue | Duplicate customer records |
| SYS | System capability, usability or reliability issue | Slow pricing screen |
| NFR-[characteristic] | Quality expectation, by ISO/IEC 25010:2023 characteristic | NFR-RELIABILITY |
| CONSTRAINT | Regulation, contract, date or budget limit | Tax rule effective from a fixed date |
| COMPLIANCE | Audit, control or regulatory need | Missing approval evidence |
| REQ-CANDIDATE | A statement that may become a requirement | Record the reason for each hold release |
| CHANGE-RISK | Concern about adoption or resistance | Fear of losing local control |
| CONFLICT | Disagreement with another stakeholder's view | Central versus local credit decisions |
| [Code] | [Meaning] | [Example] |
11.2 Theme summary
Counts use the number of interviews held at the time of synthesis as the
denominator. Example: 23 of the 29 planned interviews held (section
13.2).
| Theme ID | Theme | Interviews mentioning it | Groups | Strength | Representative evidence | Leads to |
|---|
| TH-01 (Example) | Credit holds create delays and lack an audit trail | 13 of 23 | Users, process owners, compliance | Strong | INT-003, INT-007, INT-011 | Requirement candidate, current-state finding |
| TH-02 (Example) | Customer prices are kept in several places | 8 of 23 | Users, finance | Moderate | INT-002, INT-009 | Data finding, workshop topic |
| TH-03 (Example) | Regions disagree on central credit control | 5 of 23 | Process owners, executives | Conflict | INT-001, INT-005 | Decision for sponsor |
| [TH-NN] | [Theme] | [Count] | [Groups] | [Strong / Moderate / Weak / Conflict] | [INT-] | [Destination] |
Define the strength scale before synthesis, for example Strong when more
than half of the interviews in two or more groups mention the theme, and
report counts so that readers can judge for themselves. Stop adding
interviews for a group when two consecutive interviews add no new theme,
and say so in the synthesis.
11.3 Outputs
| Output | Destination |
|---|
| Candidate requirements | Business Requirements Specification (requirements/business-requirements) or Stakeholder Requirements Specification (requirements/stakeholder-requirements) |
| Current-state findings | Current-State Assessment (architecture/current-state-assessment) |
| Topics needing a group decision | Discovery Workshop Plan (requirements/discovery-workshop-plan) |
| Risks and concerns | RAID Log (project/raid-log) |
| Stakeholder attitudes and engagement needs | Stakeholder Register (project/stakeholder-register) |
12. Follow-ups and validation
| ID | Item to validate | Method | Owner | Due | Result |
|---|
| VAL-001 (Example) | About 15 credit holds per week per controller | Report from the order system for the last 3 months | @business-analyst | YYYY-MM-DD | [Result] |
| VAL-002 (Example) | Month-end outage delays about 200 orders per hour | Order volume by hour at the last two month-ends | @business-analyst | YYYY-MM-DD | [Result] |
| VAL-003 (Example) | Theme TH-01 summary is accurate | Send summary to interviewees INT-003, INT-007 | @lead-interviewer | YYYY-MM-DD | [Result] |
| [VAL-NNN] | [Item] | [Document / Data / Observation / Read-back] | [@owner] | YYYY-MM-DD | [Result] |
Send each interviewee a short summary of what they said, or the theme
summary, and invite corrections within a set period. Record corrections
in the notes sheet and keep the original text.
13. Interview log and coverage
13.1 Interview log
| Interview ID | Date | Interviewee (role or code) | Group | Site | Interviewers | Notes link | Status |
|---|
| INT-001 (Example) | YYYY-MM-DD | Chief Operating Officer | Executive sponsors | Head office | @lead-interviewer | [Link] | Notes reviewed |
| INT-002 (Example) | YYYY-MM-DD | Pricing analyst | End users | Central | @lead-interviewer, @analyst | [Link] | Notes reviewed |
| INT-003 (Example) | YYYY-MM-DD | Credit controller | End users | North | @analyst | [Link] | Follow-up open |
| [INT-NNN] | YYYY-MM-DD | [Role] | [Group] | [Site] | [@names] | [Link] | [Planned / Held / Notes reviewed / Cancelled] |
13.2 Coverage matrix
| Objective | Executive sponsors | Process owners | End users | IT operations | Data owners | Security and compliance | External partners |
|---|
| IO-01 Goals (Example) | 3 of 3 | 4 of 6 | | | | | |
| IO-02 Current process (Example) | | 5 of 6 | 7 of 10 | 2 of 3 | | | 1 of 3 |
| IO-03 Constraints (Example) | 2 of 3 | 3 of 6 | | | | 2 of 2 | |
| IO-04 Quality (Example) | | 2 of 6 | 6 of 10 | 3 of 3 | | 2 of 2 | |
| IO-05 Change readiness (Example) | 3 of 3 | 6 of 6 | 8 of 10 | | | | |
| [IO-NN] | | | | | | | |
14. Glossary and references
14.1 Glossary
| Term | Meaning |
|---|
| Code | A short label attached to a piece of interview evidence so that it can be grouped |
| Elicitation | Drawing out information from stakeholders and other sources |
| Leading question | A question that suggests the answer the interviewer expects |
| Probe | A follow-up question that asks for detail, an example or a number |
| Saturation | The point at which further interviews in a group add no new themes |
| Theme | A pattern found across several interviews, supported by coded evidence |
14.2 References
| ID | Reference | Version or date | Use |
|---|
| REF-01 | A Guide to the Business Analysis Body of Knowledge (BABOK Guide), International Institute of Business Analysis | Version 3, 2015 | Elicitation and Collaboration knowledge area; Interviews technique (structure only) |
| REF-02 | ISO/IEC 25010:2023 Systems and software Quality Requirements and Evaluation (SQuaRE), Product quality model | Edition 2, November 2023 | Characteristic names used for non-functional probes |
| REF-03 | Regulation (EU) 2016/679 (General Data Protection Regulation), eur-lex.europa.eu | As consolidated; check the current text | Articles 5 and 13, section 2 |
| REF-04 | European Data Protection Board, Guidelines 05/2020 on consent under Regulation 2016/679, edpb.europa.eu | Version 1.1, adopted 4 May 2020 | Section 2.1, consent in the employment context |
| REF-05 | Stakeholder Register (project/stakeholder-register) | [Version] | Interviewee selection |
| REF-06 | [Internal privacy notice or research policy] | [Version] | Section 2 |
Standard and licence note
Structure aligned with the Interviews technique and the Elicitation and
Collaboration knowledge area of A Guide to the Business Analysis Body of
Knowledge (BABOK Guide) Version 3, published by the International
Institute of Business Analysis, and with the product quality
characteristics of ISO/IEC 25010:2023. Only technique, knowledge area and
characteristic names are used; no text, definitions or tables from either
source are reproduced, and the questions, scripts and examples are
original. The privacy section is based on Regulation (EU) 2016/679
(Articles 5 and 13), paraphrased in original words; it is a documentation
format, not legal advice, and you should check the consolidated text and
local law. Obtain the BABOK Guide from IIBA and the standard from ISO or
your national body for their full content. BABOK and IIBA are registered
trademarks of the International Institute of Business Analysis; this
template is not affiliated with or endorsed by it. Template licence: MIT.