validate-artefacts

You validate Discovery phase epics and stories by running them against predefined quality and governance standards, ensuring they are outcome-oriented, clearly scoped, and free of contradictions before proceeding to the Delivery phase.

An artefact quality gate is a mandatory checkpoint that enforces the transition from Discovery to Delivery by verifying generated epics and stories are clear, complete, and meet specific validation criteria.

To check if user stories have measurable acceptance criteria, run an artifact validation process that specifically inspects stories for clear, testable conditions and cross-checks them against optional strategy and marketing inputs.

Yes, you can cross-check epics against optional strategy and marketing artifacts to verify alignment between your Discovery phase outputs and broader strategic inputs.

If Discovery artefacts have rule violations or contradictions, the validation process identifies these issues, preventing downstream delivery problems by stopping incomplete or unclear epics and stories from progressing.

Yes, validating epics requires outcome-oriented scoping because the validation criteria specifically check that epics focus on delivering clear outcomes rather than just listing tasks.