What are the 3 parts of SAFe definition of done?

• A. Code complete, Test complete, Release
• B. Working software, System Increment, Release
• C. User acceptance, Documentation, Deployment
• D. Design, Build, Verify

Answer: (B)

In SAFe, the Definition of Done means a piece of work is truly finished and ready to be released. The best way to express this is that a completed increment must be a functioning, integrated piece of value that can be released. First, it should be working software—meaning the functionality works as intended, meets the acceptance criteria, and is demonstrable to stakeholders. Second, it must be a System Increment, which means this work has been integrated with the rest of the system, tested in the context of the whole product, and aligns with architecture and nonfunctional requirements. Third, it has to be releasable—approved for release to production, with the release process in place, appropriate documentation, and governance complete so the product owner can decide to deploy.

Other options tend to focus on isolated aspects (like just code, or just acceptance or deployment) or use terms that don’t align with SAFe’s emphasis on a cohesive, releasable increment that spans from implementation through integration to release.