After a project or execution is initiated, regardless of whether it is managed using the Scrum project model, the Waterfall project model, or the Kanban project model. Team members of the project or execution need to attend the product planning meeting and task breakdown.

Note: Team members here are not only developers, but also include testers, DBAs, meaning all members in the project/execution team.

How do developers determine the product backlog? How to break down tasks? Check out the video:

【视频介绍】

I. Product Planning Meeting

When attending the product planning meeting, the product manager explains the stories, story descriptions, and acceptance criteria to everyone.

Team members should fully understand the stories and express their opinions to ensure that their understanding of each story is correct. And to ensure that the entire team's understanding of the stories is consistent.

After the product planning meeting ends, the project/execution manager should maintain the stories of the project/execution.

In Project/Execution > Story, the project/execution manager links product stories or links them by plan.

When necessary, you can also click the Create Story and Batch Create Story buttons to create new stories.

If stories cannot be linked, you need to go to Project/Execution > Settings > Product to link the product first.

图1

II. Task Breakdown

After the product planning meeting ends, team members need to conduct the project/execution planning meeting.

The main task is to break down stories into tasks and estimate task hours, and all team members should participate.

After task breakdown, voluntarily claim the tasks you prefer.

After a project/execution links stories, they need to be broken down into tasks. You can break down tasks via the Batch Convert to Task button, where one story is broken down into one task, and the task name is the same as the story name. This is applicable to situations where stories are combed out in detail, story granularity is small, and stories are all broken down into the same type of tasks.

You can also break down tasks via the Breakdown Task and Batch Breakdown Task buttons in the action bar of the Project/Execution > Story list. A story can be broken down into one or multiple tasks, and multiple types of tasks.

1. Batch Convert Story to Task

On the Project/Execution > Story list page, check the stories that need to be broken down into tasks, click the Edit button, and then click the Batch Convert to Task button in the pop-up window to execute task breakdown.

图2

On the story batch convert to task pop-up page, click to select the task type.

In the synchronized fields, they are checked by default; the associated module, description, priority, cc to, and assignee information of the story will be synchronized to the task. You can also modify them according to actual needs.

图3

图4

2. Story Task Breakdown and Batch Task Breakdown

Click the Breakdown Task and Batch Breakdown buttons in the right-hand action bar of the Project/Execution story list; you can break down a story into one or multiple tasks, and multiple types of tasks.

图5

After clicking the Breakdown Task or Batch Breakdown button, it jumps to the create and batch create task page. The associated story and associated module will by default bring out the story name and story associated module information.

图6

For tasks broken down from stories using the above two methods, you can view the task information in the Project/Execution > Task list.