Project Task Structure

We're not saying that a project plan can't include more than 1000 task items and more task links. If we can spend enough efforts to plan the thousands of tasks and relationships well, we can get a “perfect” project schedule for tracking and re-scheduling.

It seems that this "perfect" plan can help us automate the heavy re-scheduling work - after the date of a task is modified, the successors change automatically according to the link constraints. So we do less job compare to manually updating related tasks as the app follows the link constraints to do the rest well.

Sounds good, but wait, let’s think a little more about this “perfect” approach.

Why do we need to spend more efforts to specify the start, finish date, the resource, the cost and the links of the tasks? Why do we not just make things simple to plan the work like managing tasks in a simple to-do list? As we are using the project schedule to guide the project team to execute the project (when, why, who and how much, etc.), to track the task progress with the team and to re-schedule the project if needed. The project team needs to follow the schedule for their daily work and needs to update the status to make the current plan reality for the coming days.

We have some suggestions to organize the tasks well when using QuickPlan

© 2013–2018 COPYRIGHT QUICKPLAN | All Rights Reserved
MOBILINKED INC.