DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Please enter at least three characters to search
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Modernize your data layer. Learn how to design cloud-native database architectures to meet the evolving demands of AI and GenAI workkloads.

Secure your stack and shape the future! Help dev teams across the globe navigate their software supply chain security challenges.

Releasing software shouldn't be stressful or risky. Learn how to leverage progressive delivery techniques to ensure safer deployments.

Avoid machine learning mistakes and boost model performance! Discover key ML patterns, anti-patterns, data strategies, and more.

Related

  • Rebalancing Agile: Bringing People Back into Focus
  • Management Capabilities 101: Ensuring On-Time Delivery in Agile-Driven Projects
  • Feature Owner: The Key to Improving Team Agility and Employee Development
  • How to Demonstrate Leadership in Cross-Functional Software Development Teams

Trending

  • Java's Quiet Revolution: Thriving in the Serverless Kubernetes Era
  • Evolution of Cloud Services for MCP/A2A Protocols in AI Agents
  • Event-Driven Architectures: Designing Scalable and Resilient Cloud Solutions
  • Recurrent Workflows With Cloud Native Dapr Jobs
  1. DZone
  2. Culture and Methodologies
  3. Agile
  4. Scrum: 16 Stand-up Anti-Patterns

Scrum: 16 Stand-up Anti-Patterns

Daily stand-ups can be a great way of creating cohesion among your team, and keeping everyone on the same page. Here are some patterns that can de-rail a stand-up.

By 
Stefan Wolpers user avatar
Stefan Wolpers
DZone Core CORE ·
Apr. 06, 17 · Opinion
Likes (33)
Comment
Save
Tweet
Share
18.4K Views

Join the DZone community and get the full member experience.

Join For Free

The daily stand-up is the ceremony with the highest anti-pattern density among all Scrum ceremonies. Learn more about the stand-up anti-patterns that threaten to derail your Agile transition.

Hands-on Agile: 16 Stand-up Anti-Patterns Threatening Your Transition to Scrum

Stand-up Anti-Patterns: From Dysfunctional Scrum Teams to Organizational Failures

Typically, a good Scrum team needs about five to ten minutes for a stand-up. Given this short period, it is interesting to observe that the daily stand-up is the Scrum ceremony with the highest potential anti-pattern density. The anti-patterns range from behaviors driven by dysfunctional teams to apparent failures at an organizational level.

My favorite stand-up anti-patterns are as follows:

  1. The stand-up is a status report meeting, and team members are waiting in line to “report” progress to the Scrum master, the product owner, or maybe even a stakeholder.
  2. Updates are generic with little or no value to others (“Yesterday, I worked on X-123. Today, I will work on X-129”).
  3. Discussions are triggered to solve problems, instead of parking those so they can be addressed after the stand-up.
  4. The team hijacks the stand-up to discuss new requirements, to refine user stories, or to have a sort of (Sprint) planning meeting.
  5. A team member experiences difficulties in accomplishing an issue over several consecutive days, and nobody is offering to help (this a sign that people either do not trust each other or that the utilization of the team is maximized).
  6. Team members violate the time-boxing, starting monologs (60 to 90 seconds per team member should be more than enough time on air).
  7. A few team members are commenting on every issue (usually, this is not just a waste of time, but also patronizing as well as annoying).
  8. Other team members are talking while someone is sharing his or her progress with the team (similarly irritating is the need to use speak tokens among adults to avoid this behavior). 
  9. The product owner – or Scrum Master – assigns tasks directly to team members.
  10. Team members are not prepared for the stand-up (“I was doing some stuff, but I cannot remember what. Was important, though.”).
  11. The stand-up acts as a kind of artificial factory siren to start the next shift (this is a common Taylorism artifact where trust in the team is missing). 
  12. Team members are late to the stand-up (note: if the team did not choose the time for the stand-up it otherwise indicates distrust on the management side).
  13. Team members criticize other team members right away sparking a discussion instead of taking their critique outside the stand-up.
  14. Stand-ups are ineffective due to the large number of active participants.
  15. “Chickens” actively participate in the stand-up. I think it is acceptable if stakeholders ask a question during the stand-up. However, they are otherwise supposed to merely listen in.
  16. Line managers are attending stand-ups to gather “performance data” on individual team members (this behavior is defying the very purpose of self-organizing teams).

Depending on the context, it could also be an anti-pattern if the product owner – or even another stakeholder – is introducing new tickets to the current Sprint during the stand-up. This behavior may be acceptable for priority one bugs (although the team should be aware of those before the stand-up). However, it is an unacceptable behavior – and thus an anti-pattern – for changing priorities on the fly in the middle of a Sprint.

Lastly, some teams like to have stand-ups in Slack, particularly those that are not co-located. Again, depending on the context, this does not need to manifest an anti-pattern.

Conclusion

A lot of Agile practitioners tend to consider stand-ups to be a candidate for waste. However, from a Scrum Master or Agile coach perspective, stand-ups offer the highest yield of anti-patterns – given the effort is so small by comparison to other ceremonies.

What stand-up anti-patterns have you observed? Please share with us in the comments.

scrum Anti-pattern agile

Published at DZone with permission of Stefan Wolpers, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Rebalancing Agile: Bringing People Back into Focus
  • Management Capabilities 101: Ensuring On-Time Delivery in Agile-Driven Projects
  • Feature Owner: The Key to Improving Team Agility and Employee Development
  • How to Demonstrate Leadership in Cross-Functional Software Development Teams

Partner Resources

×

Comments
Oops! Something Went Wrong

The likes didn't load as expected. Please refresh the page and try again.

ABOUT US

  • About DZone
  • Support and feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends:

Likes
There are no likes...yet! 👀
Be the first to like this post!
It looks like you're not logged in.
Sign in to see who liked this post!