Well, you can apply a highlight filter to show the critical tasks in a
distinct colour, or there are some critical task listing reports in the
reports library that you can use if you want and of course you can create
others with the custom report feature. My curiosity is piqued with your
need to emphasize lag time, I wonder if we're using the term to mean the
same thing. Lag time is an intentional delay introduced into a dependency
link so as to start the successor some time later than the link would
otherwise have it start. The example I use in class is we have to mail a
survey before we can analyze the responses we get to it. But we have to
wait a few weeks after mailing for enough responses to get back. So my link
is mailing->analyze FS with a 2 week lag time added to allow enough time for
the answers to get back to us. I can't imagine how that could become a
critical management issue for your functional managers or even occur all
that often. Are you sure you're not talking about SLACK time (also called
"float"), the time a task could be delayed before it pushes back the project
finish or causes a successor task to be delayed, the manager's "wiggle
room"? A critical task is one that has zero or negative slack.
--
Steve House [MVP]
MS Project Trainer/Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs