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:

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