Dave Prior on Agile: Change, Fit and Blended Methods
In this 27-minute conversation, Certified Scrum Trainer Dave Prior of LeadingAgile talks with Brett Harned about what agile demands in practice. Prior, a former PMP who resisted agile for years, frames adoption as organisational change first, then explores where agile fits, where it fails, and how to combine it with traditional approaches.
Episode details
Time Limit podcast • 47 episodes Episode 8, Season 2 Published 2019-04-15 Duration: 27:15 More episodes: EP. 7 • Elizabeth Harrin on Communications and Collaboration; EP. 6 • Culture with Colin D. Ellis; All episodes
Agile starts with organisational change
Many teams adopt agile for its promised benefits without first grasping the discipline and shift in how the organisation operates. Prior treats that gap as the central risk: ceremonies can be copied quickly, but the underlying change in trust, decision-making and tolerance for failure takes longer. His own path matters here — a former PMP who resisted agile for years, he argues from inside the scepticism many traditional project managers bring.
Where agile fits — and where it breaks
Use this fit check before committing a team to agile:
Fit checklist
Trust is present, so people can surface problems early Failure can be discussed as learning rather than punished Teams can work across silos instead of handing work over walls Command-and-control is not the default way decisions get made
Warning signs that agile will struggle: Siloed structures keep teams dependent on other groups for every step Command-and-control overrides team self-organisation Failure is treated as blame, so feedback and experimentation dry up Adoption is limited to copying ceremonies without changing how work is decided
Blending means filling gaps, not doing half of Scrum
A blended approach is not a partial version of one framework. Prior's distinction is practical: identify what a method leaves uncovered, then deliberately borrow practices from another method to fill that gap. Doing half of Scrum, by contrast, simply drops parts of the discipline while keeping its label. The episode also covers the rise of agile, the route to transformation and the roadblocks along the way, so listeners can judge whether blending is a considered design choice or an accidental shortcut.
A low-cost way to start
For a team without time for certification, Prior suggests starting from a concrete business problem rather than a framework rollout. Choose one small practice that moves toward fixing that problem — a daily stand-up, a visible backlog, or a personal kanban — and build from there. Pair that step with an accountability partner or coach who can hold up a mirror, because the hardest part is unlearning established habits, not learning new ones. As a worked example: a team whose problem is invisible work-in-progress could start with a personal kanban for each member, review it in a daily stand-up, and ask a coach weekly whether old handoff habits are creeping back.
Topics and further resources
The conversation covers the rise of agile, where it works well and where it breaks down, blending agile with traditional methods, the path to transformation and its roadblocks, and how to learn agile without certification. Further listening and classes from Prior are listed in the resources below.
Frequently asked questions
What does agile really require from an organisation?
Prior describes adoption as organisational change first. That means examining trust, tolerance for failure, silos and command-and-control habits before expecting ceremonies or tools alone to deliver the headline benefits.
Where does agile work well and where does it break down?
It tends to fit where trust exists and failure can be tolerated as learning. It struggles in siloed, command-and-control structures, where those conditions work against self-organisation and feedback.
What counts as a genuinely blended method?
A genuine blend uses practices from another method to cover the gaps a single method leaves. Simply doing part of Scrum is not a blend.
How can someone start practising agile without certification?
Pick a specific business problem, then take one practical step toward it — for example a daily stand-up, a backlog, or a personal kanban — and use an accountability partner or coach to challenge old habits.