Skip to main content

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

  1. The team reports to the Scrum Master at the Daily Scrum
  2. People wait for instructions from the Scrum Master
  3. Team members don't hold each other responsible [for their commitments]
  4. The same impediment comes up twice
  5. "That's the way it is" => resignation
  6. "I" instead of "We"
  7. Flip charts are lonely
  8. Culture of conflict-avoidance
  9. Decisions processes are unclear, nor are they discussed
  10. Personal goals are more important than team goals

To this list I would add my a couple of my favorites:
  1. you don't see a triangle on the task board (not working according prioritization of stories)
  2. after the daily Scrum, people return directly to their desks (no collaboration)
  3. there are a least as many stories in progress as team members (no pairing)

P.S. You can join the discussion or solve your own challenges at a future event! And here is the original list (in German).

EDIT: Here is the second slide:

  • Retrospectives are superficial
  • Agile Mindset Not Present => No inspect and adapt
  • The Team has no influence on the backlog (order, content, priority)
  • The Team is not interested in improving their performance
  • Changes in Team Composition are not managed by the Team
  • New members are not introduced by the whole team
(Suggestions for improved translation are most welcome!)


Think Quality said…
Was very interesting to create this list. Many of these warning signs are quite common for teams who are new to agile. The point you added to the list (team members return to their desks after daily) is also a very good indicator (just recently observed this...)
Thanks for your translation.
Think Quality said…
Hi Peter
There was a second flip with more signs...see attachments from Godela.
Peter said…
Hi Think

Thanks for pointing that out. I have added a link to the picture and taken a short at translating it.

Unknown said…
Thanks a lot for this very helpful list. We will use it as base for communication and that for, we prefer to have a positiv description. So we changed and used "we" instead:

The team reports to the Scrum Master at the Daily Scrum
We discuss our achievements and the Most Important Task for the day for ourselves and not for the Scrum Master.

People wait for instructions from the Scrum Master
We don’t wait for instructions. We always identify and start the next Most Important Task.

Team members don't hold each other responsible [for their commitments]
We depend on each other’s commitments.

The same impediment comes up twice
We never let a problem happen again.

"That's the way it is" => resignation
“We’ve always done it that way” is not a reason.

"I" instead of "We”
Always “we”, not “I”.

Flip charts are lonely
We come together to describe, diagram and prototype new concepts and designs.

Culture of conflict-avoidance
We are not afraid to disagree.

Decisions processes are unclear, nor are they discussed
We understand how a decision has been made and why.

Personal goals are more important than team goals
We prioritise team goals over personal goals.

Maybe it helps you, as well.
Peter said…
Dear Mladen,

Thank you so much for this! I am thrilled that our work has inspired you. I will post this back to the original thread so the workshop participants can benefit from your work!

Rashmi said…
Thanks for a summarized list...
Agreed, i have experienced that #3 and #10 are killer for scrum team.

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…