What is SAFe's Definition of Done?

• A. Code complete and tested locally
• B. All tests pass in isolation
• C. Working software, system increment, release
• D. Product adoption metrics

Answer: (C)

In SAFe, the Definition of Done sets the standard for when a work item or increment is truly complete and ready for release. It emphasizes that what you produce isn’t just code, but a working, integrated system increment that can be released if needed. This means the item has passed the necessary acceptance criteria, quality checks, integration tests, and any nonfunctional requirements, and is demonstrable as a usable product.

Why this answer fits best: it captures end-to-end readiness—the increment is not just locally finished or tested in isolation, but is a cohesive, deployable artifact that could be released to users. The other options miss essential aspects: coding locally without integration, testing only in isolation without system-wide validation, or focusing on adoption metrics which measure outcomes rather than whether the increment is truly done and releasable.