Creating sub tasks in microsoft project 2010

Each individual project contains a critical path. Consolidating multiple projects into one master project makes it easy to see the overall picture as multiple critical paths in the master project while retaining separate critical paths for each subproject. Link projects to create a master project. See what's driving the project finish date critical path. When you insert a subproject into a master project, the subproject is represented as a summary task in the task list and a Project icon indicator appears in the Indicators field.

The subproject is indented at the outline level of the row where you insert it, but you can indent or outdent it just as you would any other task. Because the subproject is represented as a summary task, you can't edit its summary information, but you can expand the outline to show the subproject's tasks and edit the project information in the master project file.

Note: Any formatting you have applied to summary tasks or Gantt bars in a subproject does not appear in the master project. Formatting information is stored in each file and must be applied separately to the master project. When you save the master project, changes to the subproject are saved in the subproject's source file as well. If you want to work directly in the source file without opening the master project file, changes to the subproject's source file are updated automatically in the master project file.

Note: If you no longer need to keep the master project and subproject synchronized, you can unlink them. Then, if changes are made to either the subproject or the master project, the other file remains unchanged.

After you consolidate files into a master project file, the resources for both files remain separate, just as the tasks in a subproject remain in the subproject. You can change resource information in the master project and the changes will be replicated in the subproject's source file. You can view all resources in the master project and subprojects together in the Resource Sheet view, but you can't assign a resource to any project other than the subproject it came from.

Note: If the same resources are used in multiple subprojects, you see duplicate resource names because the resources are not combined. However, if you want to assign the resources in different subprojects and resolve duplicate resource names, you can combine them in a resource pool and make them available to the other files. Consolidate unrelated files.

Create a workspace for project files. Master projects and subprojects let you create a hierarchy of projects that reflect the relationship between them and, in some cases, the structure of your organization.

But you may have other reasons to consolidate project files. For example, you may want to combine them temporarily for a quick review or for printing. Use consolidated files if you have multiple files you would like to combine in one window, whether the files are related or not.

Combining unrelated files in a consolidated project makes it easier to see information from multiple projects in various views and to print them. You might consolidate project files if you must keep track of many ongoing projects, such as when you are developing different products at the same time.

You can sort and group by product names, project deadlines, and managers in order to find and evaluate the specific information that you need. For example, you can print a Gantt Chart view that includes all your projects.

An alternative to consolidating projects is to create a workspace that contains individual project files, each open in its own window. Use a workspace if you work with the same project files frequently and don't want to consolidate them into one big project. When you open the files and then save them as a workspace, Project saves the files and their current settings in a single workspace file.

Then when you open the workspace file, you open all the included files at the same time. Each project has its own button on the taskbar, making it easy to switch from one project to another. Need more help? Expand your skills. This is a good example of how it should turn out.

Every task has a predecessor and they are all FS0 predecessors. Every task It also has some small faults. See if you can find the two tasks which do not have successors. Every task should have a successor, and it is easy to see what the successors for those two tasks should be. First, all tasks must be auto-scheduled. At 74, 'Demolition' is a good main summary Then 75 should be 'Windows Demolition', not just 'Windows'. Estimate the duration of the tasks. Do not type in dates.

Ignore what you think the duration of the summary at 75 will be. Learn how to add or hide them. Learn more. When organizing the tasks for a project, you should plan the outline for the project in one of two ways; the top-down method or the bottom-up method.

With the top-down method, you identify the major phases first and then break the phases down into individual tasks. The top-down method gives you a version of the plan as soon as you decide on the major phases. With the bottom-up method, you list all the possible tasks first, and then you group them into phases.

You can include the project as a summary task. When you move or delete a summary task, Project moves or deletes all of its subtasks. Before you delete a summary task, outdent the subtasks you want to keep. You can change the duration of a summary task without changing each subtask.

But be careful — changing the duration of the summary task does not necessarily change the durations of the subtasks.

Avoid assigning resources to summary tasks. Assign them to the subtasks instead, or you might not be able to resolve overallocations. Create and work with subtasks and summary tasks in Project desktop.