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

When Scrum Events Are Burdening

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp
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:

Categories:

Tags:

Daily Scrum
Slides
Lean Risk Management
Risk Management in Kanban
lean agile change management
Agile Mindset
Implementing SAFe
SPC
Agile Release Management
Tips
Continuous Integration
AgileSparks
Kanban Game
Agile Product Development
Professional Scrum with Kanban
Advanced Roadmaps
Built-In Quality
PI Objectives
Releases Using Lean
Spotify
Lean Software Development
LeSS
Scrum Primer
Manage Budget Creation
Business Agility
Lean and Agile Principles and Practices
SAFe DevOps
Webinar
Scaled Agile Framework
Agile Product Ownership
Elastic Leadership
Lean Startup
Software Development
Agile Games and Exercises
Implementation of Lean and Agile
Agile Techniques
Change Management
Artificial Intelligence
Self-organization
Agility
The Agile Coach
ROI
Release Train Engineer
RTE Role
Lean Agile Leadership
Agile Israel
Risk Management on Agile Projects
Agile India
Kaizen
Presentation
Tools
Product Management
Atlaassian
Certified SAFe
Achieve Business Agility
RSA
Atlassian
Lean-Agile Budgeting
Introduction to ATDD
Program Increment
Nexus and Kanban
Large Scale Scrum
EOS®
Systems Thinking
predictability
Perfection Game
Process Improvement
Pomodoro Technique
Product Ownership
IT Operations
What Is Kanban
Continuous Planning
SA
Test Driven Development
TDD
Risk-aware Product Development
RTE
A Kanban System for Software Engineering
Scrum.org
Agile Assembly Architecture
Kanban
Rapid RTC
Scrum Master
LAB
Hybrid Work
Managing Projects
Lean-Agile Software Development
Video
Agile Community
Engineering Practices
Agile Contracts Best Practices
Kanban Kickstart Example
Lean Agile Basics
DevOps
Lean Agile
LPM
Enterprise DevOps
Kaizen Workshop
Agile Release Planning
Accelerate Value Delivery At Scale
GanttBan
Covid19
AI Artificial Intelligence
Story Slicing
speed @ scale
Introduction to Test Driven Development
ATDD
Agile
BDD
Scrum Master Role
ATDD vs. BDD
The Kanban Method
Legacy Code
Iterative Incremental Development
Sprint Planning
agileisrael
speed at scale
Managing Risk on Agile Projects
Acceptance Test-Driven Development
Continuous Deployment
Coaching Agile Teams
SAFe Release Planning
Agile Exercises
Nexus Integration Team
Lean Agile Organization
Amdocs
Scrum and XP
Agile Development
Entrepreneurial Operating System®
Agile Marketing
Scrum
PI Planning
Agile Program
Certification
Jira Plans
Quality Assurance
Sprint Retrospectives
Frameworks
Kanban Basics
System Integration Environments
POPM
AI
Lean Agile Management
QA
Nexus and SAFe
Agile Project
Agile for Embedded Systems
Reading List
ART Success
Agile in the Enterprise
Legacy Enterprise
Value Streams
Agile Risk Management
Continuous Delivery
Agile Games
Software Development Estimation
Planning
ARTs
Jira
System Archetypes
Effective Agile Retrospectives
Scrum With Kanban
Sprint Iteration
Operational Value Stream
chatgpt
Agile Project Management
Agile Outsourcing
Jira Cloud
Games and Exercises
Professional Scrum Master
An Appreciative Retrospective
Kanban 101
Agile Testing Practices
Jira admin
Continuous Improvement
Code
Nexus
Principles of Lean-Agile Leadership
Agile Basics
Scrum Guide
NIT
Lean Budgeting
Scrum Values
System Team
Agile and DevOps Journey
Limiting Work in Progress
Agile Israel Events
Agile Delivery
SAFe
Nexus vs SAFe
ALM Tools
ScrumMaster Tales
User stories
WIP
Lean and Agile Techniques
Portfolio for Jira
Professional Scrum Product Owner
Applying Agile Methodology
AgileSparks
Logo
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