Fordham University            The Jesuit University of New York

Dos & don'ts

Developing a Plan
lightbulb idea
When developing a plan and entering tasks:
  • Use a meaningful description for the Task that most people in IT would understand.
  • Every Task should have a Resource, selected from the Enterprise Resource Pool, not typed in.  Project Managers should enter a generic resource allowing Resource Managers to enter a named individual.
  • Every Task should have a Predecessor and a Duration
  • Summary Tasks do not have Predecessors, nor Resources
  • Tasks should have a Duration of not longer than 2 weeks, and not shorter than an hour.
Scheduling activities, 
When scheduling activities, the best practice is NOT to enter Start Dates and End Dates. 
  1. After speaking with the people responsible for doing the work, enter the Task’s Duration.
  2. When the Tasks and Durations have been entered, enter the Predecessor and Resource for each Task.
  3. The Kickoff meeting will have a Start Date as the first Task, and can serve as the earliest anchor for any other dependent Tasks.
Although there will be Tasks that MUST be Started or Completed by a certain date, if a date is entered it acts as a “constraint”, a calendar  icon shows up in the “ info” column (“This Task has a ‘Start no earlier constraint…”), and the dependency chain of Tasks is broken. Without linkage among Tasks, there is just a list of activities.

Maintaining a Plan (Coming soon…)
  • How to Status a Plan
  • How to Baseline a Plan
  • Logging Risks and Issues in the Project Workspace

If you have any questions please send an e-mail to:

Site  | Directories
Submit Search Request