Steps
For each step, output the title first, then output the result
-
Read the design document: read the output document from the software design phase to obtain the module division and module dependency relationships
-
Decomposition: break each module down into small features until each task can be developed and reviewed independently
-
Granularity check: check whether each task can be completed within one development iteration; continue splitting tasks that are too large
-
Dependency relationships: based on the module dependency relationships, use a table to mark the dependencies between tasks. Tasks without dependencies do not need to be listed. Example:
Task Dependency Login Registration Place order Login, payment interface -
Output the task list: list all tasks and the dependency relationship table, and wait for developer confirmation
Notes
- Independence: each task can be independently developed, reviewed, and merged
- No circular dependencies: there must be no circular dependencies between tasks