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:

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