Project management

1

BUSA 428 Fall 2017 Project Management

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

BUSA 428 Project

2

PROJECT OBJECTIVE

This project attempts to address many of the topics covered in the course this semester.

Students will provide responses that directly answer the questions posed and execute

required tasks.

PROJECT INSTRUCTIONS

Copy entire document into a Word document and begin to respond to all questions

Be sure and address each question/request in detail

All graphs/charts/tables are to be produced in the native format (excel, project, etc.) and then

copied into the response area of the Word document

Post BOTH the Word document with all responses/graphs/charts/tables AND the objective

evidence (the native documents from where you copied the charts/graphs/tables)

Project Start Date: 27 October 2017

Project Due Date: 01 December 2017

GRADING CRITERIA

Cover all points in the response. Use the Word document posted as the template for all

responses and task work. The Word document will be the formal response back to Astin

Martin Graphics. All tables, graphics, and figures created by other tools should be

copied and pasted in the Word document maintaining a professional appearance with

appropriate labeling of all figures, diagrams, tables, artifacts pasted.

Where applicable, provide clear documentation, graphics, diagrams, and tables that

help clarify any responses.

STATEMENT OF WORK SUMMARY

RFP awarded for specific web services which will be incorporated into a web graphics

company (Astin Martin Graphics LLC). Topical level requirements for the software were

provided. Deliverable products include:

- Systems Engineering to provide appropriate requirements decomposition - Software Engineering to provide design/development/unit test of software - System Test Engineering to provide component and enterprise level testing - Quality Engineering to provide quality control through the entire development life

cycle

3

- Management functions to include all primary functions (project management, finance, planning & scheduling, Overhead support (contracts, engineering matrix, etc.)

Award date of May 15 and required completion date (deliverables provided) of

November 15.

Astin Martin Graphics request of planned deliverables, acceptance criteria, quality plan,

and work breakdown structure. These items need to be provided in an acceptable time

for Astin Martin to review and approve.

Astin Martin Graphics further requests other deliverables to include final software

(source and binary) which meets all approved acceptance criteria, associated design

documents (system and development level)

All project questions or request for project scope changes should be directed to the

Astin Martin Graphic designee (course instructor).

There is no requirement relative to project tools used to generate the required data.

Topical requirements include:

- System Engineering: UML design appropriate graphic widgets to display aeronautical expanse gauges within the technical specs guidelines for twenty-five different visual aspects. Include appropriate level of peer review. Design should include graphical mock-up of gauges.

- System Engineering: Derive component level requirements for Software Engineering to design, code, and unit test and System Test can provide System and Enterprise level testing

- Software Engineering: Provide appropriate level design artifacts from System Engineering UML design artifacts. Include appropriate level of peer review.

- Software Engineering: Code and Unit Test software modules that execute the software which meets all topical and derived requirements

- System Test Engineering: Derive sell-off acceptance criteria. Include appropriate peer review (including System Engineering) and customer approval.

- System Test Engineering: Derive System and Enterprise Level Test Cases. Include appropriate level of peer review.

- System Test Engineering: Execute test cases as software modules become available

- Quality Engineering: Provide quality checks during the processes described for System Engineering, Software Engineering, and System Test Engineering as appropriate

- Include the following customer related reviews: Design Review (after System Engineering completes design artifacts), Pre-Ship Review (provided prior to Astin Martin Graphics acceptance of software), and Final Acceptance Test (software demonstration at customer facility showing software meets all requirements as installed)

4

Approved labor rates as follows:

- System Engineer I: 42.50 - System Engineer II: 48.37 - System Engineer III: 51.17 - Lead System Engineer: 58.91 - Software Engineer I: 40.38 - Software Engineer II: 47.55 - Software Engineer III: 51.01 - Lead Software Engineer: 59.83 - System Test Engineer I: 40.78 - System Test Engineer II: 44.49 - System Test Engineer III: 49.25 - Lead System Test Engineer: 51.25 - Quality Engineer I: 40.38 - Quality Engineer II: 47.55 - Quality Engineer III: 51.01 - Lead Quality Engineer: 59.83 - Project Manager: 91.22 (LOE – Level of Effort) - Chief Engineer: 72.41 (LOE – Level of Effort)

Approved overhead rates as follows:

- Finance: 7.5% of total hours - Planning & Scheduling: 6.3% of total hours - Management (Contracts/Senior Management): 2.1% of total hours - Facility: 1.2% of total hours - HR/Staffing: 0.51% of total hours

ACTIVITY / TASK LIST BY LOWEST WBS LEVEL LEG

2.1 Select Layout

System Engineering: Create outline of UML design.

Software Engineering: Assist system engineering.

Quality Engineering: Provide quality checks

2.2 Design Graphics

System Engineering: Design appropriate graphic widgets to display aeronautical

expanse gauges within the technical specs guidelines for twenty-five different visual

aspects. Include appropriate level of peer review.

5

Software Engineering: Assist system engineering.

Quality Engineering: Provide quality checks.

2.3 Approve design

System Engineering: Derive component level requirements for Software Engineering to

design, code, and unit test and System Test can provide System and Enterprise level

testing.

Software Engineering: Assist system engineering

System Test Engineering: Derive sell-off acceptance criteria. Include appropriate peer

review (including System Engineering) and customer approval.

Quality Engineering: Provide quality checks.

3.1 Write content

System Engineering: Assist software engineering

Software Engineering: Code and Unit Test software modules that execute the software

which meets all topical and derived requirements.

Quality Engineering: Provide quality checks.

3.2 Approve content

System Engineering: Assist software engineering

Software Engineering: Provide appropriate level design artifacts from System

Engineering UML design artifacts. Include appropriate level of peer review.

System Test Engineering: Derive sell-off acceptance criteria. Include appropriate peer

review (including System Engineering) and customer approval.

Quality Engineering: Provide quality checks.

3.3 Insert content in pages

System Engineering: Assist software engineering

Software Engineering: Check the function

Quality Engineering: Provide quality checks.

6

4.1 Set up web service on test

System Engineering: Corporate with other engineers for opinion

Software Engineering: Corporate with other engineers for opinion

System Test Engineering: Derive System and Enterprise Level Test Cases. Include

appropriate level of peer review.

Quality Engineering: Provide quality checks.

4.2 Perform tests

System Engineering: Corporate with other engineers for opinion

Software Engineering: Corporate with other engineers for opinion

System Test Engineering: Execute test cases as software modules become available

Quality Engineering: Provide quality checks.

4.3 Approve web service

System Test Engineering: Assist Quality Engineering

Quality Engineering: Quality checks during the processes described for System

Engineering, Software Engineering, and System Test Engineering as appropriate

Include the following customer related reviews: Design Review (after System

Engineering completes design artifacts), Pre-Ship Review (provided prior to Astin Martin

Graphics acceptance of software).

4.4 Set up web service on live environment

System Test Engineering: Assist Quality engineering

Quality Engineering: quality checks, and Final Acceptance Test (software demonstration

at customer facility showing software meets all requirements as installed) installed)

ACTIVITY DURATION SCHEDULE

Activity estimated Duration

7

The estimated total elapsed time for how long an activity will take from starts

to finish, including associated waiting time. Also referred to as activity

resource estimated or estimated activity resources.

PROJECT QUESTIONS & TASKS

1. Provide a project objective associated with the Astin Martin Graphics project. Include a list of assumptions about the project.

2. What is a work breakdown structure? What is a responsibility matrix? Using the Astin Martin project activity list and activity duration schedule, create a WBS and RAM.

Work Breakdown Structure

???

Responsibility Assignment Matrix

??? (Example RAM Template)

Task\Date 15-May 25-May 5-Jun 15-Jun 25-Jun 5-Jul 15-Jul 25-Jul 5-Aug 15-Aug 25-Aug 5-Sep 15-Sep 25-Sep 5-Oct 15-Oct 25-Oct 5-Nov 15-Nov

Select Layout

Design Graphics

Approve Design

Write Content

Approve Content

Insert content into page

Set up test web service

Perform tests

Approve web service

Go live

Plan Duration Actual Start % Complete (beyond plan)

Baseline Schedule

8

3. Create a network diagram (graphical diagram) that shows the sequence and dependent relationships identified in the Astin Martin project activity list and activity duration schedule.

4. Using the project start time and the required completion date and the project activity list and activity duration schedule, calculate the ES, EF, LS, and LF times and total slack for each activity. Show results in table form. If your calculations result in a project schedule with negative total slack, revise the project scope, activity estimated durations, and/or sequence or dependent relationships among activities to arrive at an acceptable baseline schedule for completing the project within the required time line. Describe (including tables) the revisions you made.

(Example Template)

WBS

Item Work Item

1 Web Service Design P S

2 Design S S P S

2.1 Select layout P S

2.2 Design Graphics P S

2.3 Approve Design P S

3 Content S S P S

3.1 Write content P S

3.2 Approve content P S

3.3 Insert Content in pages P S

4 Development S S P S

4.1 Set up test web service P S

4.2 Perform tests P S

4.3 Approve web service S S S P

4.4 Go live S S S P

Q u

a lit

y E

n g

in e

e r

II I

Le a

d Q

u a

lit y

E n

g in

e e

r

S y

st e

m T

e st

E n

g in

e e

r II

S y

st e

m T

e st

E n

g in

e e

r II

I

Le a

d S

y st

e m

T e

st E

n g

in e

e r

Q u

a lit

y E

n g

in e

e r

I

Q u

a lit

y E

n g

in e

e r

II

S o

ft w

a re

E n

g in

e e

r I

S o

ft w

a re

E n

g in

e e

r II

S o

ft w

a re

E n

g in

e e

r II

I

Le a

d S

o ft

w a

re E

n g

in e

e r

S y

st e

m T

e st

E n

g in

e e

r I

Key: P = Primary responsibility; S = Support responsibility

P ro

je ct

M a

n a

g e

r

C h

ie f

E n

g in

e e

r

S y

st e

m E

n g

e e

r I

S y

st e

m E

n g

e e

r II

S y

st e

m E

n g

e e

r II

I

Le a

d S

y st

e m

E n

g in

e e

r

9

ES EF LS LF Slack

Select Layout 15-May 25-Jun 25-May 5-Jul 10

Design Graphics 15-Jun 25-Jul 25-Jun 5-Aug 10

Approve Design 25-Jul 15-Aug 5-Aug 25-Aug 11

Write Content 15-May 25-Jun 25-May 5-Jul 10

Approve Content 25-Jun 15-Jul 5-Jul 25-Jul 10

Insert content into page 5-Jul 15-Aug 15-Jul 25-Aug 10

Set up test web service 15-Aug 25-Sep 25-Aug 5-Oct 10

Perform tests 15-Sep 15-Oct 25-Sep 25-Oct 10

Approve web service 25-Sep 25-Oct 5-Oct 5-Nov 10

Go live 5-Oct 5-Nov 15-Oct 15-Nov 10

10

5. List all activity costs. From the project activity list and activity duration schedule, estimate the cost of each activity. Then, determine the Total Budgeted Cost (TBD) for the Astin Martin Graphics project. Provide the information in table format by month. (Example Template)

6. Provide a cumulative budgeted cost curve for the Astin Martin Graphics project. Provide in appropriate graph format.

7. Astin Martin Graphics wants to know if you plan to use a management reserve for their project. Explain what the term reserve means and why you will use contingency reserve in the project or not.

8. Astin Martin Graphics wants to know how JBB Software plans to employ cost management and earned value (EV) in their project. Define to them the following: TBC, CBC, CAC, CEV CPI, CV, FCAC, TCPI. In addition, explain to Astin Martin Graphics why it is necessary to calculate the earned value of work performed and how it is done.

9. Astin Martin Graphics is concerned about how JBB Software will manage risks. Describe what JBB Software plans to do in order to manage risk on the Astin Martin Graphics project and if a risk assessment matrix will be employed and why.

May June July Aug Sep Oct Nov Total

Select layout 7778.55 11369.98 19,148.53$

Design graphics 8976.30 14960.50 23,936.80$

Approve design 4705.14 11762.85 16,467.99$

Write content 7778.55 11369.98 19,148.53$

Approve content 4705.14 11762.85 16,467.99$

Insert content in page 15558.92 8976.30 24,535.22$

Set up web service on test 12547.04 19604.75 32,151.79$

Perform tests 11762.85 11762.85 23,525.70$

Approve web service 1922.70 9613.50 11,536.20$

Set up web service on live enviroment 9998.04 1922.70 11,920.74$

Total Budgeted Cost 198,839.49$