Agile vs Waterfall Was Never the Real Question
A healthcare programme brought together clinical stakeholders, business owners, operations, compliance, product, design, developers, QA, architects, DevOps and external vendors — each group speaking a slightly different language. Envion’s product and delivery leadership replaced the methodology debate with a hybrid delivery model: a structured roadmap at the top, iterative development inside, and workstreams like compliance and clinical validation on their own gates — connected by one product language and clear decision ownership.
The challenge
Healthcare projects bring together people who work in completely different worlds: clinical stakeholders, business owners, operations, compliance, product, design, developers, QA, architects, DevOps, external vendors. Every group may believe they understand what the project needs. The biggest delivery problem is often not technology — it is getting all of these people to function as one system.
The methodology discussion started almost immediately: are we Agile, is this Waterfall, should we use Scrum, how long is the sprint? Useful questions — but not the first questions. In healthcare, forcing every part of a project into one methodology creates just as many problems as having no methodology at all. Some things need flexibility; others need certainty.
And the cross-functional problem is real: a developer sees "we need another field," a clinician sees "this information changes the decision," a designer sees "users aren't noticing it," compliance sees "we need evidence of who changed it," QA sees "what happens if it is empty?" All of them are right.
Decision path
The first question was: what does this project need in order to make good decisions and keep moving? The answer was a hybrid delivery model. At a high level, a structured roadmap: Discovery, Architecture, MVP, Validation, Expansion, Production. Within development, iterative operation: Plan, Build, Test, Demo, Learn, Adjust. At the same time, certain workstreams follow their own timelines — development works in sprints, compliance operates against formal review gates, DevOps works toward infrastructure milestones, clinical stakeholders validate workflows at scheduled checkpoints.
Waterfall thinking was kept where certainty is required: major regulatory constraints, contractual deliverables, external integrations with fixed specifications, infrastructure dependencies, migration windows, approved clinical workflows, security requirements, release governance. Agile was applied where learning is required: workflow details, interface usability, prioritization, user response, edge cases, operational assumptions. The job of delivery leadership is to make these streams meet at the right moment.
Envion contribution
Envion's product and business analysis functions made the machine work through four rules. One product language: requirements had to connect business problem, user need, requirement, acceptance criteria, development and QA — if those links were missing, the requirement wasn't ready. Clear ownership: every major decision had an owner — clinical correctness, business priority, architecture, UX, release readiness — because without ownership, meetings become debates that repeat indefinitely.
Stakeholders don't manage developers directly: stakeholders have access to the technical team, explain problems and participate in demos — but ten stakeholders independently sending requirements to five developers produces conflicting instructions, hidden scope, lost priorities and undocumented decisions. Product and BA functions protect the team from that chaos. And developers must understand why: a developer who understands "a nurse needs this information before deciding whether the case can continue" makes different decisions from one who only hears "build this field." Context improves implementation.
Delivery
The operating model: business and clinical stakeholders define problems, constraints and outcomes; Product + Business Analysis translates them into workflows, priorities and requirements; architecture and technical leadership validate feasibility; the cross-functional team — UX, development, QA, DevOps — builds; stakeholders review working functionality at demos; feedback adjusts requirements and priorities; the next increment begins. A controlled feedback loop, without turning development into a committee.
Ceremonies were kept only when they helped decisions: discovery workshops for uncertain workflows, planning, daily team sync for blockers, refinement, demo, retrospective, and decision sessions for issues requiring cross-functional agreement. The BA acted as the connective tissue — hearing "the medical team needs more flexibility" and turning it into scenarios, roles, permissions, rules, exceptions and acceptance criteria: buildable for developers, testable for QA, traceable for stakeholders.
Outcome and evidence
The patterns that usually break healthcare projects were addressed by design: too many decision-makers, requirements flowing from meetings directly into development, the "Agile means we don't need requirements" fallacy, Waterfall used to avoid feedback, stakeholders seeing the product too late, and technical teams excluded from discovery.
The programme ran with enough documentation and governance for the healthcare environment while development remained iterative. Clinical stakeholders saw working functionality early, the technical team understood the reasons behind requirements, and decisions were captured before they turned into conflicting development requests. Great software delivery is not a collection of teams — it is a system in which business, users and technology can make decisions together without creating chaos. That is what Product Discovery and Business Analysis are designed to create.
Evidence gate. This page publishes only what Envion's project records and client disclosure permissions support. Outcomes are added once verified against a baseline, a measurement period, and an approved source.
FAQ
Questions about this case
Facing a similar challenge?
Running a cross-functional healthcare programme? Envion designs the delivery system around the realities of the project — methodology becomes a tool, not a religion.
Discuss a Similar ChallengeKeep exploring
Similar case studies
Executive Technology Leadership
Support for high-stakes product and AI decisions
Bring senior technology leadership into the business when the roadmap is unclear, delivery is at risk, an AI initiative needs stronger ownership, or the company needs an experienced technical voice before hiring a permanent CTO.
Discuss Interim CTO SupportCore responsibilities
- Align product and technology priorities with business goals and measurable outcomes.
- Review architecture, delivery risks, data foundations, security needs, and AI readiness.
- Lead internal teams and external partners through a practical execution plan.
- Clarify team structure, ownership, decision rights, and delivery cadence.
- Support investor, board, partner, and due-diligence conversations with credible technical judgment.
New experience
Prompt-to-Page — try it right here
Describe the landing page you want, in your own words. We turn it into a finished page and email you a private link in 5–10 minutes — no briefs, no calls, $0 to see the result.
- Describe what you want to create.
- We structure, write, and compose the page.
- You receive a private link when it is ready.
Start with a sentence — the interactive builder takes it from there.
Generate My PageSafe, respectful content only. No obligation.