Tip of the Week: Project Schedule Resources
Tip of the Week: Project Schedule Do’s and Don’ts – When adding resources, DO use ONLY the enterprise resource pool, DON’T add local resources to a task. Visit Tip of the Week for more tips.
Tip of the Week: Project Schedule Do’s and Don’ts – When adding resources, DO use ONLY the enterprise resource pool, DON’T add local resources to a task. Visit Tip of the Week for more tips.
Tip of the Week: Project Schedule Do’s and Don’ts – DO input all of your tasks as “Fixed Duration” and not “Effort Driven” o (Tools>Options>Schedule tab) o Exception: For planning purposes; use “Effort Driven” to see the results of resource
Tip of the Week: Project Schedule Do’s and Don’ts – DON’T leave estimated task durations in your schedule (“?” in duration field).
Tip of the Week: Project Schedule Do’s and Don’ts -DO use Hard Logic and Soft Logic when assigning predecessors and successors: o Soft Logic tasks can be worked in any order, but MUST be related to another task, assigned as
Tip of the Week: Project Schedule Do’s and Don’ts – DO give ALL tasks both tasks predecessors and successors, 4 exceptions to the rule: o No predecessor for the start task / milestone o No successor the for the end task
Tip of the Week: Project Schedule Do’s and Don’ts – DON’T use a negative lag.
Tip of the Week: Project Schedule Do’s and Don’ts – DON’T use a “Deadline”.
Tip of the Week: Project Schedule Do’s and Don’ts – If a constraint is required to assign a date to a task, instead use Lag to achieve date.
Tip of the Week: Project Schedule Do’s and Don’ts – DO only use the “As Soon As Possible” constraint.
Tip of the Week: Project Schedule Do’s and Don’ts – DO only use Finish-to-Start relationships. (Exceptions to this rule must be documented.)
PMI®, PMP®, CAPM® and PMBoK® are registered marks of the Project Management Institute
NAICS Codes: 541611, 541330, 541511, 541512 ,541519, 541613, 541614, 541618, 541990, 561990, 611420, 611430, 813910, 813920