|
Specify and review the project dates Reviewing the project dates can help you to see whether you are meeting the targeted finish date and whether you need to make any further adjustments to meet that date.
Click all of the following that apply:
Adjust the plan to meet the finish date You can use a variety of strategies, including adjusting the calendars, scope, tasks, and assignments, in order to meet the targeted finish date.
Click all of the following that apply:
Click all of the following that apply:
- Create a task calendar if the task calendars (task calendar: The base calendar that you can apply to individual tasks to control their scheduling, usually independent of the project calendar or any assigned resources' calendars. By default, all tasks use the project calendar.) that are applied to the critical path tasks are unnecessarily delaying the finish date. Modifying or removing a task calendar may have the least effect of any changes to the three types of calendars (task, resource, and project) in Microsoft Office Project 2007.
- Modify a resource calendar if the resources (resources: The people, equipment, and material that are used to complete tasks in a project.) are actually working more than their calendar reflects. For example, if the resource calendar (resource calendar: A calendar that specifies working and nonworking time for an individual resource. A resource calendar differs from a base calendar, which specifies working and nonworking time for more than one resource.) for a resource that is assigned to critical path tasks indicates a four-day workweek, but the resource actually works five days, you will probably meet the finish date.
- Modify the project calendar if the project is being worked on for more hours or days than your project calendar reflects. For example, if the project calendar (project calendar: The base calendar used by a project.) indicates that weekends are nonworking time (nonworking time: Hours or days designated in a resource or project calendar when Project should not schedule tasks because work is not done. Nonworking time can include lunch breaks, weekends, and holidays, for example.), but you actually are running weekend shifts, changing the project calendar will probably meet your finish date.
You might need to reduce the scope (scope: The combination of all project goals and tasks, and the work required to accomplish them.) to meet the finish date or the budget (budget: The estimated cost of a project that you establish in Project with your baseline plan.). Or, after building your project plan, you might have more time or money than expected. In either case, you can change the scope of the project. You can choose between changing the deliverables (deliverable: A tangible and measurable result, outcome, or item that must be produced to complete a project or part of a project. Typically, the project team and project stakeholders agree on project deliverables before the project begins.) of the product or changing the scope of the project.
For example, you decide to remove a market research task from a project, and you also reduce the duration of product testing in order to meet the finish date or budget. In this case, the end product and deliverables don't change. However, you changed the method for providing this end product by reducing the scope of the project.
Do all of the following that apply:
- Change a duration to meet the finish date by reducing the amount of time planned for critical path tasks. Be sure that the reduced duration still reflects a minimum reality. Also be sure to adjust the corresponding amount of work that is assigned to the resources.
- Remove a task to meet the finish date. Removing tasks can decrease the quality of the overall project implementation. Tasks that must be done should still be reflected in the plan, and only those tasks that are considered optional should be removed.
- Replace a resource assignment to meet the finish date. You can replace a slower resource with a faster one, such as a person with more experience, equipment with higher capacity, or material with a quicker setting time.
Click all of the following that apply:
- Show the critical path to keep an eye on the critical path and meet the finish date.
- Change when a task becomes critical if you want to change the definition of a critical task to mean, for example, a task with one or two days of slack. By default, Project 2007 considers a task to be critical if it has zero days of slack.
- Change the start date or finish date for a task if inflexible date constraints (constraint: A restriction set on the start or finish date of a task. You can specify that a task must start on or finish no later than a particular date. Constraints can be flexible [not tied to a specific date] or inflexible [tied to a specific date].) (such as Must Start On or Must Finish On) were set on tasks. When you make task constraints in the critical path more flexible, Project 2007 can calculate the schedule with fewer restrictions, and you might be able to meet the finish date.
- Change a duration for a task on the critical path to meet the project finish date.
- Split a task if the single task comprises multiple elements that can be worked on simultaneously by different resources. If you break a critical path task into these different elements with different assignments, you might be able to meet the finish date.
- Change a task link to review the relationships (or dependencies) among tasks in the critical path and to see whether there are any incorrect or unnecessary links that you can change.
- Set overlap or delay for tasks to adjust the lead and lag time between linked tasks. Adding lead time (lead time: An overlap between tasks that have a dependency. For example, if a task can start when its predecessor is half-finished, you can specify a finish-to-start dependency with a lead time of 50 percent for its successor [has a negative lag value].) between linked tasks can help to meet the finish date. Adding lag time (lag time: A delay between tasks that have a dependency. For example, if you need a two-day delay between the finish of one task and the start of another, you can establish a finish-to-start dependency and specify a two-day lag time [has a positive value].) where necessary can make the schedule more realistic.
Click all of the following that apply:
Adding more resources to tasks is called "crashing" or "compressing" the project. Taken to an extreme, crashing can be a risky way to complete a project because of the extra costs and inefficiencies that can result. If you add too many tasks, the length of the project can increase rather than decrease because of the extra complexity.
Adjust the plan to take advantage of additional time
More . . .
After you build your plan and Project 2007 calculates the schedule (schedule: The timing and sequence of tasks within a project. A schedule consists mainly of tasks, task dependencies, durations, constraints, and time-oriented project information.) and cost (cost: The total scheduled cost for a task, resource, or assignment, or for an entire project. This is sometimes referred to as the current cost. In Project, baseline costs are usually referred to as "budget.") for the project, you might have more time or an increased budget (budget: The estimated cost of a project that you establish in Project with your baseline plan.). You can choose to end the project ahead of schedule or under budget. Or you can increase the scope (scope: The combination of all project goals and tasks, and the work required to accomplish them.) and add quality (quality: The degree of excellence, or the desired standards, in a product, process, or project.) to the project deliverables.
- Check with the customers If appropriate, check with the customers or stakeholders (stakeholders: Individuals and organizations that are actively involved in the project or whose interests may be affected by the project.) to see how they prefer to use the time or budget. They might prefer to leave the plan as is and have the project come in ahead of schedule or under budget.
- Check your contract See whether there are contractual incentives (or in some cases, even penalties) for coming in ahead of schedule or under budget. The type of contract you have (fixed price, cost reimbursable, or unit price) can help you determine how you can take advantage of available time or budget.
- Add scope If you have extra time or budget available, you can add tasks (task: An activity that has a beginning and an end. Project plans are made up of tasks.) or phases (phase: A group of related tasks that completes a major step in a project.) that you wanted to implement but thought you wouldn't have enough time or money for. You can increase the duration (duration: The total span of active working time that is required to complete a task. This is generally the amount of working time from the start to finish of a task, as defined by the project and resource calendar.) on existing tasks, so that resources (resources: The people, equipment, and material that are used to complete tasks in a project.) have more time to complete them. Be aware that adding scope is likely to add both time and cost to your plan. Changing the scope and deliverables (deliverable: A tangible and measurable result, outcome, or item that must be produced to complete a project or part of a project. Typically, the project team and project stakeholders agree on project deliverables before the project begins.) may have contractual implications, so be sure to check the contract and obtain client approval when necessary.
- Raise the standard of quality You can use surplus time or budget to add tasks or phases that add or check for quality. You can increase the duration on existing tasks, so that the resources have more time to do higher-quality work. Another way to raise the quality is to add more highly skilled staff, more efficient equipment, or higher-grade materials. These types of resources can be more expensive, but they can also be a good use of surplus budget.
Enter a note about schedule changes Log information about changes that you made to meet the finish date. Such notes can be helpful when you are tracking actual progress, closing the project, or collecting data for the next project.
Evaluate the results of schedule optimization This evaluation ensures that you did indeed meet the finish date and that costs, workload, and other projects were not adversely affected by these changes.
Click all of the following that apply:
- See what's driving the project finish date to see how the changes that you made to optimize for the finish date affected the critical path. This can help you to see whether you actually achieved your goal of meeting your targeted finish date.
- Display task and project scheduling information to view the date information for your tasks and project or for projects that are published to Microsoft Office Project Server 2007.
- Review resource workloads to see whether any assigned resources are now overloaded or underutilized as a result of optimizing to meet the finish date.
Communicate the assignment changes to the resources If you assigned new tasks to the resources (resources: The people, equipment, and material that are used to complete tasks in a project.) or changed or removed existing assignments as a result of meeting the finish date, you can communicate these changes to the affected resources, either online or by printing assignment reports (report: A format in which you can print schedule information that is appropriate for the intended recipients. You can use the predefined reports provided by Project or create custom reports.).
Add supporting information about a task or resource after the project information changes Add more information in the form of notes, documents, and links to Web pages.
Click all of the following that apply:
|