EXIN VFB Functioneel Beheer Specialist study plan
EXIN VFB Functioneel Beheer Specialist · Give each week a clear focus.
8 weeks · About 7 hours per week
Functioneel beheer (onderwerpgebieden volgens Exin-programma; niet in bron vermeld) & Informatievoorziening en informatiesystemen (niet in bron vermeld)
Describe in your own words what functioneel beheer encompasses and how it differs from technisch beheer and applicatiebeheer
Map the core functioneel-beheer activities (requirements, acceptance, change, information provision, user support) to concrete tasks in a fictional organisation
Explain the difference between data, information, and information provision using one worked example from a case organisation
Build a personal glossary of at least 25 Dutch/English functioneel-beheer terms with your own definitions
Your checkpoint
A one-page mind map of the functioneel-beheer field plus a 25-term glossary, both self-checked against the Exin programme topics
Informatievoorziening en informatiesystemen (niet in bron vermeld) & Beheerprocessen en -modellen (niet in bron vermeld)
Classify information systems into types (transactional, management, decision-support, collaboration) and give a business example for each
Trace one business process end to end and identify which information systems support each step
Explain the purpose of an information plan (informatieplan) and list its main components
Distinguish structured from unstructured data and describe where each lives in a typical organisation
Your checkpoint
A process-and-system diagram of one end-to-end business process, annotated with system types and data flows
Beheerprocessen en -modellen (niet in bron vermeld) & Functioneel beheer (onderwerpgebieden volgens Exin-programma; niet in bron vermeld)
Compare at least four reference models or frameworks (e.g. ITIL-style service management, ASL/BiSL, DevOps, Agile/Scrum) on scope and applicability to functioneel beheer
Explain how change management, release management, and configuration management interact in a chain
Describe how a functional design and a technical design differ and who owns each
Outline a requirements lifecycle from intake to acceptance and sign-off
Your checkpoint
A comparison table of four frameworks with a reasoned recommendation for a mid-sized Dutch organisation
Beheerprocessen en -modellen (niet in bron vermeld) & Stakeholders, communicatie en organisatie (niet in bron vermeld)
Draft a change request procedure including impact analysis, prioritisation, and approval authority
Identify stakeholder groups in an information-provision change and map their interests and influence
Explain the role of a product owner or functional owner versus a supplier and an IT department
Practise writing a short functional requirement that is testable and unambiguous
Your checkpoint
A complete change-request template with a filled-in worked example, plus a stakeholder influence/interest matrix
Stakeholders, communicatie en organisatie (niet in bron vermeld) & Functioneel beheer (onderwerpgebieden volgens Exin-programma; niet in bron vermeld)
Describe how to run a requirements workshop and how to handle conflicting stakeholder wishes
Explain acceptance testing (functionele acceptatietest) and how to define acceptance criteria
Demonstrate how to communicate a defect or incident to non-technical users and to technical staff in one consistent story
Identify escalation paths and when to involve management
Your checkpoint
A written acceptance-test plan for one feature, including at least eight concrete acceptance criteria and a communication script
Informatievoorziening en informatiesystemen (niet in bron vermeld) & Stakeholders, communicatie en organisatie (niet in bron vermeld)
Explain information security and privacy basics relevant to functioneel beheer, including access management and data classification
Describe how data quality dimensions (completeness, accuracy, timeliness) are monitored and improved
Outline how reporting and management information are built from source systems
Explain the functioneel beheerder's role in audits and compliance evidence
Your checkpoint
A one-page data-quality and access-control checklist applied to a case system, with findings and proposed actions
Functioneel beheer (onderwerpgebieden volgens Exin-programma; niet in bron vermeld) & Beheerprocessen en -modellen (niet in bron vermeld)
Assemble a personal summary sheet of all four domains with the ten facts you are least sure about flagged for review
Work through at least 60 practice questions and log every error with its cause
Re-derive the change, incident, and acceptance processes from memory without notes
Explain to a non-specialist in five minutes what functioneel beheer delivers to the business
Your checkpoint
An error log of at least 20 analysed mistakes with corrected reasoning and a one-page summary sheet per domain
Functioneel beheer (onderwerpgebieden volgens Exin-programma; niet in bron vermeld) & Informatievoorziening en informatiesystemen (niet in bron vermeld) & Beheerprocessen en -modellen (niet in bron vermeld) & Stakeholders, communicatie en organisatie (niet in bron vermeld)
Review every flagged weak fact from week 7 and confirm or correct it against a reliable source
Complete two full timed mock exams under exam conditions and score them
Rehearse the exam's question style by explaining why each wrong option is wrong
Finalise a one-page pre-exam cheat sheet covering the four domains
Your checkpoint
Two scored mock exams with a written analysis of every wrong answer and a final one-page cheat sheet
Milestones
Week 2: You can explain, without notes, the difference between functioneel beheer and technisch beheer and place five system types in a real business process
Week 4: You can produce a complete change request and a stakeholder matrix for a new case within 45 minutes
Week 6: You can describe the functioneel beheerder's role in security, data quality, and reporting, and your error log shows fewer than 30% repeat mistakes
Week 8: Both timed mock exams are scored, every wrong answer is analysed, and you can state your two remaining weak areas with a concrete fix plan