Scheduling Rules, A Free mini-eBook

The audience I had in mind when I was writing this book was mainly the project planning and control engineers, leaders and managers. This information would also be helpful for other project management team members.
Applying the rules might increase the length and effort of your initial planning, but trust me, it would buy you back a lot of time in schedule maintenance and control.

Table of Contents:
Rule 01: Document the Scheduling Methodology
Rule 02: The Schedule Should Have a Complete Scope
Rule 03: Be Careful with Level-of-Effort Activities
Rule 04: Activities Should Have Unique Names
Rule 05: Activity Names should have a verb
Rule 06: Each Activity Should Have at Least One Predecessor and One…
Rule 07: Activities should not be Dangling
Rule 08: Most Relationships should be FS
Rule 09: Try not to Use SF Relationship
Rule 10: You should not Use Large Lags
Rule 11: Use Lags as Less as Possible
Rule 12: Be Careful with Leads
Rule 13: Be Careful with Negative Floats
Rule 14: Activities should not Have Large Floats
Rule 15: Do not Split Activities
Rule 16: Do not Use a Lot of Date Constraints
Rule 17: Make Milestones for Date Constraints
Rule 18: Activities should not have Large Durations
Rule 19: Use Only One Duration Unit