Tailoring the Delivery Phase for a Regulated Release
A pharmaceutical client requires a validated system for adverse-event reporting. Regulatory rules mean the software cannot be released incrementally to production - it must go live as a single validated release with full traceability evidence. The team has been running 3-week timeboxes with demonstrable increments to a staging environment, and stakeholders value the early feedback. The sponsor now asks whether AgilePM 'even works' for this, given the no-incremental-release constraint. A consultant suggests dropping timeboxing and reverting to a waterfall plan to 'satisfy the auditors'. The project manager is unsure whether the phased approach and timeboxing can be tailored without losing AgilePM's benefits. There are 11 timeboxes planned; timeboxes 1-6 have completed on schedule.
1. Advise the sponsor on whether AgilePM can accommodate a single validated release, and how the approach should be tailored.
Read the worked answer
Yes - AgilePM is explicitly a tailorable framework, and its principles include 'Tailor to the context'. The constraint is on deployment, not on how work is organised. AgilePM separates the delivery of increments (to a staging/demo environment) from deployment to live. A single validated production release is compatible with evolutionary development and timeboxing provided the tailoring is explicit.
Tailoring options:
- Keep timeboxing and incremental development, but define the 'increment' as a validated build delivered to the staging/validation environment for stakeholder review, not to production. Stakeholders still get early feedback - the benefit the sponsor values.
- Keep the phased approach (Foundation, Evolutionary Development/Deployment) and document the deployment phase as a single validated release with the regulatory evidence pack.
- Strengthen products for traceability: ensure the Prioritised Requirements List, requirements/design records and test evidence are maintained to the standard the auditors need. AgilePM products can be tailored in formality - the content requirement rises, not the framework changes.
- Add validation gates at timebox boundaries (e.g. formal review of increments) so evidence accrues continuously rather than being reconstructed at the end.
What not to do: drop timeboxing and revert to waterfall. That discards the working practices that have delivered 6 on-schedule timeboxes and would not, by itself, satisfy auditors better - traceability comes from disciplined products, not from a waterfall diagram.
2. Critique the consultant's proposal to revert to a waterfall plan, using evidence from the project.
Read the worked answer
The proposal is a false solution and should be rejected.
Evidence against it:
- Timeboxes 1-6 completed on schedule - the current approach is demonstrably working. Abandoning it introduces disruption and risk for no proven regulatory gain.
- Stakeholders value early feedback - waterfall defers feedback to the end, increasing the risk of late rework in a safety-critical domain where requirements are complex.
- Audit needs are about evidence, not methodology - auditors require traceability and validation evidence; these can be produced under AgilePM by tailoring product formality and adding validation gates. A waterfall plan does not automatically produce better evidence and often produces it later.
- Risk concentration: waterfall concentrates integration and validation risk at the end; timeboxing surfaces issues early.
What the consultant may be right about: the need for formal documentation and sign-off. That should be met by tailoring - e.g. more formal product descriptions, documented review records, a defined validation evidence pack - not by changing the delivery model.
Recommendation to the sponsor: retain the phased, timeboxed approach with increments to the staging environment, add validation gates at timebox boundaries, and document the tailoring rationale so it can be shown to auditors. Revisit only if a specific regulatory requirement genuinely cannot be met - and identify that requirement explicitly rather than assuming it.