Project Scheduling Rules
Publisher: Bookboon
Published: 2013
ISBN-13: 9788740303339
Table of contents: title: Sisältö; title: Scheduling Methodology Should Be Documented and Approved; title: The Schedule Should Have a Complete Scope; title: Level-of-Efforts Should not Be Critical and Should not Have Variance; title: Activities Should Have Unique Names; title: Activity Names Should Have a Verb; title: Each Activity Should Have at Least One Predecessor and One Successor; title: Activities Should not Be Dangling; title: Most Relationships Should Be FS; title: SF Relationships Should Be Avoided as Much as Possible; title: Long Lags Should not Be Used; title: The Number of Lags Should Be the Fewest Possible; title: The Number of Leads Should Be the Fewest Possible; title: Activities Should not Have Negative Floats; title: Activities Should not Have Long Floats; title: Activities Should not Be Split; title: Date Constraints Should Be the Fewest Possible; title: Date Constraints Had Better Be Implemented Through Milestones; title: Activities Should not Have Long Durations; title: Duration Units Had Better Be the Same; title: Appendix 1: Creating Work Breakdown Structures; title: Appendix 2: The Distinction between Schedule and Schedule Model