Sie sind auf Seite 1von 2

Birla Institute of Technology & Science, Pilani Work-Integrated Learning Programmes Division Second Semester 2014-2015

Assignment-2

(EC-1)

Course No.

: AETT ZG523

Course Title

: Project Management

Weightage

: 10%

Submission date

: 20-June 2015

N.B. Both assignments 1 & 2 below should be attempted. Do not copy- work independently in order to derive value and to get credit.

1. You are serving as Project Manager on a critical communications project, and are now well along in the project. The following table summarizes the actual progress as of today (all figures are given in thousands of rupees) Develop a narrative status report for the board of directors of the chain store that discusses the status of the project to date and at completion. Be as specific as you can using numbers given and those you might develop. Remember, your audience is not familiar with the jargon used by project managers and computer software personnel; therefore, some explanation may be necessary. Your report will be evaluated on your detailed use of the data, your total perspective of the current status and future status of the project, and your recommended changes (if any).

 

NAME

PV

EV

AC

SV

CV

BAC

EAC

COMMUNICATIONS PROJECT

420

395

476

-25

-81

915

1103

H

1.0

HARDWARE

92

88

72

-4

16

260

213

 

H

1.1

Hardware specifications (DS)

20

20

15

0

5

20

15

H

1.2

Hardware design (DS)

30

30

25

0

5

30

25

H

1.3

Hardware documentation (DOC)

10

6

5

-4

1

10

8

H

1.4

Prototypes (PD)

2

2

2

0

0

40

40

H

1.5

Test prototypes (T)

0

0

0

0

0

30

30

H

1.6

Order circuit boards (PD)

30

30

25

0

5

30

25

H

1.7

Preproduction models (PD)

0

0

0

0

0

100

100

OP 1.0

 

OPERATING SYSTEM

195

150

196

-45

-46

330

431

 

OP 1.1

Kernel specifications (DS)

20

20

15

0

5

20

15

OP 1.2

 

Drivers

45

55

76

10

-21

70

97

 

OP 1.2.1

Disk drivers (DEV) I/O drivers (DEV)

25

30

45

5

-15

40

60

OP 1.2.2

20

25

31

5

-6

30

37

OP 1.3

 

Code software

130

75

105

-55

-30

240

336

 

OP 1.3.1

Code software (C) Document software (DOC) Code interfaces (C) Beta test software (T)

30

20

40

-10

-20

100

200

OP 1.3.2

45

30

25

-15

5

50

42

OP 1.3.3

55

25

40

-30

-15

60

96

OP 1.3.4

0

0

0

0

0

30

30

U

1.0

Utilities

87

108

148

21

-40

200

274

 

U

1.1

Utilities specifications (DS)

20

20

15

0

5

20

15

U

1.2

Routine utilities (DEV)

20

20

35

0

-15

20

35

U

1.3

Complex utilities (DEV)

30

60

90

30

-30

100

150

U

1.4

Utilities documentation (DOC)

17

8

8

-9

0

20

20

U

1.5

Beta test utilities (T)

0

0

0

0

0

40

40

S

1.0

System integration

46

49

60

3

-11

125

153

 

S

1.1

Architecture decisions (DS)

9

9

7

0

2

10

8

S

1.2

Integration hard/soft (DEV)

25

30

45

5

-15

50

75

S

1.3

System hard/software test (T)

0

0

0

0

0

20

20

S

1.4

Project documentation (Doc)

12

10

8

-2

2

15

12

S

1.5

Integration acceptance testing (T)

0

0

0

0

0

30

30

2. From your experience, consider any one project that you worked on or managed. Giving a brief description of the project, discuss the following:

a. The project organization structure used. Was it appropriate?

b. The communication plan implemented. Did it serve the requirements of the project?

c. Draw the project priority matrix for the project.

d. How did the project perform on the three criteria for project success?

e. Prepare a suitable lessons learned document in an appropriate formatdoc file attached

Glossary:

EV Earned value for a task is simply the percent complete times its original budget.

Stated differently, EV is the percent of the original budget that has been earned by actual work completed. [The older acronym for this value was BCWPbudgeted cost of the work performed.]

PV The planned time-phased baseline of the value of the work scheduled. An approved cost estimate of the resources

scheduled in a time-phased cumulative baseline [BCWSbudgeted cost of the work scheduled].

AC Actual cost of the work completed. The sum of the costs incurred in accomplishing work. [ACWPactual cost of the

work performed].

CV Cost variance is the difference between the earned value and the actual costs for the work completed to date where

CV = EV - AC.

SV Schedule variance is the difference between the earned value and the baseline line to date where SV = EV - PV.

BAC Budgeted cost at completion. The total budgeted cost of the baseline or project cost accounts. EAC Estimated cost at completion. ETC Estimated cost to complete remaining work. VAC Cost variance at completion. VAC indicates expected actual over- or underrun cost at completion.

Suggested format-headings for lessons learneddocumentation:

INTRODUCTION

LESSONS LEARNED APPROACH

LESSONS LEARNED FROM THIS PROJECT

The following chart lists the lessons learned for the project. These lessons are categorized by project knowledge area and descriptions, impacts, and recommendations are provided for consideration on similar future new construction projects. It is important to note that not only failures or shortcomings are included but successes as well.

Category

Issue Name

Problem/Success

Impact

Recommendation

Procurement

       

Management

Human

       

Resources

Management

Scope

       

Management

Quality

       

Management

Risk

       

Management

LESSONS LEARNED KNOWLEDGE BASE / DATABASE

.

LESSONS LEARNED APPLIED FROM PREVIOUS PROJECTS

PROCESS IMPROVEMENT RECOMMENDATIONS