1. What is an epic?
Before discussing epics, let's briefly review project management. Project Management (PM for short) combines agile development concepts to help users realize product iterations, and provides functions such as demand control, task collaboration, and defect tracking, which can effectively control project progress and help teams improve R&D efficiency.
Then an epic is a relatively large function or feature, which generally requires multiple iterations to complete. It can be used to create, modify, delete, and associate requirements, tasks, defects, and other matters. When actually decomposing tasks, epics can generally arrange tasks on a quarterly basis, and iterations can be allocated on a monthly basis.
Epic elements (may be greater than) :
- Title: The name of the epic
- Description: Introduction to the epic
- Person in charge: the person in charge of the epic matter
- Priority: Usually divided into Urgent, High, Medium, and Low
- Affiliated project: Create an epic under a specified project
- Labels: Usually divided into five categories: product planning, user feedback, internal demand, competitive product research, and others
- Attachment: Additional Notes on the Epic
2. What is the content of iteration?
Iteration is to subdivide the project according to the established cycle delivery plan. It can create, modify, delete iterations, and realize the management and control of various matters such as requirements, tasks, and defects.
1. Requirements
Requirements refer to software functions that can solve user problems or achieve specific goals, and can realize the management and control of demand assignments, transfers, splits, comments, etc. Contains the following elements (can be greater than)
- Title: The name of the requirement
- Description: Brief introduction of the requirement
- Person in charge: the person in charge of the demand item
- Priority: Usually divided into Urgent, High, Medium, and Low
- Belonging project: Create requirements under a specified project
- Milestone: planning to a certain milestone
- Iteration to which it belongs: planning to be part of an iteration
- Participants: Personnel in various roles participating in the requirements discussion
- Start and end time: custom start and end time
- Labels: usually include product planning, user feedback, internal requirements, competitive product research, and other five types of default labels
- Attachments: Additional instructions for requirements.
2. Task
A task refers to a specific activity to achieve a certain goal, which can realize the control of task assignment, transfer, split, comment and other content. Contains the following elements (can be greater than)
- Title: the name of the task
- Description: Brief introduction of the task
- Person in charge: the person in charge of the demand item
- Priority: Usually divided into Urgent, High, Medium, and Low
- Belonging project: Create a task under a specified project
- Milestone: planning to a certain milestone
- Iteration to which it belongs: planning to be part of an iteration
- Participants: Personnel of various roles participating in the task discussion
- Start and end time: custom start and end time
- Labels: usually include design, development, deployment, testing, documentation, product default labels
- Attachment: Additional instructions for the task.
3. Defects
Defects refer to the planning content that does not match the original definition. The coverage includes bugs, usability, etc., and can realize the management and control of defect assignment, transfer, splitting, and commenting. Contains the following elements (can be greater than)
- Title: The name of the bug
- Description: Brief description of the defect
- Person in charge: the person responsible for the defect
- Verifier: The person who checked the defect
- Priority: Usually divided into Urgent, High, Medium, and Low
- Belonging project: Create a task under a specified project
- Milestone: planning to a certain milestone
- Iteration to which it belongs: planning to be part of an iteration
- Severity: Typically includes Critical, Critical, Average, Minor
- Defect type: usually includes functional defects, UI interface problems, usability problems, security problems, performance problems default options
- Participants: Personnel in various roles participating in the defect discussion
- Start and end time: custom start and end time
- Labels: usually include Valid Issue, Duplicate Issue, Not Issue, Not Reproduced, Other Default Labels
- Attachment: Additional instructions for the task.
Epic: is a feature set or a large user story, but too granular to fit in a sprint, it can be broken down into many smaller stories; story:
is a brief user requirement, small enough to fit in a sprint;
task : It is a procedural work to complete user needs, indicating the completion of user story development tasks;
subtasks: subtasks are usually specific splits of stories or tasks, undertaken by a single person, and can usually be completed in a short period of time;
defects: Mainly for defects in testing or defects in released versions;