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:

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