Definition of Done – Epic and Feature level
An epic is a large story with minimal detail that is created from a high-level feature definition and will be broken down at a later step in sprint planning. Features and subsequent epics define the scope of product delivery. The scope is the vision of the end-product and is closely managed by quality metrics and processes. This ensures that only the features that are needed, viable and measurable are in sprints and subsequent releases.
Quality is also measured during the feature and epic stages by the evaluation of the value or Return on Investment (ROI) of a feature to deliver acceptance criteria that are of high value to the organization and end users.
The backlog prioritization and sprint review ceremonies provides opportunities to review quality at the feature level. During the prioritization ceremony features and epics are validated, updated and added so that the priority level is continuously reviewed.
During the sprint review ceremony, the product owner has the responsibility to review the features delivered to determine if the overall ROI and vision of the product have been met. If they have then the team may decide to stop delivery and divert resources to other activities. The team may also realize that the vision and ROI will not be met thereby ending a project that is not meeting value and quality.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course:
Course Contents
Section 1: Agile Project Management
Section 2: Using the Agile Manifesto to Deliver Change
Section 3: The 12 Agile Principles
Section 4: The Agile Fundamentals
Section 5: The Declaration of Interdependence
Section 6: Agile Development Frameworks
Section 7: Introduction to Scrum
Section 8: Scrum Projects
Section 9: Scrum Project Roles
Section 10: Meet the Scrum Team
Section 11: Building the Scrum Team
Section 12: Scrum in Projects, Programs & Portfolios
Section 13: How to Manage an Agile Project
Section 14: Leadership Styles
Section 15: The Agile Project Life-cycle
Section 16: Business Justification with Agile
Section 17: Calculating the Benefits With Agile
Section 18: Quality in Agile
Section 19: Acceptance Criteria and the Prioritised Product Backlog
Section 20: Quality Management in Scrum
Section 21: Change in Scrum
Section 22: Integrating Change in Scrum
Section 23: Managing Change in Scrum
Section 24: Risk in Scrum
Section 25: Risk Assessment Techniques
Section 26: Initiating an Agile Project
Section 27: Forming the Scrum Team
Section 28: Epics and Personas
Section 29: Creating the Prioritised Product Backlog
Section 30: Conduct Release Planning
Section 31: The Project Business Case
Section 32: Planning in Scrum
Section 33: Scrum Boards
Section 34: Sprint Planning
Section 35: User Stories
Section 36: User Stories and Tasks
Section 37: The Sprint Backlog
Section 38: Implementation of Scrum
Section 39: The Daily Scrum
Section 40: The Product Backlog
Section 41: Scrum Charts
Section 42: Review and Retrospective
Section 43: Scrum of Scrums
Section 44: Validating a Sprint
Section 45: Retrospective Sprint
Section 46: Releasing the Product
Section 47: Project Retrospective
Section 48: The Communication Plan
Section 49: Formal Business Sign-off
Section 50: Scaling Scrum
Section 51: Stakeholders
Section 52: Programs and Portfolios