Develop Epic(s)

This step uses the Project Vision Statement to outline broad, high-level, and still unrefined user stories known as Epics. The team may hold User Group Meetings to gather insights and shape these Epics.

Key Points

  • The Project Vision Statement guides and aligns the creation of Epics with business goals.
  • Epics are large, coarse-grained user stories that will be split into smaller, detailed stories later.
  • User Group Meetings and stakeholder workshops help discover, validate, and clarify Epics.
  • Epics seed the product backlog and roadmap and are refined during backlog grooming and sprint planning.

Example

A team building a mobile banking app reviews the vision "Deliver secure, convenient banking anywhere." They draft Epics such as "Mobile account onboarding," "Funds transfer," and "Card management." They host a User Group Meeting with customers and support staff to capture needs, confirm priorities, and refine the scope of each Epic before breaking them into smaller user stories.

PMP Example Question

Using the Project Vision Statement, a product team creates broad, high-level user stories and consults customers in a User Group Meeting. Which process are they performing?

  1. Develop Epic(s)
  2. Create Product Roadmap
  3. Prioritize Product Backlog
  4. Define Definition of Done

Correct Answer: A - Develop Epic(s)

Explanation: Developing Epics translates the vision into large, unrefined user stories, often with input from user groups, before decomposition into smaller stories.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Run the drill before the incident runs you

Design a 15-minute drill, build a full tabletop and run the room before an incident tests your team. ICS/OT Incident Drills and Tabletop Exercises includes 51 lessons, eight quizzes, four hands-on assignments and the exercise materials, delivered through HKSM Courses for US$47 one-time. 30-day money-back guarantee when 50% or less of the course has been consumed.

Explore the Course