In addition to creating schedule logic the way people ordinarily perform their business activities, it's important from a scheduling logic perspective to also include at least one Finish-To-Start successor to each detail level task in a Microsoft Project schedule model. To illustrate this, I'm going to use a wildly exaggerated example.

Consider a program that has tasks as shown in Figure 1. Task A represents an integration activity; Task B represents a testing activity that may commence sometime after the start of integration. Task B is scheduled to start on Friday of Week 1 in the program. The “Finish Up Task” item represents the writing of a test report that can't start until the testing is complete. In this article, we're going to focus on the relationship between Tasks A and B (integration and test).

Click here to view entire article (members please login first)

This full article is available only to MPUG paid Members.
Join today and read the article in its entirety today.