Remove Definition Remove Quality Assurance Remove Test-Driven Development
article thumbnail

Definition of Done vs. User Stories vs. Acceptance Criteria

Agile Pain Relief Notes from a Tool User

One of the more frequently asked questions in my Scrum workshops is around the difference between Definition of “Done” and Acceptance Criteria , and how they relate to User Stories. While Acceptance Criteria is a commonly understood concept in software development, Definition of “Done” is unique to Scrum. Definition of “Done”.

SCRUM 107
article thumbnail

AoAD2 Practice: Test-Driven Development

James Shore

Test-Driven Development. We produce high-quality code in small, verifiable steps. It’s test-driven development, and it actually delivers these results. Test-driven development, , or TDD, is a rapid cycle of testing, coding, and refactoring. Other Unit Test Definitions.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Quality Management is Risk Management

Xebia

From a quality perspective this is mostly about making sure deviations can be mitigated as soon as possible. . Designing your quality strategy . To lower risks, we introduce quality assurance. Understanding the risk management strategies enables us to design a quality strategy. .

article thumbnail

Definition of Done vs. User Stories vs. Acceptance Criteria

Agile Pain Relief Notes from a Tool User

import Figure from '@/components/global/figure.astro'; import APRBlogIllustrationsNov2019AcceptanceCriteriaAV2 from 'src/content/blog/definition-of-done-user-stories-acceptance-criteria/images/APR_Blog-Illustrations_Nov2019_AcceptanceCriteria_A_v2.jpg'; Still others will assume that Done is limited to checking in working code.

SCRUM 52
article thumbnail

AoAD2 Practice: Fast, Reliable Tests

James Shore

Fast, Reliable Tests. Our tests don’t get in our way. Test-Driven Development. Teams who embrace test-driven development accumulate thousands of tests. The more tests you have, the more important speed and reliability become. The vast majority of your tests should be unit tests.

article thumbnail

Behavior Driven Development: The methodology that connects the three amigos

Apiumhub

Developer: Implements the requirements captured by the business to create the product. Quality assurance: Validates that the final product matches the initial specifications. Behaviour Driven Development is a software methodology that allows us to define and develop the product based on the behaviour of the system.

article thumbnail

How to Cross-Skill and Grow T-shaped Team Members

Agile Pain Relief Notes from a Tool User

Goldratt’s work is, in part, the basis for Kanban and also shows why, in a constrained situation, moving a Developer or Writer from their primary work to the constraint (e.g. Quality Assurance or Editing) is so effective. Test Driven Development, Behaviour Driven Development).

SCRUM 65