Today’s video introduces a ChatGPT Prompt Template, revolutionizing the way we create epic stories. Ideal for product managers, it streamlines gathering crucial information for epic creation. Simply input the prompt, and ChatGPT guides you through key questions, allowing responses at your pace. You can skip or request ideas for any question. The outcome? A concise, customized first draft of your epic, adaptable for your company’s unique product features. Dive in and simplify your epic creation process!

 

ChatGPT Interative Agile Epic Createion Prompt Template

[ENTER EVERYTHING BELOW INTO THE PROMPT]

Let’s Collaborate on an Agile Epic Creation 

ChatGPT, we will work together to create an Agile epic. I’ll guide you through a series of questions for a product manager, one by one, to gather all the necessary details. These questions will help us define and document the epic effectively. When you write each question give it a unique number starting with 1 and write the number and title of the question in bold font. After each question wait for the answer and I will prompt you to ask the next one. If the user asks to skip or ignores a question, move on to the next question. If the user asks you to help with the answer, provide a suggestion, ask the user if they would like to use your suggestion, and move on to the next questions. Once we have all the information, we will compile it into a complete epic. 

  1. Title of the Epic: What is a concise and descriptive title for the epic that encapsulates its essence, with a focus on the main feature or goal?
  2. Epic Summary: Let’s provide a comprehensive overview and description of the epic.
  3. User Persona: Can you describe the primary user or customer persona for whom this epic is intended? Include their characteristics, behaviors, and specific needs.
  4. Epic Purpose: Define the purpose of this epic. Please provide an epic statement in the format ‘As a [user persona], I want [need/goal] so that [benefit].’
  5. Business Justification: What is the business justification for this epic? Why is it necessary, and how does it align with our broader business goals and objectives?
  6. Specific Stories: Are there specific stories required for this epic? Break down the epic into smaller, manageable user stories that detail specific functionality or features required.
  7. Acceptance Criteria: What are the acceptance criteria for this epic? List specific, measurable, and testable conditions that must be satisfied for completion.
  8. Value Proposition: Articulate the value this epic will bring to the user or the business to understand its priority against other work.
  9. Outcomes and KPIs: What outcomes are we aiming to achieve with this epic? Link them to KPIs or other performance metrics if possible.
  10. Dependencies: Are there any dependencies, such as external processes, features, or teams, that the implementation of this epic relies on?
  11. Assumptions and Risks: What assumptions are we making, and what potential risks could impact the delivery of this epic?
  12. Effort and Time Estimate: Provide a rough estimate of the effort and time required for this epic to help with prioritization and planning.
  13. Progress Tracking: What method should we use to track the status and progress of this epic as work on it continues?
  14. Definition of ‘Done’: How will we define ‘done’ for this epic? What quality standards and requirements must be met?
  15. Non-functional Requirements: Are there any non-functional requirements, such as performance, security, and usability, that we need to consider for this epic?
  16. Roadmap Alignment: How does this epic fit into our product roadmap and release planning? Is it aligned with a particular phase or release?
  17. Technical Requirements: What specific technical requirements or standards must the solution adhere to?

 

  1. Development Team Resources: What are the Details of any specific resources (like tools, technologies, or additional personnel) required by the development team?
  2. Design Specifications: Are there any user interface, user experience, and other design-related specifications?
  3. Stakeholders: Identify the stakeholders interested in this epic, both internally and externally. List the relevant user groups and individuals.
  4. Feedback Process: Finally, what is the process for obtaining and incorporating feedback from users or stakeholders during or after the epic’s development?

 

After we have answered all these questions, I will compile the information into a complete and concisely written best practices Agile epic that includes only the answers provided by me in this process. 

 After we have compiled the information into a complete epic I will ask “Would you like me to rewrite the epic using your original full answer text for each question for your records?” 

Now, let’s begin with the first question.