Reference no: EM131340461

This assignment contains two (2) deliverables: a summary document to be delivered in a word processor document format and a Work Breakdown Structure (WBS) to be delivered in a project file.

Overview:

Imagine that you work as the project manager for an IT department. Your organization has recently approved the development of a mobile application. As the project manager, you will manage the development of the project. The project will include user experience (UX) design by a consultant, graphic design by a team of two contracted designers, and in-house application development by a team of three (3) programmers and a database developer.

Deliverable 1: Summary (MS Word or open source equivalent)

Write a one to two (1-2) page summary document in which you:

Summarize the project requirements and other assumptions (i.e., budget, human resources, workload, environmental dependencies, etc.).
Define a work breakdown structure and describe the methodology behind constructing one.

Deliverable 2: WBS (MS Project or open source equivalent)

Use Microsoft Project or an open source equivalent to create a WBS which addresses the following:

Contain at least five (5) main tasks, one (1) for each of the PMBOK® process areas.

Contain at least thirty (30) line items distributed in five (5) or more work packages.

Contain Work Breakdown Structure Code for each task.

Present duration estimates for each task that results in a duration estimate for the project not to exceed the requirements described in the overview.

Deliverable one (1) of your assignment must follow these formatting requirements:

Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions.

Include a cover page containing the title of the assignment, the student's name, the professor's name, the course title, and the date.

The cover page and the reference page are not included in the required assignment page length

Mobile App Part 2 (Gantt and PERT Charts)

Update the Microsoft Project file you created in Assignment 4: Mobile App Part 1 (Work Breakdown Structure) with the following changes:

Set progress in at least ten (10) of the line items.

Set the properties so that at least one (1) of the main tasks is behind schedule.

Create a Gantt chart for the project.

Take a screenshot of the Gantt chart which can later be inserted into your written paper.

Create a PERT diagram that identifies the critical path.

Take a screenshot of the PERT chart which can later be inserted into your written paper.

Note: If you need a tutorial on taking a screen shot, visit one of the following locations: PC Users Mac Users

Write a two to three (2-3) page paper in which you:

Compare and contrast the information that one receives from a Gantt chart, versus that of a PERT diagram.

Examine the advantages of using a Gantt chart over a PERT chart and vice versa. Determine when it is appropriate to use one over the other. Justify your response.

Explain the importance of the critical path in project management.

Insert the screenshots of the Gantt and PERT charts you created based on the provided criteria. Elaborate on the status of the mobile application development project based on the updated information. Note: The graphical representations do not count toward the overall page requirement.

Use at least one (1) quality resource in this assignment. Note: Wikipedia and similar Websites do not qualify as quality resources.

Mobile App Part 3 (Risk)

Reference the Microsoft Project file you created in Assignment 5: Mobile App Part 2 (Gantt and PERT Charts) for the completion of this assignment.

Write a two to three (2-3) page paper in which you:

Document at least ten (10) total risks (two [2] risks for each phase of IT projects) of the mobile application development project.

Assess the likelihood of occurrence for each risk.

Assess the impact of each risk on the success of the project.

Identify an owner for each risk.

Recommend a strategy to manage each risk.