Create an Epic¶

(Activity) for Tier: Product

PURPOSE¶

Epics serve to provide general direction for the software project team. We create epics to represent high level contractual or portfolio requirements. Once epics have been established, the team has a foundation from which they can decompose the epics into features, user stories, and eventually tasking needed to develop the software solution and satisfy contractual and portfolio commitments.

WHEN¶

When contractual or portfolio requirements are identified and as needed throughout the product’s lifecycle.

PARTICIPATING ROLES¶

ACCOUNTABLE
- Product Owner
RESPONSIBLE
- Project Manager
- Product Owner

INPUTS¶

Contract Statement of Work, performance work statement, task order, policy , guidance, doctrine, or feedback
Project operational concept description document (Optional)

ENTRY CRITERIA¶

SUB-ACTIVITIES¶

Identify High-Level Requirements
- Review inputs in order to identify specific high-level requirements related to documentation, training, or other operational scenarios, such as security, how users will interact with the system, expectations for support, etc. related to the system/project.
Create Epics
- Create epic(s) based upon identified conceptual solutions, ensuring they are sufficient to invoke conversation, and provide traceability to the source input.
Refine Epics
- Product owner and stakeholders collaborate to update epics.

OUTPUTS¶

Refined Product Backlog

EXIT CRITERIA¶

Epics have been created, added to the Product Backlog, and are ready to be consumed for further elaboration and traceable decomposition into User Stories and other derived work items.

NEXT ACTIVITY¶

Create Feature