Based on the long-term strategic direction of the product, it is put forward at the maximum granularity level, which is usually a product module that can be used independently;

Features:

As a sub-demand of an epic (more figurative than an epic), the collection of several user stories needs many rounds of iteration to complete the delivery;

User story:

From the user's point of view, it describes the user's desire to be satisfied, with the smallest granularity level, and can be developed iteratively at one time.

Task:

Demand is the user dimension, and the task is the development dimension. Requirements are a complete user story with independent functions that can be tested and delivered. A task is a specific task that is decomposed according to requirements. For example, a requirement is divided into foreground development task and background development task, and the two tasks can only be delivered after the requirement is completed. Requirements include multi-level display of father-son requirements, tree display of requirements classification, user-defined workflow status, circulation authority control, requirements statistics and so on. Tasks do not have these functions.