Does this information (WBS) allow you to define any milestones of the project? Why or why not? What are they? The information that provided in part 1 alone is not enough to allow the project team in defining any milestones of the project. Actually the hierarchical breakdown of the activity can be designed out of this information but for defining milestones; the project team may well require the following: * Duration of Activity/Activities/Group of Activities that is the time allocated to each activity. * Resource Dependency that is the resources upon which each activity or group of activities depends on. So far, we do not know the afore-mentioned aspects of the project and hence only this information is insufficient to provide us ant help in defining the milestones of the project.
1. When is the project estimated to be completed? How long will the project take?
The project will take to complete on 2/2/12 and it will take 530.
2. What is the critical path(s) for the project?
Architectural decisions- Hardware specifications - Hardware design - Hardware documentation - Integration first phase - Serial I/O drivers - System hard/software test -Network interface - Integrated acceptance testing.
3. Which activity has the greatest amount of slack?
Utilities documentation (115 days).
4. How sensitive is this network?
It is not very sensitive network because there is only one critical path. The more critical path you have the more sensitive you get in the project.
5. Identify two sensible milestones and explain your choices.
The Integration first phase, System hard/software test.
1. Compare the advantages/disadvantages of displaying the schedule as a network versus a Gant chart.
The advantage of network:
The network diagram display logical relationships among the various activities that take place within a project. It also allows the project manager to see how the various activities flow towards to...
Please join StudyMode to read the full document