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
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

  • Challenges and Ethical Considerations of AI in Team Management
  • Automating PMO Meetings With n8n Automation
  • Conflict Management in Technology Teams: Insights From Google's Project Aristotle
  • Efficient Ticket Management Using LangChain and Large Language Models

Trending

  • Key Considerations in Cross-Model Migration
  • Scaling in Practice: Caching and Rate-Limiting With Redis and Next.js
  • Cutting-Edge Object Detection for Autonomous Vehicles: Advanced Transformers and Multi-Sensor Fusion
  • Medallion Architecture: Efficient Batch and Stream Processing Data Pipelines With Azure Databricks and Delta Lake
  1. DZone
  2. Culture and Methodologies
  3. Team Management
  4. The Definition of Done, Done-Done and Really Done

The Definition of Done, Done-Done and Really Done

Definition of Done is a bit of vague term and tends to vary from team to team. An Agile expert gives his views of Definition of Done and what Done really means.

By 
Gil Zilberfeld user avatar
Gil Zilberfeld
·
Nov. 06, 17 · Opinion
Likes (18)
Comment
Save
Tweet
Share
16.4K Views

Join the DZone community and get the full member experience.

Join For Free

In a short post, John Cutler reminds us that the work is never done. Customers change, their needs change, we have new ideas, and that's why we show up for work every day.

His final suggestion is not to be fooled by Jira's "Done" status.

I can't believe I'm actually defending Jira here, but Done (in Jira or outside), is really meaningful. It is so important that we even have variants for it, like "Done with bugs," or "Dev done."

Regardless of what the Definition of Done in your team really is, "Done" means we can do the following:

  • We celebrate completion (We love that! Our bosses love that!).
  • We clear our minds of the actual work, problems, and issues we've worked on.
  • We focus on the next item, feature, and task.
  • We match expectations with other people, who now know that we've moved on.

Done is so precious, in any of its forms, because it's a signal, like a traffic light. We're looking at the flashing lights, waiting for the light to change. We know it's coming, and we know what's coming right after the event.

It's no surprise that we like moving those post-its (or changing the status in Jira). It's not the Definition of Done we're celebrating, but the meaning of moving forward.

We're making progress.

Visibility of Done-ness

The problem with "our" Definition of Done starts when it's not as completely Done as we, and others, expect it to be.

When "Done" means "Dev Done," well, the work is not really done.

When "Done" is "Test Done," but with a couple of bugs open, it's still not really done.

Even when Done means it's "shippable," or even "shipped," feedback needs to come back, and then work may resume, as John suggested.

We have moved forward, yet work has returned to haunt us like a bad horror movie sequel.

The Definition of Done's Hidden Meaning

Done, much like life itself, is a matter of perspective.

  • At the individual level, "Done" is when I passed my deliverable to someone else.
  • At the team level, "Done" is when the team completes their work and passes their package to the Ops team, or (hopefully deployed automatically).
  • At the product level, "Done" is when we get feedback from the customer that finds the product/feature/bug fix valuable.
  • And even then, a few months later, what was Done may be completely overturned.

We may never be "really" Done, and Jira may indeed fool us. But as long as we understand that "Done" is temporary, and we can look at the board and ask about its done-ness, it is still useful.

At the end of the day, the work is "Done" when we ask:

What's next?

teams Jira (software) Project management

Published at DZone with permission of Gil Zilberfeld, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Challenges and Ethical Considerations of AI in Team Management
  • Automating PMO Meetings With n8n Automation
  • Conflict Management in Technology Teams: Insights From Google's Project Aristotle
  • Efficient Ticket Management Using LangChain and Large Language Models

Partner Resources

×

Comments

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: