Skip to main content

Definition of Done (DoD) vs Acceptance Criteria (AC)

 The Definition of Done (DoD) in Scrum is a formal description of the state of an Increment when it meets the quality measures required for the product. Think of it as all the necessary ingredients for an Increment to be considered complete. Just as the Sprint Goal represents the commitment by the Developers for the Sprint Backlog, and the Product Goal represents the commitment by the Product Owner for the Product Backlog, the Definition of Done is the commitment by the Developers for the Increment. It includes all the characteristics and standards that an Increment must meet to be released. Once the Definition of Done is satisfied, the Increment is considered “Done” and can be delivered. This transparency ensures that everyone shares a common understanding of the work completed and the standards met as part of the Increment. If a Product Backlog Item does not meet the Definition of Done, it cannot be released yet. The Definition of Done may include organizational standards or be tailored specifically for the product being developed12. Here are some examples of items that might be found in a Definition of Done:

For a written Marketing Case Study:

  • Meets featured client branding guidelines
  • Written in AP style
  • Reviewed by the featured client, with feedback incorporated
  • Final draft approved by the client

For a health-focused software application:

  • All testing completed
  • No known defects
  • Code review completed and passed
  • Meets HIPAA compliance standards
  • Meets general security requirements

Remember that the Definition of Done ensures the quality and completeness of the product increment, contributing to successful product delivery in Scrum! 

Acceptance criteria are defined as the conditions that must be satisfied for a product, user story, or increment of work to be accepted. While not a part of the Scrum Guide, these criteria can be a useful tool that teams may choose to use to improve the quality of product backlog items. Also shortened to the acronym AC, these conditions are pass/fail. Acceptance criteria are either met or not met; they’re never only partially fulfilled. They are often expressed as a set of statements that should be:

Clear: So that everyone understands them.

Concise: So that there’s no ambiguity.

Testable or verifiable: Focused on providing customer-delighting results.

Acceptance criteria do not focus on “how” a solution is reached or “how” something is made. Instead, they illuminate the “what” of the work you are doing.

For example, the criteria may be: “Users can pay with Google Pay or Apple Pay at checkout.” The spirit of acceptance criteria is not to tell you how to do it (e.g., install a WordPress plugin or write HTML), but rather to define the conditions for accepting the work. It’s up to the developers on the Scrum team to decide the “how” of fulfilling the acceptance criteria. These criteria are widely used in software development but are now applied to various deliverables across diverse industries, from app development to Human Resources departments and beyond1

 Remember, acceptance criteria ensure that the work meets the necessary standards and aligns with customer expectations! 

Comments

Post a Comment

Popular posts from this blog

New way of product development

Today is the era of fast-paced world and competitive world. Companies are realizing that the old sequential approach to developing new products won’t get the job done and product can’t be reached to market when compared to competitors. The 4 stages of product development are as follows – R&D, Growth, Maturation, and Decline. Instead of sequential approach, companies are using holistic approach – as in rugby game, the ball gets passed within the team as it moves as a unit up the field. This holistic approach has six characteristics: 1)     Build-in-instability 2)   Self-organizing project teams 3)   Overlapping development phases 4)   Multi-learning 5)   Subtle (very clear and strong) control 6)   Organizational change to explore and learning The above six characteristics forming a fast and flexible process for new product development with advantage of act as a change agent, creative, market driven ideas, flexi...
Post a Comment
Read more

Product Manager vs Product Owner

Both the product manager and the product owner work towards a common goal, to build and improve products that create meaningful value for customers and all stakeholders within the company. This usually happens by delivering and optimizing product features. Product Manager Product Owner The product manager discovers what users need, prioritizes what to build next, and rallies the team around a product roadmap. The product owner is responsible for maximizing the value of the product by creating and managing the product backlog. This person creates user stories for the development team and communicates the voice of the customer in the Scrum process.      Product Manager and Product Owner's work on below vacuum. Product manager focus on: Business Strategy Long term Product Vision Long term Product Strategy Product Roadmap Alignment with Product Owner Product owner focus on: Release Plan (Product Backlog ie: ...
Post a Comment
Read more

Generative and Predictive AI - Artificial Intelligence

Generative and Predictive AI - Artificial Intelligence Generative AI: Generative AI (GenAI) is a type of artificial intelligence (AI) that can create new content.  GenAI learns patterns from training data and uses this knowledge to generate new outputs. The new outputs have similar characteristics to the training data, but they don't repeat it. GenAI can create a variety of content, including:  Images Videos Audio Text 3D models Music Speech Software code Product designs Here are some steps to build a GenAI: Benefits of GenAI: Makes informed decision Content creation and inspection Personalized experience Improved efficiency Automaton friendly Virtual guidance Disadvantages of GenAI: Generative AI can raise ethical questions about privacy, intellectual property, and misinformation. Generative AI models depend on the quality and diversity of their training data. Generative AI can't be completely trusted due to Incorrect facts and biased information. Generative AI is not me...
Post a Comment
Read more