Capstone Project

This guide supports students enrolled in BU404 – Capstone Project at Vector Technology Institute (VTI). It focuses on the applied decisions that make a capstone useful: defining a real problem, choosing a suitable framework, gathering evidence or data, analysing findings, making practical recommendations, and presenting or defending the project.

Scope note: This is the project-specific guide. General research mechanics belong in the Research Skills Guide, Research Process, and How to Conduct Research.

BU404 Capstone Roadmap

1. Define the project problem and scope.
2. Check feasibility.
3. Select and justify a framework or model.
4. Plan evidence and data gathering.
5. Choose the methodology or project approach.
6. Analyse findings against the question and framework.
7. Develop recommendations and implementation considerations.
8. Present and defend the project.

1. Define the Problem and Scope

A strong capstone addresses a clear organisational, technical, service, policy, or community problem rather than a broad subject. Describe what is happening, who is affected, why it matters, and what a useful improvement could look like.

• Write a concise problem statement.
• State the project aim, objectives, and research or design questions.
• Define the users, organisation, environment, or population in scope.
• Set boundaries: what the project will not cover, and what constraints apply.

Align the problem with your programme learning outcomes and the expectations of BU404.

2. Check Feasibility

Before committing to a topic, test whether the project can be completed with the time, access, skills, tools, and evidence available.

• Can you access the people, documents, systems, datasets, or case materials you need?
• Can you complete the work within the academic calendar and available resources?
• Are permissions, privacy, safety, and ethical concerns manageable?
• Can the proposed output be tested, evaluated, or defended with evidence?

If the answer is no, reduce the scope or change the approach before building the proposal.

3. Examples of Frameworks and Models for Research Analysis

Frameworks and models can help you structure an analysis, interpret evidence, compare options, evaluate performance, understand adoption or change, assess risk, design a solution, or support recommendations. Choose one because it fits your research question, evidence, and project scope.

Technology Adoption and Information Systems

• Technology Acceptance Model (TAM): Examines how perceived usefulness and ease of use influence technology acceptance.
• UTAUT / UTAUT2: Examines factors such as performance expectations, effort, social influence, facilitating conditions, and user adoption.
• Diffusion of Innovations: Explores how an innovation spreads through groups or organisations over time.
• Technology-Organization-Environment (TOE): Considers how technological, organisational, and external environmental factors shape adoption.
• DeLone & McLean Information Systems Success Model: Links system quality, information quality, use, user satisfaction, and resulting benefits.
• Systems Development Life Cycle (SDLC): Structures the planning, analysis, design, development, testing, deployment, and maintenance of an information system.

Business and Strategic Analysis

• SWOT Analysis: Organises internal strengths and weaknesses alongside external opportunities and threats.
• PESTLE Analysis: Examines political, economic, social, technological, legal, and environmental influences on a project or organisation.
• Porter's Five Forces: Analyses competitive pressure and the structure of an industry or market.
• Business Model Canvas: Maps value propositions, customers, channels, activities, resources, partners, revenue, and costs.
• Balanced Scorecard: Translates strategy into objectives and measures across financial, customer, internal-process, and learning perspectives.

Change and Implementation

• People-Process-Technology (PPT): Considers how people, workflows, and technology must work together during implementation.
• ADKAR: Organises individual change around awareness, desire, knowledge, ability, and reinforcement.
• Kotter's 8-Step Change Model: Provides a staged approach for building urgency, alignment, action, and sustained change.
• McKinsey 7S: Assesses alignment among strategy, structure, systems, shared values, style, staff, and skills.

Process and Quality Improvement

• PDCA / Deming Cycle: Uses plan, do, check, and act to support iterative improvement.
• DMAIC: Defines, measures, analyses, improves, and controls a process or quality problem.
• Lean / Lean Startup: Helps identify waste or test assumptions through small experiments where that approach suits the project.

Cybersecurity and IT Governance

• NIST Cybersecurity Framework: Organises cybersecurity activities around identify, protect, detect, respond, and recover.
• COBIT: Supports governance, management, control, and alignment of enterprise IT.
• ITIL 4: Provides service-management practices for creating, delivering, and improving IT-enabled services.
• CIA Triad: Frames security objectives around confidentiality, integrity, and availability.
• Zero Trust principles: Emphasise continuous verification, least privilege, and explicit trust decisions.
• OWASP guidance and frameworks: Supports secure application design, testing, and web-application risk analysis where appropriate.

Design, Innovation, and Evaluation

• Design Thinking: Uses an iterative, user-centred approach to understand needs, generate ideas, prototype, and test solutions.
• Logic Model: Connects inputs and activities to outputs, outcomes, and intended impact.
• Input-Process-Output (IPO) Model: Maps what enters a system, how it is transformed, and what it produces.
• Risk Matrix / Risk Assessment Framework: Compares risks by likelihood and impact to support prioritisation and response.

How to Choose

• What problem or question are you analysing?
• What evidence or data do you have, and what are its limits?
• What will the model help you explain, compare, design, measure, or evaluate?
• Is it recognised and appropriate in your discipline or project context?
• Can you justify the choice clearly in your methodology and analysis?

A project may use one primary framework and, when there is a clear reason, one supporting model. Avoid stacking multiple frameworks simply to make the project appear more complex; each one should have a distinct purpose and be used consistently.

For technology, cybersecurity, and IT governance options, consult the IT Standards & Frameworks Guide and the relevant VTI programme guide.

4. Plan Evidence and Data Gathering

Use evidence that can support both the problem definition and the proposed solution. A capstone may combine scholarly research, industry reports, standards, organisational records, interviews, surveys, observations, tests, or public datasets.

• Google Scholar, BASE, DOAJ, and OATD for scholarly examples and prior research.
• Government of Jamaica Open Data, the Planning Institute of Jamaica, and the World Bank Open Knowledge Repository for reports and public data.
• Professional standards, technical documentation, and organisational evidence when they directly fit the problem.

For general search strategy, source evaluation, and peer-reviewed source identification, use the Research Skills Guide.

5. Choose the Methodology or Project Approach

Explain how you will answer the question or assess the proposed solution. Your approach might be qualitative, quantitative, mixed methods, a case study, a design-and-build project, a system evaluation, or a structured comparison.

• Identify the data or participants, selection criteria, instruments, procedures, and measures.
• Explain how the framework informs data collection or design decisions.
• State how you will analyse results and manage limitations.
• Address consent, privacy, confidentiality, security, and responsible data handling.

Make sure the method is realistic for the scope and produces evidence that answers the stated objectives.

6. Analyse Findings

Analysis is more than reporting what you found. Connect findings to the problem, objectives, framework, and evidence from the literature.

• Organise results around the research question or project objectives.
• Use clear tables, figures, process diagrams, or comparison points when they improve understanding.
• Explain patterns, exceptions, trade-offs, and unexpected results.
• State what the evidence supports, what it cannot establish, and where limitations affect interpretation.

Use the Literature Review Guide when you need to synthesise prior research, rather than simply list sources.

7. Develop Recommendations and Implementation Considerations

Recommendations should follow from the findings and be practical for the organisation, users, or setting described in the project.

• State the action, priority, intended owner, and expected benefit.
• Consider resources, cost, timeline, training, infrastructure, policy, and risks.
• Identify dependencies and barriers to implementation.
• Suggest measures or milestones that could show whether the recommendation is working.
• Separate evidence-based recommendations from ideas that require further testing.

8. Present and Defend the Project

Your presentation should tell a clear story: problem, purpose, framework, approach, evidence, findings, recommendation, and value. Use visuals to explain systems, data, models, or comparisons rather than filling slides with paragraphs.

• Explain why the problem and method matter.
• Be ready to justify the framework, data, design decisions, and limitations.
• Show how recommendations connect to findings.
• Prepare concise answers to questions about feasibility, ethics, scope, and next steps.

BU404 Working Checklist

• Problem statement, aim, objectives, and focused question.
• Defined scope, stakeholders, assumptions, and constraints.
• Relevant literature, evidence, framework, and methodology.
• Findings linked to the question and project objectives.
• Recommendations that address feasibility and implementation.
• Clear report, complete APA references, visual presentation, and defence preparation.

Use How to Write a Research Paper for report structure and the APA Formatting & Citation (7th Edition) guide for references.

Programme-Specific Pathways

• ICT and software: Computer Science, IT and Software Engineering Guide, ASC Software Programming Guide, and IT Standards & Frameworks.
• Cybersecurity: Advanced Diploma Cybersecurity Analyst Guide and the IT Standards & Frameworks Guide.
• Technology management and business: BSc Technology Management Guide and the Business & Management Student Guide.
• All programmes: Browse the Programme Guides collection.

Which Guide Should I Use?

• Need general research mechanics? Use Research Skills, Research Process, or How to Conduct Research.
• Need to synthesise sources? Use the Literature Review Guide.
• Need report structure or citation help? Use How to Write a Research Paper and APA Formatting & Citation.

This guide supports successful completion of the BU404 Capstone Project through applied learning, evidence-based decision-making, and professional communication.