SSI Tools for Microsoft Project

User guide

×
Menu
Index

No Predecessor or Successor

 
What gets flagged by the Audit
A Task or Milestone that has no Predecessor or Successor will be identified by this audit.  If the option to check selected items only is not checked, all tasks and milestones (summaries are never evaluated in this audit) are tested for this condition.
 
Why does it matter if items in the project have no Predecessor or Successor?
Dependencies (Predecessors and Successors) are a necessary element of an effective schedule.  Without dependencies, the impact of schedule variances may not be known on affected tasks and it will not be possible to perform a credible Critical Path Method (CPM) analysis.   If your schedule is visible or reported to certain private and Government organizations, it might not pass audits that test for generally accepted scheduling practices if it contains too many schedule items without predecessors and successors. 
To the maximum extent possible, the Start date for a task in a schedule should be determined by its predecessors.  The Finish date, I turn, should be determined by its duration - which may need to be adjusted to take into account its successors.
 
Does every task and milestone in a project need a Predecessor and Successor?
No. It is common for a project to contain certain items that have either no predecessor, no successor or both.  Examples of these include:
 
 
Resolving tasks with No Predecessors or Successors
 
What Else to Consider
Project Management Institute's PMBOK (Project Management Body of Knowledge) definition of Predecessor and Successor Activity:
 
The DCMA 14 Point Assessment tests for "Missing Logic"
Missing Logic: Number of activities missing a predecessor, a successor, or both. Should not exceed 5%.
 
 
 
Made by Dr.Explain, software documentation tool