Evidence Review: Conditions That Support Process Improvement

Research question

What should a team consider before assuming that adopting an improvement method will produce better outcomes?

Review method

This is an RDE targeted narrative desk review of published evidence, not an original study or a systematic review. Sources were searched and checked on 8 October 2026. Search terms: Serrador Pinto Does Agile work 2015 project success Magenta Book Test and Learn. Sources were selected for direct relevance, identifiable authorship, accessible methods or an official technical basis. Commercial marketing, unsourced statistics and advice presented as research were excluded. The small, purposive selection may miss relevant or conflicting studies. No pooled effect estimate was calculated and no participants or original data were collected.

Evidence and interpretation

Serrador and Pinto studied the relationship between agile approaches and project success. Their reported positive relationship concerns project delivery, not every kind of operational improvement. It cannot be treated as direct proof that a Lean Six Sigma initiative will succeed. [1] Original project-success paper.
HM Treasury's Test and Learn annex describes iterative learning, explicit assumptions and feedback, with particular value in uncertain settings. This is evaluation guidance, not a controlled study demonstrating a universal effect size. [2] Official evaluation guidance.

What this evidence cannot establish

A method name is not a causal explanation. Survey relationships can be affected by project context, reporting and selection. Guidance explains how to organise learning but does not prove that a particular local change works. The two sources address different settings and evidence types; this review does not pool them. It leaves unanswered which specific changes help your process, who benefits and whether gains persist.

RDE practical interpretation

The following activity is an RDE learning exercise, not a tested intervention or a finding reported by the cited authors. Use it to make a decision explicit and identify the evidence you would still need. Record uncertainty rather than filling gaps with an attractive explanation.

• Define one observable problem and the decision the trial must support. For example, distinguish elapsed approval time from time spent actively reviewing.
• Record a baseline using the same definition you intend to use after the change. Note sample period, missing records and unusual workload.
• Write the proposed change and the assumption connecting it to the desired outcome. Include a possible adverse effect.
• Set a review point and a stop or revise condition before trying the change. Record other changes that could explain the result.
• Compare evidence with the original assumption. Describe an encouraging local signal as a signal, not proof of a universal method.

Check your learning

Which statement above is a published finding, which is guidance, and which is an RDE interpretation? What additional evidence would change your decision? Write a short answer before applying the exercise to a real situation.

References

• [1] Serrador, P. and Pinto, J. K. (2015). Does Agile work? A quantitative analysis of agile project success. International Journal of Project Management, 33(5), 1040–1051. DOI: 10.1016/j.ijproman.2015.01.006.
• [2] HM Treasury. The Magenta Book: Test and Learn annex, HTML edition accessed 8 October 2026. Methodological guidance, not an empirical trial.

Review version 1.0. Sources checked 8 October 2026. Follow the links for full methods and context. The cover is illustrative and does not depict study participants or results.

Cover image: AI-generated illustrative scene created specifically for this resource.