Why your Scrum implementation may be failing and how Belbin® can provide the missing link.
The Context
You have invested months in an ‘Agile Transformation’. Your teams are dutifully attending daily stand-ups and your Jira boards are overflowing with user stories. You have hired expensive Scrum Masters to police the ceremonies, yet the promised ‘velocity’ is nowhere to be found. Sprint goals are missed, backlogs are bloated with half-baked ideas and burnout is rising, while tangible value delivery is flatlining.
The brutal truth is that Scrum is a framework for process, but it is silent on behaviour. At ClarusBlue Consulting, we have implemented Scrum with hundreds of teams over the last decade, and the pattern is always the same: a ‘one-size-fits-all’ process cannot fix a behaviourally imbalanced team.
If your Agile engine is stalling, it isn’t because you’re doing Scrum wrong. It’s because you’ve ignored the human chemistry required to make it work. To build a truly high-performing, anti-fragile team, you must blend the structured iterative progress of Agile with the scientifically backed behavioural insights of Belbin Team Roles.
Why Scrum Alone Isn’t Enough: The Statistical Reality
According to the 17th State of Agile Report, while 71% of organisations use Agile to accelerate software delivery, only 11% are ‘very satisfied’ with their Agile practices. The primary barriers cited are not technical; they are ‘Company Culture’ and ‘Lack of Management Support’.
Scrum provides the ‘what’ and the ‘how’, but it fails to address the ‘who’. Adherence to ceremonies does not equal productivity. At ClarusBlue, we frequently encounter teams that follow the Scrum Guide to the letter, but still suffer from critical failure points:
Isolated Product Owners: Visionaries working in a vacuum, missing out on team creativity and innovation.
The ‘Random Work’ Syndrome: Teams working on random work items because Sprint Goals lack clarity or are entirely absent, resulting in reduced motivation.
The Burnout Loop: Overambitious sprint commitments leading to sprint failure, chronic overwork, and burnout.
Stakeholder Disengagement: Teams working in silos with no stakeholders present in the Sprint Review to recognise or validate the work.
The ‘Groundhog Day’ Retrospective: Meetings that identify issues but fail to drive any kind of meaningful change or resolution.
These are not process failures; they are behavioural voids. To solve them, we can effectively apply the Belbin lens to the entire Agile lifecycle.
The Belbin-Scrum Integration: A Deep-Dive Journey
A high-performing Agile team requires a balance of nine distinct roles present in harmony. Here is how those behaviours drive the Scrum machine through every phase:
1. Setting the North Star: The Sprint Goal
The sprint process starts with setting a Sprint Goal. This shouldn't be a ‘bunch of stuff’. It needs the Shaper’s natural drive for goal setting and the Plant’s creative spark to build the pieces that ensure real business value is delivered. Without these roles, your sprint is just a list of tasks with no purpose.
2. Sprint Planning: The Reality Check
The first half of planning is where the Product Owner shares what will be done. While this is a Shaper role, a good dose of Monitor Evaluator behaviour ensures the sprint goal is actually achievable.
If the team is working in a larger organisation, the Resource Investigator is vital; they naturally build networks to other teams to ensure the sprint goal is in harmony with the wider business, for example, where other teams are trying to launch a product that relies on features you need to build / incorporate. In the second half of the Sprint Planning meeting, the Coordinator ensures everyone is clear on their tasks, while the Teamworker watches for overloading to prevent burnout.
3. The Daily Scrum: Maintaining Momentum
The Daily Meeting is where most teams lose their way. To keep it punchy:
The Shaper ensures the sprint is on track and the goal is being met.
The Implementer rolls up their sleeves, gets on with tasks, and ensures progress is recorded on a Kanban board (and often takes pleasure in producing the ‘burndown charts’).
The Completer Finisher polices the ‘Definition of Done’, ensuring no one is cutting corners on testing or documentation.
The Specialist and Plant are your ‘Blocker-Busters’, using deep technical knowledge or creative pivots to overcome obstacles.
The Teamworker monitors for stress and suggests solutions like pairing to resolve issues early.
4. The Sprint Review: Stakeholder Engagement
Once the sprint is completed, a ‘potentially shippable product increment’ should be ready. The Resource Investigator ensures all necessary stakeholders are in attendance, while the Monitor Evaluator reviews the increment for gaps. The Specialist handles the demonstration, answering the deep technical questions that investors/stakeholders actually care about.
5. The Retrospective: Continuous Improvement
Retrospectives (or post-mortem review) often identify issues but fail to resolve them. A Monitor Evaluator ensures the facts are on the table, while the Teamworker ensures feedback is handled diplomatically to avoid blame culture. The Shaper prevents the meeting from disappearing down rabbit holes and ensures the team stays on track as well as making sure that at least one of the items gets fixed in the next sprint cycle (and we don’t agree to fix every issue raised – which in reality means nothing gets improved).
6. Refinement: The Quality Filter
Backlog Refinement is where future success is built in a regular meeting that builds what is needed for upcoming sprints, then gets the team to collectively assess and size the work (using tools like Planning Poker). For this meeting to be effective, the Plant challenges the status quo with creative solutions, aided by the Specialist's deep knowledge. The Completer Finisher ensures no half-thought-through ideas make it to the sprint backlog, while the Monitor Evaluator ensures work items are sized realistically, setting the team up for success.
If you are in a sprint team and have any of the behavioural roles missing – its likely that the entire scrum cycle will be affected by the gap.
Agile Sprint Cycle and where each Belbin team role plays an essential part
Case Study: The ‘Brilliant’ Software House That Couldn't Ship
We recently worked with a high profile tech team in a Tier 1 Investment Bank. Their engineering team was composed of 90% Plants and Specialists. They were brilliant, inventive and visionary, but they were in a perpetual state of refining requirements.
They had no Implementers to build the software (despite having several ‘programmers’) and no Completer Finishers who were naturally attuned to polishing the final 5%. Consequently, they were missing 70% of their sprint goals. The ‘Cultural debt’ (the price paid for ignoring team issues today) was massive - the Board had lost trust, and project budget was being incinerated in so-called Research and Development that never reached the customer.
By introducing just two team members (exchanging) from another team who had strong Implementer / Completer Finisher profiles and empowering an existing team member as Coordinator to facilitate delegation, their velocity/throughput increased by 45% within three sprints. They didn't need a new process; they needed the behavioural muscle to move the process.
The Investor’s Lens: De-risking the Human Engine
In a business context, an Agile team that lacks behavioural balance is a high-risk asset. McKinsey research shows that 70% of complex, large-scale change programs fail, with ‘Employee resistance and management behaviour’ being the primary cause, but we believe that its not malicious failure, and even with the best processes and procedures, you need a sensibly balanced team behaviourally to make things work and naturally adopt the roles needed.
If you have a team of Plants with no Implementers, you are funding a research lab, not a product. If you have Shapers with no Teamworkers, you are funding a high-churn culture that will incinerate talent and profits. By conducting a professional Belbin Team Role assessment, you move from guessing to knowing in a way that puts facts behind a powerful dimension. In a recent client engagement, the CEO said “for years I’ve known that behaviour is a critical part of business, but for the first time ever I can put numbers and facts on it, measure it and improve it”. You can identify natural strengths, expose blind spots, and strategically optimise team composition to ensure the Value Creation Plan is actually executable.
The 2-Minute Agile Diagnostic
Whether you are an operational agile team, or a team of very senior practitioners following an Agile approach, is your team behaviourally balanced? Ask yourself:
Who is the Completer Finisher? If no one is obsessing over the "Definition of Done," your technical debt is quietly killing your future margin.
Who is the Resource Investigator? If your team only talks to each other, you are building a product in a silo that stakeholders won't recognise.
Do we have Role Voids? Without the right mix of roles, teams struggle to maintain momentum, resolve conflict, or innovate effectively.
The "So What?"
We’ve seen teams have amazing results by adopting Agile ways of working – the best team we’ve seen had a 300% improvement in productivity (although we buried that statistic from company view to save the team from potential embarrassment!). For most teams, a 20-50% improvement in output isn’t unusual, but more importantly, that is often coupled with a massive increase in team engagement, which to us is priceless.
We’ve helped countless software teams, and many business teams to adopt working in this way.
If the Agile process is the skeleton; Belbin is the muscle. Yes, teams sometimes just ‘get it’, but more often that not, Agile doesn’t fully take hold and we believe that one without the other (i.e. Agile without Belbin) is often useless. To achieve exceptional results, you must optimise the team and its behavioural or cognitive diversity, not just the ticket board. This is how you build a resilient, productive and engaged organisation that can fully harness the power of Scrum.
Are you struggling to unlock the benefits you'd hoped from the shift to Agile ways of working? Get in touch below to discuss how we can help you to maximise the potential of your teams.
