Team execution

A task can have more than one assignee. The assignment record identifies which person is primary, so collaboration does not blur who carries the result. Team members move task status as work starts, enters review, becomes blocked or finishes. The task’s due date and estimate remain visible beside those changes. A task comment records the conversation; an attachment keeps a deliverable close to the work it supports. A time entry records the day and hours spent on the task and project.

For an internal rollout, one team member may draft a training guide while another reviews it. The primary assignment names who will see it through. If the guide needs a decision, the member can place the task in review and use a comment to explain what is ready. If a dependency is missing, mark it blocked and tell the Project Manager what decision or input is needed. The task stays in the project plan rather than disappearing into private messages.

• Assignment. An assignment links a person to a task and marks the primary owner.
• Progress. The task carries status, percent complete and completion date for the work item.
• Evidence. Comments, attachments and time entries hold discussion, files and effort.

Set a simple rule for when work moves into review and who resolves comments. Agree on the level of time detail the team needs: a daily entry with hours and optional notes is available, but the project should not ask people to reproduce every conversation. Decide how files will be named and which attachments belong on the task rather than inside a comment. For guest collaboration, review project membership and the task scope before inviting an external person.

A team member who changes the due date should coordinate with the Project Manager when downstream tasks or milestones depend on it. The Kanban shows current state, while the Project Gantt shows the planned date span. Looking at both helps distinguish an item moving across status columns from a plan that has slipped.

Assign a preparation task to a primary owner and a collaborator. Ask the primary owner to start it, post a short progress comment, attach a draft and log the hours spent. Ask the collaborator to respond in the task thread. Move the task into review, then complete it when the work has been checked. Inspect My Tasks for the assignee and My Time Entries for the person who logged time. Finally, review the task’s actual hours beside its estimate. This is an effort comparison, not a billing event.

• My Tasks — Assigned work for the current person.
• Project Kanban — Task state across the project.
• My Time Entries — Hours the person recorded against tasks.

Run and record work follows this daily loop. Review and close covers the manager’s later decision.