Microsoft Office Tutorials and References
In Depth Information
Entering a milestone task
For complex, long-duration projects or projects involving a large number of
unknowns, you might be able to make detailed duration estimates only of tasks to be
started and completed soon (for example, within two to four weeks). You then might
have only very general duration estimates for tasks that will start later (for example,
after two to four weeks). You could hold a recurring task-duration estimating session
with the team in a regular cadence as time progresses.
For complex projects, you probably would combine these and other strategies to
estimate task durations. Because inaccurate task duration estimates are a major source
of risk in any project, making good estimates is well worth the effort expended.
Entering a milestone task
In addition to entering tasks to be completed, you might want to account for an important
event for your project’s plan, such as the end of a major phase of the project. To do this,
you will create a milestone task.
Milestones are significant events that are either reached within the plan (such as the
completion of a phase of work) or imposed upon the plan (such as a deadline by which
to apply for funding). Because the milestone itself doesn’t normally include any work,
milestones are represented as tasks with zero duration.
The scenario: At Lucerne Publishing, you just learned the date by which the new book
launch’s planning activities needs to be completed for the book launch to occur on time.
You want this date to have visibility in the plan.
In this exercise, you create a milestone task.
Click the name of task 3, Public Launch Phase .
On the Task tab, in the Insert group, click Milestone .
Project inserts a row for a new task and renumbers the subsequent tasks. Project
names the new task <New Milestone> and gives it a zero-day duration. As with
the other new tasks, the milestone is initially scheduled at the project start date of
January 5.
Search JabSto ::

Custom Search