Project Management Exercise -
The Beta project team has started gathering the information necessary to develop the project network diagram - predecessor activities and durations in weeks. The results of their meeting are found in the following table.
Activity
|
Description
|
Duration
|
Predecessor
|
1
|
Define Scope
|
6
|
None
|
2
|
Define Customer Problems
|
3
|
1
|
3
|
Define data records and relationship
|
5
|
1
|
4
|
Mass Storage Requirements
|
5
|
2, 3
|
5
|
Consultant Needs Analysis
|
11
|
2, 3
|
6
|
Prepare Installation Network
|
3
|
4
|
7
|
Estimate Costs and Budgets
|
2
|
4
|
8
|
Design Section Point System
|
1
|
4, 5
|
9
|
Write Request Proposal
|
5
|
5
|
10
|
Compile Vendor List
|
2
|
5
|
11
|
Prepare MGMT Control System
|
5
|
6, 7
|
12
|
Prepare Comparison Report
|
5
|
9, 10
|
13
|
Compare System Philosophies
|
5
|
8, 12
|
14
|
Compare Total Installation
|
2
|
8, 12
|
15
|
Compare Cost of Support
|
3
|
12
|
16
|
Compare Customer Satisfaction Level
|
8
|
12
|
17
|
Assign Philosophies Points
|
1
|
13
|
18
|
Assign Installation Cost
|
1
|
14
|
19
|
Assign Support Cost
|
1
|
15
|
20
|
Assign Customer Satisfaction Points
|
1
|
16
|
21
|
Select Best System
|
2
|
11, 17, 18, 19, 20
|
22
|
Order System
|
1
|
21
|
The project team has requested that you create a network diagram for the project, identify the critical path, and determine if the project can be completed in 50 weeks.
You are to first do a "hand drawn" solution, and then use Microsoft Project to create network diagram again. Assumptions: Start date is October 3, 2016, one shift per day, no overtime, no weekends, and all traditional holidays to be observed.