Project Scheduling Rules
Publisher: Bookboon.com
Published: 2013
ISBN-13: 9788740303339
Table of contents: title: Content; title: 1. Scheduling Methodology Should Be Documented and Approved; title: 2. The Schedule Should Have a Complete Scope; title: 3. Level-of-Efforts Should not Be Critical and Should not Have Variance; title: 4. Activities Should Have Unique Names; title: 5. Activity Names Should Have a Verb; title: 6. Each Activity Should Have at Least One Predecessor and One Successor; title: 7. Activities Should not Be Dangling; title: 8. Most Relationships Should Be FS; title: 9. SF Relationships Should Be Avoided as Much as Possible; title: 10. Long Lags Should not Be Used; title: 11. The Number of Lags Should Be the Fewest Possible; title: 12. The Number of Leads Should Be the Fewest Possible; title: 13. Activities Should not Have Negative Floats; title: 14. Activities Should not Have Long Floats; title: 15. Activities Should not Be Split; title: 16. Date Constraints Should Be the Fewest Possible; title: 17. Date Constraints Had Better Be Implemented Through Milestones; title: 18. Activities Should not Have Long Durations; title: 19. Duration Units Had Better Be the Same; title: 20. Appendix 1: Creating Work Breakdown Structures; title: 21. Appendix 2: The Distinction between Schedule and Schedule Model