After a project or execution is initiated—regardless of whether it is managed using the Scrum, Waterfall, or Kanban model—all team members in the project/execution should participate in the Product Planning Meeting and the subsequent task breakdown activities.

Note: “Team members” here are not limited to developers. They also include testers, DBAs, and any other roles involved in the project/execution team.

How do R&D team members identify the product backlog items and break them down into tasks? Watch the video: [Video link—Sanplex version to be provided]

视频介绍

1. Product Planning Meeting

During the Product Planning Meeting, the Product Manager walks the team through the requirements, including the requirement description and acceptance criteria.

Team members should ensure they fully understand each requirement and share their feedback to confirm that: their understanding of every requirement is accurate; and the entire team has a consistent understanding of the requirements.

After the meeting, the Project/Execution Lead should maintain the requirements within the project/execution.

In Project/Execution > Requirements, the Project/Execution Lead can link product requirements to the project/execution (or link them according to the plan). If needed, click Create Requirement or Batch Create Requirements to create new requirements.

If you cannot link requirements, go to Project/Execution > Settings > Products first and link the product to the project/execution.

图1

2. Break Down Tasks

After the Product Planning Meeting, the team should hold a Project/Execution Planning Meeting.

The main objectives are to:

• break requirements down into tasks;
• estimate task effort (man-hours);
• ensure full-team participation.

After tasks are broken down, team members can volunteer to pick up the tasks they prefer.

Once requirements are linked to a project/execution, they must be broken down into tasks. You can do this in either of the following ways:

• Use Batch Convert Requirements to Tasks when one requirement maps to one task, and the task name matches the requirement name. This works well when requirements are already refined in detail (small granularity) and each requirement is decomposed into a single task type.
• Use Decompose Tasks or Batch Decompose Tasks in the requirements list to split one requirement into one or multiple tasks, including different task types.

2.1 Batch Convert Requirements to Tasks

On the Project/Execution > Requirements list page, select the requirements you want to break down, click Edit, and then click Batch Convert to Tasks in the pop-up window.

图2

In the “Batch Convert Requirements to Tasks” pop-up window, select the task type.

Under Fields to Sync, all options are selected by default. The requirement’s module, description, priority, CC, and Assignee will be synchronized to the task. Adjust these options as needed.

图3

图4

2.2 Decompose Tasks / Batch Decompose Tasks

In the action column on the right side of the Project/Execution > Requirements list, click Decompose Tasks or Batch Decompose Tasks to break a requirement down into one or multiple tasks of different types.

In the action column on the right side of the Project/Execution > Requirements list, click Decompose Tasks or Batch Decompose Tasks to break a requirement down into one or multiple tasks of different types.

图5

After you click Decompose Tasks or Batch Decompose Tasks, you will be redirected to the Create Task or Batch Create Tasks page.

The related requirement and its module are auto-populated by default (including the requirement name and module information).

图6

Tasks created using either method can be viewed in Project/Execution > Tasks.