Crafting Your Own Blended Process: Lessons from Suze Haworth
Consulting digital delivery lead Suze Haworth, known for telling agile conferences to 'forget agile', discusses crafting a blended process with Brett Harned. The conversation covers why strict frameworks often fail agency and fixed-budget work, how project management responsibilities shift, and how to introduce change without expecting a framework to solve every problem.
Principles before labels
A framework is a starting point, not a guarantee. Haworth's central warning is that adopting ceremonies or roles without changing underlying mindset is the most common mistake. Teams should expect to try, test and change things, treating each practice as an experiment whose fit must be checked against real delivery conditions.
Why fixed-budget work needs a blend
Contract shape influences process shape. Fixed timescales and budgets push most agency projects toward a blended approach, while time-and-materials contracts allow more pure agile. That distinction helps teams choose honestly: if dates and price are fixed, plan for upfront commitments plus iterative delivery inside them, rather than pretending the constraints do not exist.
How the PM role maps to delivery roles
Embracing Agile practices changes what a project manager does day to day. Responsibilities that sit with a Scrum master, product owner and delivery lead need to be covered explicitly, instead of assuming a single PM title covers them. Clarify who facilitates, who owns product decisions, and who owns delivery flow before adopting new ceremonies.
A practical way to start
Start with evidence, not a framework rollout. Use retrospectives to identify pain points, borrow one practice such as a daily stand-up, and map outcomes with a now/next/later roadmap. Take proposed changes to the team first, make small changes, and let team members lead some of them so change is not carried by one person.
Decision checklist for adapting process
Use this checklist before adopting a new practice: 1) Name the pain point from a retrospective. 2) State the principle you are trying to improve - customer focus, frequent delivery, or collaboration. 3) Pick one practice to test. 4) Agree who will lead it. 5) Review after a short trial and keep, adapt, or drop it. 6) Record the outcome on a now/next/later roadmap so stakeholders see what changed and why.
What the episode covers
The episode also covers what leads teams to transform process, what adapting Agile means in practice, challenges encountered when adapting process, and practical tactics for employing a new process. It runs 27:26 in the player, with structured episode data listing 27:27.
| Contract / context | Likely process fit | Practical implication |
|---|---|---|
| Fixed timescale and budget | Blended approach | Combine upfront commitments with iterative delivery inside fixed constraints |
| Time-and-materials | More pure agile possible | Greater scope for iterative discovery and delivery |
Based on episode takeaways; not a universal rule for every client.
Frequently asked questions
Why does fixed-budget agency work rarely fit a strict framework?
When dates and price are locked in, agency teams usually need a hybrid way of working; a time-and-materials arrangement gives more room to work in a fully iterative Agile way.
What should teams focus on instead of being agile?
Focus on customer first, frequent delivery and team collaboration rather than on being labelled agile. Borrow single practices, test them, and adapt them to your context.
How does the PM role change with Agile practices?
The PM role maps across Scrum master, product and delivery responsibilities when Agile practices are embraced, rather than staying only with traditional project management duties.