After tasks have been broken down for a project/execution, team members should claim (take ownership of) the tasks they want to work on and begin daily development activities.

In addition to daily coding work, team members should update task status and log effort on a daily basis to keep execution tracking accurate.

To learn how to claim tasks in Sanplex, watch the video: [Video link—Sanplex version to be provided]

视频介绍

1. Claim Tasks

Following Scrum principles, team members are encouraged to choose tasks they prefer, which helps improve ownership and team engagement.

Some users may ask:

• What if no one claims a task?
• What if everyone only picks easy tasks?
• What if a newcomer selects a critical task?
• What if workload distribution becomes uneven?

In practice, these are manageable because task information is transparent and visible to the team—an individual cannot consistently select only easy work every iteration. That said, macro-level coordination by the Project/Execution Lead remains important. Critical tasks often require balancing and, when necessary, targeted assignment.

In Sanplex, tasks can typically be claimed in two ways: Assign or Edit.

1.1 Assign a Task

You can use Assigned To in the task list, or the Assign action on the task detail page.

In the task list, click Assigned To to assign a task or change the assignee.

图1

On the task detail page, click Assign in the action bar to assign the task.

图2

In the Assigned To field, select a member of the project/execution team.

图3

1.2 Edit a Task

Click Edit in the action column on the right side of the task list, or click Edit in the task detail page action bar. Then set Assigned To on the right side of the edit panel/page.

图4

This method can also be used to assign a task or change the assignee.

图5

When the current user views the task list, tasks assigned to them are highlighted by assignee. Users can also filter tasks using the Assigned to Me label.

图6

You can also view tasks assigned to you via Dashboard/My > To Do > Tasks.

图7

2. Update Task Status

• Tasks in Started status also provide Pause.
• Tasks in Paused status provide Resume.
• Only Started tasks can be paused, and only Paused tasks can be resumed.

Sanplex also supports a common workflow: when a task is finished, it is automatically reassigned back to the task creator for verification. The creator can then:

• Close the task if it meets the completion criteria; or
• Activate the task if it is not truly complete.

3. Update Effort Logged

In addition to updating status, you should keep task effort information up to date:

Original Estimate: the initial estimate entered when the task was created. After the task starts, this value should not be changed. After completion, compare it with Total Consumed to calibrate future estimates.

Total Consumed: the total amount of time actually spent on the task.

Remaining Estimate: how much time you estimate is still needed to complete the task. If Remaining Estimate = 0, it indicates the task is complete.

Important note: Original Estimate ≠ Total Consumed + Remaining Estimate.

You should update tasks daily because the burndown chart is typically calculated using the Remaining Estimate field.

You can log effort via the Log Effort (or Effort) button in the task list action column, or the Log Effort (or Effort) action on the task detail page.

图8

When logging effort, fill in Total Consumed and Remaining Estimate, and briefly describe the work performed in Comment/Remark.

图9

4. Commit Code

After implementing requirements or fixing bugs, developers should commit their code.

Under Project/Execution > Code, Sanplex provides repository capabilities for browsing and reviewing code associated with the project/execution.

图10