If the successor of Summary Task 1 is Summary Task 2 the activities under Summary Task 2 can’t have a successor activity under Summary Task 1. Linking summary tasks can result in the same warning message. This warning message notifies the planner of a circular relationship. Task C cannot link back to Task A as a successor task. Task A’s successor is Task B and Task B’s successor is Task C. Consider a plan with 3 activities: Task A, Task B and Task C. MS Project prevents links between activities that would create circular logic. Linked summary tasks may cause circular logic warning messages in MS Project Here is the Resource Usage view from the more efficient plan.
When the links are removed from the summary tasks the developers can move from one build to the next with minimal downtime. The Resource Usage view below clearly shows the down time. You have probably already spotted that when summary tasks were used to link the modules in the example above, Developer's 1 and 2 had periods of down time. Linking summary tasks can lead to bench time Of course there might be resource constraints that prevent this approach, but MS Project resource calendars should be used to reflect the Developers availability rather than activity links. Removing the logic from the summary activity enables the project planner to identify these efficiencies see below.īy planning for the Developers to move straight from one build to another the project delivery time could be reduced from 5 to 4 weeks. This would reduce the time between builds and the overall plan timescale. However, it is likely that the summary task links are causing an error in logic and the developer could actually move straight onto Build section 2.1.
Because of the links between the summary tasks there is a gap between section 1.1 and the developer's next task Build section 2.1 completing in week 3. Developer 1 is completing the Build of section 1.1 in week 1. Summary task links can produce errors in logic often artificially extending the planĬonsider the example below. In this example links between summary tasks turn the Gantt view in to a complex spaghetti junction of dependencies.
0 kommentar(er)
