Welcome to PMConnection

     

Menu
· Home
· The Project Management Search Engine
· Exclusive Articles

Related Sites
There isn't content right now for this block.

Related Products
   
 

The Self-Driving Project: Using Artificial Intelligence to Deliver Project Success

 
  
 
Citizen Development: The Handbook for Creators and Change Makers
  
 
 
A Guide to the Project Management Body of Knowledge: PMBOK 7th Edition 2021
  

 
PMP Project Management Professional Exam Study Guide
    
 

 
Microsoft Project Step by Step


  

 
Microsoft Project
  

  

 
Managing Enterprise Projects: Using Project Online and Microsoft Project Server

MS Project: Automatically Format Critical Path Activities in MS Project 2007
Posted on Sunday, September 24 @ 22:01:42 EDT by webadmin

PMConnection Articles
If you are a user of Microsoft Project, then you have probably discovered that to see which task are on the critical path, you can use a filter or grouping option.  Or perhaps you attempt to leverage the Tracking Gantt View to see the critical tasks appearing as red task bars.  Using this option works well if you manage your schedule from the gantt chart portion.  But from my experience, most people focus on the tabular portion of their schedule when modifying activity attributes.  If this describes you, then here is a trick that will help.

It is possible to configure MS Project to automatically format the critical path tasks on the tabular portion of your schedule.  Here are the steps:

1. Click on Format
2. Click on Text Styles
3. Click on the dropdown for the Item to change
4. Select Critical Tasks
5. Click on the dropdown for Color
6. Select Red
7. Select Bold under Font Style
8. Click on OK

The entire row for all tasks that are on the critical path of your schedule will now appear in Bold Red.

But here is the best part... As you are managing / modifying your schedule, if your change causes a new task to come on the critical path, that task will automatically turn Bold Red!!

Since learning this trick a few years ago, I use it on all my schedules.  During the planning stages, I inspect these critical path tasks just to make sure I'm seeing what I would expect.  Many times I will find simple errors in the logic of the plan that I would not have otherwise caught.  Now before committing to delivery dates, I'm more confident that we have developed a realistic plan.  Using this option during the execution phase of my projects allows me to immediately know if the impact of schedule changes causes a change in critical path tasks.







Note: You may find this book helpful:


 
Related Links
· More about PMConnection Articles
· News by webadmin


Most read story about PMConnection Articles:
300 Project Manager Interview Questions


Article Rating
Average Score: 4.78
Votes: 32


Please take a second and vote for this article:

Excellent
Very Good
Good
Regular
Bad


Options

 Printer Friendly Printer Friendly


Associated Topics

PMConnection Articles

Sorry, Comments are not available for this article.


Copyright 2005-2024 PMConnection.com. All Rights Reserved.
http://www.pmconnection.com a
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.10 Seconds