This comprehensive prompt will help you systematically assess and analyze any Agile epic, ensuring that all essential aspects are considered during the planning and execution stages.
[PROMT TEMPLATE]
I’m going to give you an agile epic to analyze based on the following criteria
Epic Analysis Prompt:
- Epic Title: Is the title clear, concise, and reflective of the epic’s content?
- Epic Description: Does the description provide a comprehensive overview of the epic’s purpose and objectives?
- Epic Statement: Does it include a clear epic statement in the format ‘As a [user persona], I want [need/goal] so that [benefit]’?
- Business Objective: Is there a specific business objective associated with the epic?
- Measurable Outcome: Are there clear KPIs or metrics linked to the desired results?
- Market Trends/Competitor Analysis: Have industry trends and competitor analysis influenced the epic’s objectives?
- Technical Feasibility: Is there an assessment of the technical feasibility to determine if the required technical aspects can be integrated or implemented effectively?
- Dependencies: Are dependencies clearly stated, and is there a plan for managing or resolving them?
- Estimate: Is the effort and time estimate detailed enough for prioritization and planning?
- Priority: Does the epic effectively communicate its priority relative to other work items?
- Status and Progress Tracking: Is there a method for tracking progress?
- Definition of Done (DoD): Does it specify when the epic can be considered complete, including quality standards and other requirements?
- Non-Functional Requirements (NFRs): Are non-functional requirements, if relevant, included?
- Roadmap Alignment: Does the epic align with the product roadmap and release planning?
- Stakeholder(s): Are the relevant stakeholders and user personas identified?
- Alignment with Company Values/Principles: How does the epic align with the organization’s values and principles?
- High-Level Tasks/User Stories: Are there high-level tasks or user stories for breaking down the epic?
- Additional Considerations: Are there any unique aspects or elements within the epic that deserve special attention?
- Conciseness: Is the epic concise while still providing all necessary details?
- Template Consistency: Does the epic follow the organization’s standardized template for consistency in documentation?
- Risk Assessment: Assess potential risks and challenges associated with the epic’s implementation. Identify and document the risks that could impact the successful delivery of the epic.
- Resource Allocation: Evaluate the availability of resources, including personnel, technology, and budget, required for the epic’s execution. Ensure that resource constraints are addressed.
- Change Management: Determine how changes resulting from the epic’s implementation will be managed, communicated, and documented. Consider impacts on users, stakeholders, and existing processes.
- Regulatory Compliance: If the epic involves data handling, privacy, or other regulatory considerations, assess compliance requirements and ensure that the epic adheres to relevant regulations and standards.
- User Acceptance Testing (UAT): Outline the plan for conducting user acceptance testing, including criteria for success and the involvement of end-users in validating the epic’s functionality.
- Documentation Plan: Specify how documentation related to the epic, such as user guides or technical documentation, will be created, updated, and maintained.
- Release and Deployment Strategy: Describe the strategy for releasing and deploying the epic, including considerations for staging environments, deployment windows, and rollback plans.
- Training and Onboarding: If applicable, outline plans for training users, support teams, or other relevant stakeholders on the epic’s features and changes.
- Feedback and Continuous Improvement: Detail how feedback from users and stakeholders will be collected, analyzed, and used to iteratively improve the epic’s functionality and user experience.
- Post-Implementation Review (PIR): Plan for a post-implementation review to evaluate the success of the epic in achieving its objectives and to capture lessons learned for future projects.
- Accessibility: If the epic impacts user interfaces, consider accessibility requirements to ensure that the system is usable by individuals with disabilities.
- Scalability: Assess the system’s scalability to accommodate potential growth in users or data volume resulting from the epic’s implementation.
- Sustainability: If the epic introduces new processes or technologies, consider sustainability aspects, such as energy consumption or environmental impact.
- Legal and Intellectual Property: Ensure that legal aspects, including intellectual property rights and licensing, are addressed, especially if the epic involves third-party components or integrations.
- Data Migration and Retention: If applicable, plan for data migration and retention, ensuring that data is migrated correctly and that retention policies are followed.
- User Communication: Develop a plan for communicating changes and updates related to the epic to end-users, stakeholders, and support teams.
— “Please enter the Epic you would like to analyze to begin”