Task planning

A project plan becomes useful when the team can see a concrete next task. The Project Manager creates phases to group work, tasks for the work people carry, and sub-tasks where a deliverable needs smaller steps. A sub-task points to its parent. Planned start and due date place each item in the schedule. Estimated hours give the team a planning reference; progress and status show how execution compares with that starting estimate.

Consider a product launch. Discovery, content preparation and launch can be phases. A task to approve the product page can be a predecessor of publishing it. The Project Manager records the dependency rather than relying on a note in a meeting. The Gantt timeline then gives a view of planned dates, while the Kanban board gives a view of status. The two screens answer different operating questions from the same task records.

• Hierarchy. A task type distinguishes a phase, a deliverable task and a sub-task.
• Order. A dependency relates a task to its predecessor and records the type and lag.
• Schedule. The planned start and due date bound the task’s work interval.

Agree on the level of detail that makes ownership clear. A phase alone is too broad for daily assignment; a large list of tiny steps is harder to maintain than the project itself. Decide when a task is marked Blocked and who reviews its predecessor. Set a consistent rule for moving a due date after a dependency shifts. Where a milestone is linked to a completing task, decide which task genuinely demonstrates that the checkpoint was reached.

The dependency type matters. Finish-to-start order is a common default, while start-to-start, finish-to-finish and start-to-finish relationships carry different scheduling meaning. The Project Manager should confirm the intended order with the people doing the work. A line on the Gantt is a planning aid; the owner still needs to check whether the handoff is possible.

Build a short implementation plan with a preparation task, a review task and a release task. Give each planned dates and a due date. Link review to preparation as predecessor, and link release to review. Move preparation later and check the dates of dependent work before telling the sponsor that release remains on schedule. Mark the review task Blocked when the predecessor has not supplied its input. Use Overdue Tasks and the Project Gantt to compare the same case from exception and timeline views.

• Project Gantt — Dated work laid out as a project timeline.
• Project Kanban — The same work grouped by current status.
• Overdue Tasks — Tasks needing a date or scope decision.

Break down and assign takes the plan into ownership. Run and record work covers the delivery loop.