Focus on Plain English Acceptance Criteria for Epics

Useful, comprehensive and plain English Acceptance Criteria are essential at the Epic level.

Writing Epics in plain English will enable a decomposition into User Stories and Acceptance Criteria in the Agile Teams which will align to the Stakeholders requirements.

If Stakeholders do not define their Epic-level Acceptance Criteria very well, a lot of time will be wasted with Agile Team Members going back and forth to the Stakeholders requiring clarifications and elaborations. More thought at the beginning of each Epic saves huge amounts of time and money downstream.

The Product Owner and Scrum Master should reject Epics with no Acceptance Criteria or poorly worded or ambiguous Acceptance Criteria before they get anywhere near the Agile Team for sizing etc.

Got a Question? Ask Agile Unpacked…