Project team members can maintain focus on their work by viewing it as a separate file, and the project manager who controls the master project can coordinate each subproject team's schedule. But often a project is part of a larger program that upper-level managers may need to manage. Ideally, a project file is owned, managed, and modified by a single project manager. The resulting structure of subprojects should reflect the priorities and responsibilities of your team members, as well as the interrelationships between tasks in different areas and the overall deadline. You can accurately reflect the hierarchy of multiple projects by inserting various projects into other files. Creating dependencies between projects makes it easier for different project managers to see how work by other project managers affects their schedules. If the projects are interrelated, the project manager can create task dependencies between tasks in different projects. This approach also makes it easier to generate reports on multiple projects. Instead of opening them one by one, you can open all the subprojects at the same time when you open the master project. Project managers may have a set of projects they work on all the time, whether the projects are interrelated or not. If top-down planning is the norm, you may want to reorganize the initial plan into subprojects when it is implemented so that individual project managers or teams have access to, and control over, their own schedules. If lower-level managers are responsible for, and know which tasks are needed on the project, it may make more sense to enable them to plan their teams' work and then consolidate their project files into a master project. You want to increase the effectiveness of your organization's planning methods. In a decentralized or distributed organization, a master project and subprojects give workers more control over their own work than one centralized project file does. A single file is almost always the faster alternative, but being able to focus on just a part of the project may be worth the trade-off. If some parts of the project contain work that is broken down into more detail than others, it may make sense to make those parts into subprojects so that most users see only a rolled-up description of the subproject, but interested parties can view it in more detail. If your project contains more than a few hundred tasks, breaking it into subprojects can make it easier to manage. To determine whether you should break up a large project into a master project and subprojects, consider the following: In Project terms, creating subprojects in a master project helps project managers gain access to, and control over, their parts of the schedule. In project-management terms, assigning subprojects in this manner gives responsibility to those who do the work and matches authority with accountability. If you just must combine files to create a report or print a view of combined-project information, you can also consolidate them temporarily in a view.Ĭreating a master project and subprojects lets you break down a large project and delegate its parts to the necessary people. When you update a subproject from the master project, it is updated in its source file as well. When you insert a subproject into the master project, the two projects are linked and you can view all the information in the subproject from the master project. In the master project, subprojects appear as summary tasks that you can easily arrange in an outline.Ĭlick the plus sign next to a subproject to expand that subproject's tasks for viewing.Įach subproject represents a different phase or other functional group in the main project. When you insert a subproject, a small Project icon distinguishes it from summary tasks that are part of the master project. Projects inserted into a master project are called subprojects. Think of a master project as a collection of consolidated projects that show a hierarchy among multiple related projects. How resources are affected when you combine files Work with subprojects in a master project You can have more control over your project by creating smaller projects in Project and then linking them into a single Project file to show where they fit in your master project. Before you know it, a simple building project becomes a collage of smaller projects, such as design, excavation, foundation work, and marketing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |