Tip of the Week: Project Schedule Task Descriptions

Share on facebook
Share on twitter
Share on linkedin
Share on google

Tip of the Week: Project Schedule Do’s and Don’ts –  DON’T use generic, non-unique task descriptions (ex: Unit Test); DO make task descriptions completely unique and include an action verb (ex: Perform Unit Test on 123 Module); usually the summary tasks above the detailed tasking will provide clues as to project context.  Summary tasks are often not included in specialized reporting, so that tasks need to be able to stand alone.

Click here for more tips.

Articles & News

DOWNLOAD OUR PROJECT ASSURANCE® CHECKLIST

Fill out the form below to access our checklist that will ensure your project's success!