Archives
- April 2012
- January 2012
- December 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- October 2008
- September 2008
- August 2008
-
Summary Task versus Milestone
1 CommentBY: Collin Quiring
This is a quick primer on the difference between a summary task and a milestone task.
In the Project Management Body of Knowledge (PMBOK), version four, the term “Summary Activity” is defined as: “A group of related schedule activities aggregated at some summary level, and displayed/reported as a single activity at that summary level.” And, a “Milestone” is defined as “A significant point or event in the project.”
A milestone is usually used to indicate when a specific phase or group of tasks is to be completed. It can be considered a deadline date. It is possible to have numerous milestones in a schedule. While a milestone can be assigned a resource that is responsible for its completion, it is more common to use the milestone without resources. This is because the milestone is often a successor to a number of other tasks that all have to be completed prior to its completion.
In Project Professional, a milestone is what the system automatically creates when a task is given a zero duration. To add a deadline date to the milestone task there is an option to add that date in the task information.
A summary task is just that – a task that summarizes another set of tasks. Normally, the summary task is not assigned a resource. This is because the summary task’s start and completion dates are derived from the earliest subtask’s start date and latest subtask’s finish date. As each task is completed, the summary task’s overall completion is updated as well. Normally, a summary task is not linked to other tasks. Using summary tasks makes reading a WBS (Work Breakdown Structure) easier when using a logical grouping. Creating a WBS usually involves determining the summary tasks and then the subtasks to complete them but it is possible to put all the tasks into a WBS and then determine the summary tasks later.
In Project Professional, the subtasks are indented and that makes the summary task bold and outdented. Many levels of summary and subtasks can be created.
Just as a reference point, here are the definitions as defined by Microsoft. For Microsoft Project, a milestone is defined as: “A milestone is a reference point that marks a major event in a project and is used to monitor the project’s progress. Any task with zero duration is automatically displayed as a milestone. You can also mark any other task of any duration as a milestone.” And, a summary task is defined as: “When organizing the tasks for a project, you can group the tasks that share characteristics or that will be completed in the same time frame under a summary task….You can use the summary tasks to show the major phases and subphases in the project. Summary tasks summarize the data of their subtasks, which are the tasks that are grouped beneath them.”
Published on October 6, 2009 · Filed under: Enterprise Project Management, Microsoft Project; Tagged as: Deadline, Microsoft, Milestone, PMBOK, Project, Summary, Task
One Response to “Summary Task versus Milestone”
-
jamesparker said on October 9th, 2009 at 1:55 pm
In the project management the layout you have shown is very nice and honestly your blog is full of juice of knowledge thanks mate!website designing
Leave a Reply
You must be logged in to post a comment.
