We are not saying that a project plan cannot contain many tasks and even more task links. Suppose we can put enough effort into planning the thousands of tasks and relationships well. In that case, we can get a "perfect" project plan for tracking and rescheduling.

It seems that this "perfect" plan can help us automate the heavy rescheduling work. After changing the date of a task, the successors will change automatically according to the link constraints. So we need to do less work than updating related tasks manually because the app follows the link constraints to do the rest well.

Sounds good, but wait, let's think a bit more about this "perfect" approach.

Why do we have to put so much more effort into specifying the start date, end date, resource, cost, and task links? Why don't we make it easy to schedule work, like managing tasks in a simple to-do list? Since the project plan is a guide (what, when, to whom, how, and how much. See why we chose the project plan app) for the project team to execute the project. We need to track task progress with the team and reschedule the project as required. The project team needs to follow the schedule for their daily work and update the status to achieve the current plan for the upcoming days.

• Is the schedule convenient enough to update the task status when discussed with the team?
• Is the cost acceptable for management to change something when the link needs to be broken? It's telling when you find that you have to spend hours rebuilding the plan to accommodate just the change of one task because many tasks are linked, and one task impacts many others.
• We can trust the app, but can we believe the result of the rescheduling? After you change a task, the app correctly changes the date of the linked tasks. That sounds good, but do you believe the new plan is the right one with the right resource allocation, duration, and cost?
• It's super time-consuming to create the perfect task links to ensure everything is correct after it's in place. The new plan still meets the balance of resources, keeps the low cost and short duration. The reality is that most of the time, we still have to manually check the result after the "perfect" linkage has gone into effect.
• Is the schedule a clear map in your mind? Also, can your team members get going quickly? Since we have a "perfect" and complicated schedule document, we have to review it every day before doing anything. Every time there is an unexpected change, we have to review the documents. It can take a long meeting because we have no idea what will happen. How can the organization handle risk and change when the project team has no idea of the tasks ahead?
• Is it a good practice to display too many tasks together on an iOS device? QuickPlan is indeed the most fluid Gantt chart app that has no performance issues. But navigating a list with thousands of items is still not a good practice, alternatively on a Mac device?

We have some suggestions to keep tasks well organized when using QuickPlan.

• Organize the tasks well into groups. This can help the team understand the plan quickly and significantly improve the efficiency of project maintenance, as QuickPlan supports moving the entire group at the same time.
• Organize the tasks into main projects and sub-projects. It is not a good practice to include many tasks in a single project. Although QuickPlan works great for a large project with thousands of tasks, we still recommend creating separate minor projects. For example, less than 200 tasks in each project.
• Depending on the situation, if the project team includes multiple sub-teams, you may prefer to plan each sub-team in a child project. This approach is suitable for working with each subteam separately (especially if the organization is decentralized).
• Try to eliminate cross-group dependency relationships between tasks. Too many cross-group links make the schedule confusing.
• Depending on the situation, if the project has some large phases, I prefer to organize the massive project phases into subprojects.
• If possible, and if the project is not that complicated, avoid task linkages and organize tasks well into groups. Moving task groups around for rescheduling is more intuitive than depending on task links. (As described above, even when using task links for rescheduling, we need to check if the new plan is the right one).
• Pay attention to task links, especially if there are long task link chains. The app can correctly update the time of linked tasks. However, linking constraints don't help balance resources and don't fix other problems simultaneously. We may find that we have great difficulty in making the plan reasonable in all aspects if we change only a tiny part of the project.
• If we find that we have to arrange tasks in many levels of outline, there may be much room for us to improve the task structure.
• Let the project plan focus on scheduling. Suppose we find that we need to write long and complicated task descriptions in a project plan. In this case, we need to consider how to improve the work for other project documents. A project plan is just one of the project documents that does not replace the requirements document or a design document, or a test case document.
• A long task name, while correct, can cause more problems when communicating with team members and reporting. A short task name with a slightly longer note may be better.
• Let team members be flexible in managing their very short task durations and ensuring the project plan is accurate but straightforward enough.
  
  Give an example to implement a feature. We can create a "perfect" schedule with some small tasks AND links (e.g., the tasks like "Feature xxx coding," "Feature xxx self-testing," "Feature xxx code submit," "Feature xxx ...", and the links between the tasks. You will find that you can make the simple work plan "perfect" if you want to and have enough time). However, in most cases, we will see that it is better to combine some small tasks assigned to the same project member into one task. The project manager may need to sit near the members to adjust the project plan because these "perfect" small tasks cause many changes.
• Use tools like Agile Board to manage tasks on very short notice. It helps make the plan more transparent, simple, and real if you use other appropriate tools to manage the easily changeable parts.
• You may need to find a balance between accuracy and administrative effort. If possible, let your team members be flexible in managing the details.