Posted by Brian Leach on 6/6/2012 4:24 PM | Comments (0)

Microsoft Project users make mistakes in their schedule every day. Some of these mistakes result in nothing and yet others, can lead to quite serious consequences. Ultimately, these commonly made mistakes obstruct the ability of Microsoft Project to do what it was designed for: calculate an accurate critical path. When the critical path is not accurate, the schedule suffers from poor quality, in much the same way a written document filled with spelling errors would be considered to be poor quality.

Steelray Software developed a “spell checker” for Microsoft Project, except instead of catching spelling errors, its catches scheduling errors and mistakes that are commonly made when using Microsoft Project.

Schedule Checker, an add-in to Microsoft Project 2010 from Steelray Software, helps in the same way that a spell checker helps. Like a spell checker, Schedule Checker searches for mistakes much faster than they could be found by searching manually. The issues are highlighted inside of Microsoft Project, in much the same way a spellchecker will highlight spelling errors in your document. In the same way a spell checker suggests corrections, Schedule Checker will explain the issues and suggest steps on how to correct the problem.

What are examples of the issues that can cause an inaccurate critical path? Schedule Checker searches for 22 of them, including:

  • Planned dates in the past
  • Missing sequencing
  • Tasks with constraints
  • Manually scheduled tasks

For the same reason you would use a spell checker, Schedule Checker will result in a higher quality schedule by allowing Microsoft Project 2010 to serve its main purpose: calculating an accurate critical path.

blog comments powered by Disqus