Close this search box.
Close this search box.
Close this search box.

When Scrum Events Are Burdening

At the beginning of a Scrum implementation y, you usually find two main types of team behaviors. Those who embrace the scrum events (Planning, daily, etc.) and try to better understand them to represent one type. There are many issues and many required adjustments and the team is working on them with the coach. Other teams view Scrum events as a total waste of time. They do them reluctantly and don’t see any value in it. What do you do? We’ve had several such cases and we wanted to better understand what’s going on there. After a deeper look into the dynamics of these teams, we reached some conclusions that let us sleep better at night.

Reason One – Lack Of Understanding

The first obvious reason for a team not performing the scrum events would be that they didn’t get what we’re looking for. It may be they went through training, saw videos, and had pep talks with their managers but still, they didn’t get it. They think this is just another fad and it will go. We say culture follows practice but if you don’t understand where you’re aiming for you just won’t get there. Here is where one on one coaching and a lot of patience is in place.

Reason Two – The Double Star Syndrome

A good clue to what’s going on is the value of the scrum events. The events are there to help the team self-organize: to make sure everyone sees what’s going on so everyone can make decisions. Following the above clue, we understand that another possible explanation for what’s going on in these teams is that the command and control management style in these teams has reached some local optimum, meaning, quite frankly, that it works well. There is usually a talented team leader there, that works very hard, and a bunch of people doing what she says. The people around the leader usually admire her, which reinforces the same dynamics. “How can we decide anything without her in the loop?” The result is that the leader keeps working harder and harder and the other people of the team become smaller and smaller, but in some way, they are all happy about it. The team leader’s ego is well provided for in this situation, and the other team members are feeling blessed for having the opportunity of working with her. We call this the “Double Star Syndrome”: the team is working in a star formation (the leader in the middle) and the team leader becomes a star! In this situation, it is no surprise the entire team is against Scrum events. Who needs planning if the leader does it alone and very well anyway? Who needs the daily meeting if the leader goes around telling everyone what to do? No doubt the retrospective is redundant too – let the leader think about what should we do to improve But what’s wrong with this picture? Why should we change? Should we change? These are good questions (and we’re being quite objective here). We would like to say that in the long run, this management form is unsustainable – meaning, it will not hold for long. However, that would not be true. Many teams are working this way, spawning more managers using the same style. A team member looking admiringly at her manager would like to be in her place. Many people are looking for this kind of power and it is a great motivation for working hard and being promoted. This leads us to the ultimate reason, the mother of all reasons for the change:

The Ultimate Reason for Hating The Scrum Events – Everything’s Fine!

To make a change you need to have a compelling reason. If everything’s fine, don’t change anything. Yet, being in this situation, asking ourselves these questions, suggests something started a change process. It may be that the real reasons for change are hidden and you need to discover them. As a manager, as a coach, you must find the reason for the change. Many times we just get into the “implement the ceremonies” frenzy and forget why are we doing it for. That’s not good. We need to remind ourselves again and again why are we doing the change. The bottom line is that when people see the scrum roles as burdening, the solution would not be to enforce them. The solution would be to understand why are they seen this way. Does the team understand where we’re going? Is there something basic about how the team operates that is blocking the agile implementation? Is there really a reason to change?
Subscribe for Email Updates:



RTE Role
Scrum With Kanban
Agile Contracts Best Practices
Principles of Lean-Agile Leadership
Agile Techniques
ScrumMaster Tales
Agile Product Ownership
Product Management
Jira admin
Large Scale Scrum
Legacy Code
Keith Sawyer
Built-In Quality
Quality Assurance
Games and Exercises
Rapid RTC
Agile Basics
Continuous Deployment
speed at scale
Applying Agile Methodology
Agile Exercises
Releases Using Lean
Acceptance Test-Driven Development
User stories
Implementation of Lean and Agile
Continuous Integration
Systems Thinking
Lean Risk Management
Entrepreneurial Operating System®
SAFe Release Planning
A Kanban System for Software Engineering
Release Train Engineer
PI Objectives
Coaching Agile Teams
PI Planning
Agile and DevOps Journey
Development Value Streams
Kanban Basics
Jira Plans
Agile Risk Management
Agile Assembly Architecture
Engineering Practices
What Is Kanban
The Agile Coach
System Integration Environments
Professional Scrum Product Owner
Introduction to Test Driven Development
Sprint Iteration
Lean-Agile Software Development
Lean Agile Basics
Agile Program
Lean Agile
Nexus and Kanban
Effective Agile Retrospectives
Agile Testing Practices
Process Improvement
Change Management
Risk-aware Product Development
Iterative Incremental Development
Business Agility
Software Development
Risk Management in Kanban
Agile Games
Agile for Embedded Systems
Agile Delivery
Agile Project Management
lean agile change management
Legacy Enterprise
Software Development Estimation
Kanban Kickstart Example
Scrum Master Role
Scrum Guide
Agile Israel
Lean-Agile Budgeting
Agile Release Planning
Elastic Leadership
Lean Budgeting
Scaled Agile Framework
Risk Management on Agile Projects
Scrum Primer
Lean Agile Organization
Introduction to ATDD
Nexus Integration Team
Test Driven Development
Agile Israel Events
Nexus vs SAFe
An Appreciative Retrospective
Certified SAFe
Kanban Game
Daily Scrum
Managing Risk on Agile Projects
Story Slicing
Agile Community
Lean Software Development
Lean Agile Leadership
Lean Agile Management
Sprint Planning
Professional Scrum with Kanban
The Kanban Method
System Archetypes
speed @ scale
Kanban 101
Operational Value Stream
Product Ownership
Agile Outsourcing
Managing Projects
Scrum Master
Enterprise DevOps
Program Increment
Achieve Business Agility
ART Success
Lean Startup
SAFe DevOps
Scrum Values
Perfection Game
Continuous Improvement
ALM Tools
Reading List
Professional Scrum Master
Agile Project
Limiting Work in Progress
System Team
Artificial Intelligence
Pomodoro Technique
Kaizen Workshop
Manage Budget Creation
Accelerate Value Delivery At Scale
Agile India
Implementing SAFe
Agile Mindset
Agile Product Development
Agile Games and Exercises
Agile Marketing
Continuous Planning
Scrum and XP
Sprint Retrospectives
IT Operations
AI Artificial Intelligence
Value Streams
Agile in the Enterprise
Agile Release Management
Jira Cloud
Team Flow
Portfolio for Jira
Lean and Agile Principles and Practices
Lean and Agile Techniques
Agile Development
Nexus and SAFe
Hybrid Work
Advanced Roadmaps
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart