DZone
Agile Zone
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
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Agile Zone > Challenging Sprint Retrospectives

Challenging Sprint Retrospectives

Don't be afraid to dig deep in your Sprint Retrospectives, and try implementing creative solutions, like knowledge sharing sessions, to make your next Sprint great.

Gunther Verheyen user avatar by
Gunther Verheyen
·
Mar. 01, 17 · Agile Zone · Opinion
Like (3)
Save
Tweet
8.31K Views

Join the DZone community and get the full member experience.

Join For Free

An essential question when doing Scrum seems to be, “How can we make our Retrospectives more fun?"

i-wonderIt makes me wonder about the value of engagement, human energy, and bottom-up inspiration. It makes me wonder because Done Increments are at the heart of the empiricism and the Agility of Scrum.

If Scrum was to be reduced to one purpose, and one purpose only, that is the creation of a Done Increment in a Sprint.

So few teams are able to actually deliver releasable versions of a product, Sprint after Sprint after Sprint. And this problem is only compounded when multiple teams are involved in delivering a product.

Understanding that Scrum Masters are all about helping teams and organizations understand and enact Scrum, the following might be a great way to start your next Sprint Retrospectives:

  • Scrum Master: “Have we delivered a Done, releasable version of the product this Sprint?”
  • Team: “No.”
  • Scrum Master: “What can we do about that?”

How will this help to kick off a professionally challenging and fun Sprint Retrospective? How will this question initiate a deep reflection on improvements that will help teams and the organization get more out of employing Scrum? How can this be a start for some fun experiments in the next Sprint?

Committed, connected and engaged people might consider these solutions:

  • Increased effectiveness through collaboration, autonomy, and self-organization.
  • Skills and knowledge sharing (training, communities).
  • Engineering practices, and standards.
  • Infrastructure, tooling, and automation.
  • Quality standards and guidelines.
  • Removal of Impediments.
  • Elimination of low value (requirements, projects).

I wish you fierce, focused, and purposeful Sprint Retrospectives. It’ll be seriously fun. Fun and purpose go hand in hand

Sprint (software development) retrospective scrum

Published at DZone with permission of Gunther Verheyen, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Pull Request vs. Merge Request
  • How To Build a Multi-Zone Java App in Days With Vaadin, YugabyteDB, and Heroku
  • Why Should You Choose ReactJS for Your Next Project?
  • Workout Tracking With Your App in the Background

Comments

Agile Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

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

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo