Skip to main content
CBE NEXUS · GLOBAL HIGHER EDUCATION

Chapter 15: Research Methods and Project Performance Analysis

Bachelor of Project Management · Year 4 · Comprehensive undergraduate textbook notes

Chapter overview

Comprehensive undergraduate Project Management chapter on research methods and project performance analysis, with detailed explanations, applied frameworks, case study, revision questions and print-ready notes. The chapter develops conceptual understanding, applied analytical skill and professional judgement. Students should connect the methods to project context, organisational strategy, stakeholder needs and sustainable outcomes rather than treating techniques as isolated procedures.

Learning outcomes: explain the major concepts; interpret frameworks and evidence; apply methods to realistic projects; evaluate assumptions and limitations; consider ethical and legal responsibilities; and communicate justified recommendations.

Study approach: read the sections, create a glossary, reproduce the diagram, work through the integrated application, attempt the case study and answer the assessment questions independently before reviewing the model guidance.

Chapter learning model

DefinePurposeAnalyseEvidencePlanResourcesDeliverCoordinateEvaluateOutcomesImproveLearn

This learning model links specialist techniques to a continuous cycle of accountable project decisions. Adapt the steps to the chapter's subject and the project's governance requirements.

Chapter contents

1. Purpose of research in project management2. Research problem and question formulation3. Literature review and conceptual framework4. Research philosophies and approaches5. Quantitative research design6. Qualitative research design7. Mixed-methods research8. Sampling methods and sample size9. Questionnaire and survey design10. Interviews, focus groups and observation11. Documentary and secondary data analysis12. Measurement, validity and reliability13. Descriptive statistics and data presentation14. Inferential statistics and hypothesis testing15. Qualitative coding and thematic analysis16. Project performance analysis and benchmarking17. Causal analysis and contribution18. Research ethics, privacy and data management19. Writing a research proposal and report20. Case study: evaluating a community infrastructure projectIntegrated applicationExtended case studyAssessment questions

1. Purpose of research in project management

Research supports evidence-based decisions about project design, delivery, performance and outcomes. It may explore stakeholder needs, test assumptions, compare interventions, evaluate implementation or investigate why performance differs from expectations. Research is systematic inquiry guided by a question and an appropriate method. It is not simply collecting opinions or assembling statistics. The research problem should be relevant, feasible and ethically acceptable. Students should distinguish academic research, routine monitoring, audit and evaluation because they have different purposes and standards of evidence.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

2. Research problem and question formulation

A research problem identifies a gap, uncertainty or practical challenge that warrants investigation. A good question is clear, focused, answerable with available methods and significant to a defined audience. Questions may be descriptive, exploratory, explanatory, evaluative or predictive. Avoid questions that are too broad, contain hidden assumptions or imply a preferred answer. Define the project context, population, key concepts and time period. A well-framed question guides the literature review, design, sampling, data collection and analysis.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

3. Literature review and conceptual framework

A literature review critically synthesises relevant theory, prior findings, methods and debates. Search systematically using appropriate academic databases, keywords and inclusion criteria. Assess authority, relevance, currency, methods and limitations rather than relying on the first search result. A conceptual framework explains relationships among key concepts and guides what evidence is collected. Distinguish established findings from hypotheses and identify where evidence is mixed. Cite sources accurately and avoid plagiarism or misrepresenting another author's conclusions.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

4. Research philosophies and approaches

Research philosophy concerns assumptions about knowledge and reality. Positivist approaches often emphasise measurement and testing; interpretive approaches examine meaning and context; pragmatic approaches select methods according to the research problem. Deductive reasoning tests ideas derived from theory, while inductive reasoning develops patterns or explanations from observations. These are broad traditions, not rigid boxes. Students should explain why their assumptions fit the question and recognise how researcher position, context and values can influence interpretation.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

5. Quantitative research design

Quantitative research uses numerical data to describe patterns, estimate relationships or test hypotheses. Designs may be descriptive surveys, correlational studies, experiments or quasi-experiments. Define variables, population, sample, measurement instruments and analysis plan before collecting data. Consider confounding factors, missing data and measurement error. Statistical association does not automatically establish causation. The design must match the question and the practical constraints of a project environment, including access, time, ethics and the ability to compare groups.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

6. Qualitative research design

Qualitative research explores experiences, meanings, processes and context through methods such as interviews, focus groups, observation and document analysis. Sampling is often purposive to include people with relevant experience. Develop an interview guide aligned to the research question, pilot it and use neutral prompts. Record field notes and maintain a clear audit trail. Analysis may involve coding, theme development and comparison across cases. Researchers should reflect on their role and avoid treating a small purposive sample as statistically representative.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

7. Mixed-methods research

Mixed-methods research integrates quantitative and qualitative evidence to address a question more fully. A sequential design may use interviews to develop a survey or use qualitative follow-up to explain numerical findings. A convergent design collects both forms in a similar period and compares results. Integration must be planned; simply placing a survey and interviews in the same report does not create mixed methods. Explain where findings agree, differ or provide complementary insight. Differences may reveal measurement problems or meaningful variation between groups.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

8. Sampling methods and sample size

Probability sampling gives eligible population members a known chance of selection and can support statistical inference when properly designed. Non-probability methods include purposive, convenience, quota and snowball sampling. Sample size depends on the question, variability, effect size, desired precision, analysis and resources. Qualitative sample adequacy is judged through relevance, depth and information power rather than a universal numerical rule. Explain inclusion and exclusion criteria, recruitment procedures and likely sources of bias.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

9. Questionnaire and survey design

A questionnaire should use clear, neutral and accessible questions that measure defined concepts. Avoid double-barrelled wording, leading assumptions, ambiguous time frames and unnecessary personal data. Choose response options that are mutually exclusive and sufficiently comprehensive. Pilot the instrument with people similar to the intended respondents and revise confusing items. Consider language, accessibility, device compatibility and response burden. Report the sampling method, response rate and limitations; a large number of responses does not automatically eliminate selection bias.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

10. Interviews, focus groups and observation

Interviews allow detailed exploration of individual experience; focus groups reveal interaction and shared or differing views; observation captures behaviour in context. Select the method according to the question and sensitivity. Obtain informed consent, explain recording and confidentiality, and protect participants from harm. Use a consistent guide while allowing relevant follow-up. In focus groups, researchers cannot guarantee that participants will keep other people's comments confidential. Observation may alter behaviour, so document the setting and researcher role.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

11. Documentary and secondary data analysis

Secondary data include project reports, financial records, schedules, audit findings, administrative datasets and published research. Before use, assess provenance, purpose, definitions, completeness, access rights and potential bias. Data created for management may not be suitable for a different research question without adjustment. Check version history and missing records. Documentary analysis can reveal decisions and formal processes but may not show informal practice. Combine sources where possible and explain discrepancies rather than choosing the most convenient record.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

12. Measurement, validity and reliability

Validity concerns whether a measure represents the concept it is intended to measure. Reliability concerns consistency under appropriate repeated conditions. A satisfaction score may be reliable but fail to capture service accessibility or actual outcomes. Use established instruments where suitable and explain adaptations. Consider content, construct and criterion validity. Pilot measures, document scoring and examine missingness. Do not confuse a precise numerical result with a valid measure of the phenomenon.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

13. Descriptive statistics and data presentation

Descriptive statistics summarise data using frequencies, percentages, mean, median, mode, range and standard deviation. The mean can be influenced by extreme values, while the median may better represent skewed distributions. Select charts that suit the data: bar charts for categories, histograms for distributions and line charts for change over time. Label axes, units, sample size and source. Avoid misleading scales and unnecessary visual effects. Describe what the data show before explaining why a pattern may have occurred.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

14. Inferential statistics and hypothesis testing

Inferential statistics use sample data to estimate population characteristics or assess hypotheses. Confidence intervals communicate a range of plausible values under model assumptions. P-values describe compatibility of data with a specified null model; they are not the probability that a hypothesis is true. Statistical significance does not necessarily imply practical importance. Consider effect size, uncertainty, multiple comparisons, sampling design and assumptions. Report methods transparently and avoid selecting only favourable analyses after seeing the results.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

15. Qualitative coding and thematic analysis

Qualitative analysis may begin with familiarisation, initial coding, grouping codes, developing themes, reviewing patterns and writing an evidence-based interpretation. Codes should capture meaningful features of the data and may be inductive or guided by a framework. Keep links to original excerpts and document analytic decisions. Consider contradictory cases rather than forcing all accounts into one story. Use quotations sparingly and protect identities. A theme is an interpretive pattern, not simply a frequently repeated word.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

16. Project performance analysis and benchmarking

Performance analysis compares actual delivery with baselines, targets, historical results or external benchmarks. Benchmarking requires comparable definitions, context and data quality. Differences may reflect scope, geography, regulation, maturity or resource conditions rather than superior management. Analyse time, cost, quality, risk, productivity, stakeholder experience and benefits together. Use variance analysis to identify causes and consequences. Avoid ranking projects without explaining whether their objectives and conditions are comparable.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

17. Causal analysis and contribution

Understanding why an outcome occurred requires more than observing that two variables moved together. Consider causal pathways, timing, alternative explanations, confounders and implementation evidence. Contribution analysis examines whether the intervention plausibly contributed to observed change alongside other influences. Experimental or quasi-experimental designs may support stronger causal claims when assumptions are met, but are not always feasible or ethical. State the strength of inference honestly. A useful evaluation explains mechanisms and context, not just a final score.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

18. Research ethics, privacy and data management

Research ethics includes voluntary informed consent, minimising harm, fair participant selection, confidentiality, privacy, secure storage and responsible reporting. Obtain institutional or regulatory approval where required before recruitment. Explain withdrawal rights and limits to confidentiality. Collect only necessary data, control access and define retention and deletion. Extra care is needed with children, vulnerable groups, employees and power relationships. Do not assume that removing names makes a dataset anonymous if people can still be identified indirectly.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

19. Writing a research proposal and report

A proposal typically includes title, background, problem statement, aim, objectives, questions, literature review, conceptual framework, methodology, ethics, limitations, timeline and references. A report presents methods, findings, interpretation, conclusions and recommendations in a logical sequence. Separate results from interpretation and connect each conclusion to evidence. Recommendations should identify an action, rationale, owner or responsible group and relevant conditions. Use a consistent citation style required by the institution and verify every reference.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

20. Case study: evaluating a community infrastructure project

A local authority wants to know whether a completed market facility improved trader livelihoods and public access. Students should formulate evaluation questions, identify stakeholder groups, select a mixed-methods design and define indicators. Consider baseline availability, seasonal variation, changes in nearby markets, safety, accessibility and distribution of benefits. Develop an ethical data plan and explain sampling limitations. Analyse financial and service data alongside trader and user experiences. Conclude with proportionate claims about contribution and recommendations for future investment.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

Integrated worked application

Consider a regional organisation implementing a service improvement across several sites. The sponsor has approved a strategic outcome, but the delivery team must translate it into an achievable plan. Begin with the intended user and organisational outcomes, then define the scope, constraints, assumptions and acceptance evidence. Map the stakeholders and identify who can approve decisions. Break the work into manageable packages, estimate the resources and sequence dependencies. Establish a baseline and a proportionate set of indicators. During implementation, compare actual evidence with the plan, investigate material differences and decide whether corrective action or formal change approval is required.

Suppose a new requirement emerges after a pilot reveals that a group of users cannot access the service through the intended channel. Do not treat this only as a technical defect. Analyse the requirement, accessibility implications, affected users, cost and schedule consequences, data and security considerations, operational support and expected benefits. Develop options such as adapting the interface, adding assisted access or revising rollout sequence. Evaluate each option against user outcomes, compliance, affordability and delivery risk. Present a recommendation with assumptions and an explicit decision request.

After approval, update the relevant plans and communicate the change to delivery and operational teams. Test the revised solution with representative users and collect evidence against acceptance criteria. At transition, confirm training, support, ownership, documentation and unresolved issues. Later, evaluate whether the service is used and whether the intended outcome has improved. This sequence demonstrates integration: project success is not a collection of separate documents but a coherent chain from need to sustainable benefit.

Extended case study: multi-site public service transformation

A public organisation intends to modernise a service delivered through twelve regional offices. The current process relies on paper records, repeated data entry and manual approvals. Users report long waiting times and inconsistent decisions. The proposed project introduces a shared digital platform, revised operating procedures and staff development. The organisation has a fixed funding envelope, varied internet connectivity, limited internal technical capacity and a target launch period. Some stakeholders support rapid implementation; others are concerned about privacy, job changes, accessibility and disruption.

Prepare a structured project response. Define the intended outcomes and measurable indicators. Identify stakeholders, their interests and engagement needs. Set out scope, exclusions, assumptions and constraints. Propose a delivery approach that allows learning while maintaining necessary governance. Develop a high-level schedule, budget logic, risk responses and quality criteria. Explain procurement and supplier oversight where external services are required. Plan training, data migration, operational readiness and post-launch support. Include an evaluation design that can distinguish outputs from outcomes and consider whether observed changes are plausibly connected to the intervention.

During implementation, the pilot identifies data inconsistencies and a connectivity gap in three offices. The supplier requests a variation and the sponsor asks whether the launch date can be retained. Analyse the decision using evidence rather than preference. Consider a phased release, additional validation, offline capability, targeted support or a revised timetable. Identify approval authority, impact on cost and benefits, and how users will be informed. State what evidence would justify proceeding, pausing or changing the plan. Your response should demonstrate professional judgement, ethical awareness and a clear audit trail.

University assessment questions and model answer guidance

1. Explain the principal concepts and purpose addressed in this chapter.

Model answer guide: Define the key terms accurately, explain their relationship to project objectives and distinguish them from related concepts. Use a relevant example and show why the concepts matter to project decisions.

2. Compare two approaches or frameworks relevant to the chapter.

Model answer guide: Identify the purpose and assumptions of each approach, compare their strengths and limitations, and explain which project conditions would make each more suitable. Avoid claiming that one method is universally superior.

3. Apply the chapter's methods to a project experiencing a major challenge.

Model answer guide: Define the problem, establish the evidence, identify affected stakeholders, develop feasible options, assess impacts on scope, time, cost, quality, risk and benefits, recommend an action and specify how it will be monitored.

4. Evaluate the ethical, legal and sustainability implications of a project decision.

Model answer guide: Identify relevant duties and affected groups, assess possible harm and distribution of benefits, explain applicable controls and show how transparency, participation and monitoring can improve the decision.

5. Discuss how performance should be measured and reported.

Model answer guide: Select indicators aligned to outcomes, define sources and frequency, explain thresholds and limitations, and distinguish activity, output, outcome and impact measures. Recommend a reporting format suited to decision-makers.

6. Explain how lessons learned should influence future projects.

Model answer guide: Use evidence to identify causes and context, distinguish effective practice from isolated success, formulate actionable recommendations and assign responsibility for embedding improvements.

7. Prepare a concise recommendation for a project sponsor.

Model answer guide: State the decision required, preferred option, evidence, assumptions, costs, benefits, main risks, alternatives, approvals, implementation responsibilities and review triggers.

8. Essay: project success requires integration of technical delivery and organisational change. Discuss.

Model answer guide: Explain the role of outputs and technical controls, then analyse user adoption, governance, operational readiness, benefits, ethics and sustainability. Support the argument with examples and a balanced conclusion.

Revision checklist and independent study

For deeper study, consult current academic texts, peer-reviewed research, recognised professional standards, institutional library resources and applicable national laws or sector guidance. Confirm the edition and jurisdiction relevant to your course. Professional standards and legislation can change, and students should not treat these study notes as a substitute for official institutional or regulatory requirements.

Official Education References

Use these official organisations for curriculum guidance, examinations and further learning information.