Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Webinar #7: Scrum Sprint Anti-Patterns [Video]

DZone's Guide to

Webinar #7: Scrum Sprint Anti-Patterns [Video]

The seventh webinar in this series tackles some of the most common Scrum anti-patterns that teams should be aware of and avoid.

· Agile Zone ·
Free Resource

You've been hearing a lot about agile software development, get started with the eBook: Agile Product Development from 321 Gang

The seventh Hands-on Agile webinar Scrum Sprint Anti-Patterns analyzed 12 ways a Scrum team can improve its effectiveness by avoiding typical sprint anti-patterns. Learn more about gold-plating, delivering Y instead of X, absenteeism, side-gigs, and organizing people instead of the flow of work.

The video of the webinar is available now:


Webinar Scrum Sprint Anti-Patterns: The Episodes

  • The first episode covers the absent Product Owner: This means no feedback to developers during the sprint thus increasing the risk of not meeting the sprint goal. The best product backlog refinement shall not answer all questions in advance—that would be too granular and thus waste. A successful sprint is all about collaboration between the Product Owner and the developer team in real-time.
  • The second episode covers the interfering Product Owner: You can change the sprint backlog—if the development team agrees—as the sprint backlog is not static. However, the Product Owner cannot single-handedly change it, for example, increase its scope. (The sprint cancellation is the exception to this rule if you want to consider abandoning the current sprint as a change of its sprint backlog.)
  • The Third episode covers scope-stretching or gold-plating: The development team increases the scope of the sprint by adding unnecessary work to sprint backlog items. For example, the development team enlarges a task without prior consulting of the Product Owner. This ignorance may result in a questionable allocation of resources thus endangering achieving the sprint goal as well as creating waste.
  • The fourth episode covers out-of-date sprint boards: The development team does not update tickets on the board in time to reflect their current statuses. No matter if it is a physical or digital board, it is vital for coordinating a team’s work. Transparency is key to inspection and adaptation during the daily Scrum: who needs help, is our plan to achieve the sprint goal still working? An up-to-date board is also an integral part of the communication of the Scrum team with its stakeholders. A board that is not up-to-date will impact the trust the stakeholders have in the scrum team: “How shall they deliver software if they already fail at moving a few stickies?” Deteriorating confidence may then cause counter-measures on the side of the stakeholders. The (management) pendulum may swing back toward traditional methods as a consequence. The road from Scrum to PRINCE II is paved with abandoned boards.
  • The fifth episode covers the flow undermining Scrum Master: The Scrum Master allows stakeholders to disrupt the flow of the development team during the sprint. For example, the SM has a laissez-faire policy as far as access to the development team is concerned. Or the SM does not object that the management invites engineers to random meetings as subject matter experts. Or the scrum master allows that either stakeholders or managers turn the daily scrum into a reporting session.
  • The sixth episode covers the skipped Retrospective: All Scrum events are essential for a team’s success — you cannot skip an event. Junior Scrum teams may be tempted to skip Retrospectives to buy some more time to meet the sprint goal. A Scrum Master accepting this “deal” is a Scrum Master by title only. The proposal is already a sign of how important the team needs a retrospective.
  • The seventh episode covers the static sprint goal: According to the Scrum guide, the Scope may be clarified and re-negotiated between the Product Owner and the development team as more is learned. There is no such thing as a static sprint goal.
  • The eighth episode covers the hardening sprint: The Scrum team decides to have a hardening or clean-up sprint. That is a simple one: there is no such thing as a hardening sprint in Scrum. Let’s revisit the Scrum Guide: Quality goals do not decrease. Hence hardening sprints are commonly a sign of a low grade of adoption of agile principles by the development team or the (engineering) organization. If you encounter this anti-pattern, ask yourself: Is the development team cross-functional? Or is QA still a functional, non-agile silo? Suggesting a hardening sprint thus violates a core component of Scrum: adherence to the Definition of Done.
  • The ninth episode covers variable sprint lengths: The scrum team extends the sprint length by a few days to meet the sprint goal. This extension is just another way of cooking the agile books. Please remember: the sprint goal is delivering working software that delights the customers within the available time-box. Stop lying to yourself, and address the underlying issues — why didn’t the sprint’s outcome meet the sprint goal in time? — during the next retrospective.
  • The tenth episode covers special Scrum forces: A manager assigns specific tasks directly to engineers, bypassing the Product Owner. Alternatively, the manager removes an engineer from the Scrum team to work on such a task. This behavior does not only violate core Scrum principles. It also indicates that the manager cannot let go command and control practices. He or she continues to micromanage subordinates although the Scrum team could accomplish the task in a self-organized manner. This behavior demonstrates a level of ignorance that may require support from a higher management level to deal with.
  • The eleventh episode covers the everything-is-a-bug stakeholder hack: Stakeholders try to speed up delivery of their issues by relabeling tasks as ‘serious bugs.’ First of all — nice try! Nevertheless, the Scrum Master shall address the stakeholders in question and coach them on “useful interaction with the Scrum team.” As Joko Willink likes to say: leadership is not what you preach, but what you let slip through. And while you’re at it: Watch also out for stakeholders trying to sneak in small tasks by pitching them directly to developers.
  • The twelveth episode covers the all-hands-to-the-pump moments: The management temporarily abandons Scrum in a critical situation. This is a classic manifestation of disbelief in agile practices, fed by command & control thinking. It is fine-weather sailing so to speak. Most likely, canceling the sprint and starting a new sprint addressing the issue at hand would also solve it.
  • The last episode summarizes the dirty dozen of the sprint anti-patterns: from gold-plating, delivery Y instead of X, to absenteeism, side-gigs, and organizing people instead of the flow of work. Don’t miss the next Hands-on Agile mini-series and subscribe to this Youtube channel.

Agile Transition – A Hands-on Guide from the Trenches

The free Agile Transition – A Hands-on Guide from the Trenchese-book is a 249-page collection of articles I have been writing since October 2015. They detail the necessary steps to transition an existing product delivery organization of over 40 people strong to Agile practices.

Download the free agile tools checklist from 321 Gang. This guide will help you choose the right agile tools to position your team for success. 

Topics:
scrum ,sprint ,agile anti patterns ,development team ,webinar recording ,webinar ,agile

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}