Unit VII Project (For hifsa shaukat Only) Project Management

profileAlessandro Volta
unit_vi_project.docx

Running head: UNIT VI PROJECT

2

UNIT VI PROJECT

( Unit VI Project Claude Holmes Professor Jim Marion Project Management Columbia Southern University 22 November 2016 )

Part 1: Activity Precedence and Duration Table

No.

Task Name

Duration

Predecessors

1

Project Management

30 days

 

2

Market Research

6 days

 

3

Focus Group Definition

1 day

 

4

Survey

2 days

3

5

Research Analysis

1 days

4

6

Market Analysis

2 days

5

7

Software Designing

6 days

 

8

Design

1 day

6

9

Research Evaluation

1 days

8

10

Concept Model

2 days

9

11

Design Selection

2 days

10

12

Software Development

6 days

 

13

ERD

2 days

10

14

Initial Prototype

1 day

13

15

Prototype Testing

2 days

14

16

Production On Development

1 days

15

17

Production Planning

6 days

 

18

Focus Group Definition

1 day

16

19

Survey

2 days

18

20

Research Analysis

2 days

19

21

Concept Model

1 day

20

22

Marketing

6 days

 

23

Marketing Strategy

1 days

21

24

Marketing Plan

1 days

23

25

Marketing Collateral

2 days

24

26

Advertisement

2 days

24

Gantt Chart

Network Diagram

This is the network diagram

Part 2:

Question No.1: Favorable and Unfavorable conditions for Crashing

The most favorable condition for the crashing of the remaining project activities is that it would buy the some time for the team in which they would be able to complete the project as per its completion date. The timely completion is both desirable for the project manager and the organization. It would also help the organization from in saving it from the penalties. Another unfavorable factor could be the public image of the organization that would be spoiled as a result of late completion of the task.

The unfavorable condition for the crashing of the remaining project is the cost of the crashing that must be incurred in order to complete crashing. If the cost of crashing is lower than the additional margin that is provided to the project manager Mr. Joe then he may consider the crashing of other options otherwise it would become escalation of commitment. Another unfavorable condition may be that after selecting of the crashing option, it is not sure that the project will be completed at the required date of completion. There is a risk that would cost the company both cost of crashing and penalties that would be faced due to delayed completion of the project.

Question No.2: Decision Making as a Site Supervisor

Being a site supervisor, I would consider the cost of the crashing the project and would compare the same amount with the allotted budget, if it crosses the budget then crashing would not be advisable. Another option would be the cost benefit analysis of the crashing that is if it saves the organization from penalties (for delayed completion). Time saving would be also be considered, that is, whether it is possible that time would be saved as a result of crashing. Which activities can be performed parallel, would this compromise the quality of the final product?

The decision of crashing would be advisable only when it is assured that the controllable reasons due to which the project was delayed mishaps (Delayed delivery of materials, etc.) would not happen in future. If the supplier has agreed upon timely delivery of the materials and there is insurance that no mishap will happen. If the cost of the penalties is higher than the cost of the crashing it would be advisable to go for crashing as it would save the organization from penalty, if timely completion is ensured. Time saving is the main objective so it must be properly planned. Part 3: Network Activity Chart and Identification of Critical Path

Gantt chart Activity Document

Network Diagram and Critical Path

Activity Network as Gant Chart

Days

2

4

6

8

10

12

14

16

18

20

22

24

26

28

30

32

34

36

38

40

42

44

46

48

50

52

54

Tasks

A

X

X

C

B

C

X

X

X

X

C

C

C

X

X

X

C

D

C

E

C

X

X

F

X

X

X

X

X

X

G

X

X

X

X

X

X

X

X

H

X

X

X

X

X

X

X

X

X

C

I

X

X

X

X

X

X

X

J

C

X

X

C

X = Shows full time block

C = Half time in the block

Expected Duration of the Project

Expected Duration = Optimistic Duration + 4 * Most Likely + Pessimistic Duration/6

Expected Time = 47 (=5+6+5+10+12+3+6) + 4*53 (Critical Path = 5+15+10+14+3+6) + 74 (=5+10+8+1+5+10+14+3+12+6)/6

Expected time would be 52 days

Part 4: Activity Network and Critical Path Management

Here is the activity network diagram in which the critical path is highlighted as red.

05 Days5

055

Task Name

51015

51015

B

5813

7715

C

516

19120

D

15520

15520

E

201030

201030

F

301444

301444

G

44347

44347

H

301242

351247

I

47653

47653

J

Task Name 0 5 Days 5 0 5 5 B 5 10 15 5 10 15 C 5 8 13 7 7 15 D 5 1 6 19 1 20 E 15 5 20 15 5 20 F 20 10 30 20 10 30 G 30 14 44 30 14 44 H 44 3 47 44 3 47 I 30 12 42 35 12 47 J 47 6 53 47 6 53

033

003

Task A

358

8513

B

3710

3010

C

10313

10013

D

8512

12517

E

13417

13017

F

17522

17022

H

10212

15517

G

Early StartDuration

Early

Finish

Late StartSlack

Late

Finish

Legend

Task A 0 3 3 0 0 3 B 3 5 8 8 5 13 C 3 7 10 3 0 10 D 10 3 13 10 0 13 E 8 5 12 12 5 17 F 13 4 17 13 0 17 H 17 5 22 17 0 22 G 10 2 12 15 5 17 Legend Early Start Duration Early Finish Late Start Slack Late Finish

ID

Project Management of Software

Development

StartFinishDuration

Nov 2016Dec 2016

181920212223242526272829301234567891011121314151617

16d25-Nov-1618-Nov-16Market Research

26d05-Dec-1628-Nov-16Software Designing

36d13-Dec-1606-Dec-16Software Development

46d21-Dec-1614-Dec-16Production Planing

56d29-Dec-1622-Dec-16Marketing

18192021222324252627282930

ID Project Management of Software Development Start Finish Duration 1 6d Market Research 2 6d 28-Nov-16 Software Designing 3 6d 06-Dec-16 Software Development 4 6d 14-Dec-16 Production Planing 5 6d 22-Dec-16 Marketing