CS 660 Assignment 4 - Integrated Project Plan

The assignment is to create an Integrated Project Plan that integrates the content of lectures, textbook chapters, and PMBOK chapters for a specific project case study. The plan should be well-organized, properly formatted, and answer several questions related to the project management process groups (initiating, planning, executing, controlling, and closing). The assignment also requires proper headings, subheadings, font, and margins. Additionally, students must submit their work in both printed paper format and via Blackboard by the due date.

CS660 Managing Projects, Resources and Risks
Assignment 4: Web Site Development Project
 Grade weight: 40% towards 20% overall assignment grades
 Due Date: 7/21/2016
 Assignment: Web Site Development
A nonprofit organization would like you to lead a Web site development project. The organization has Internet access
that includes space on a Web server, but no experience developing Web sites. In addition to creating its Web site, the
organization would like you to train two people on its staff to do simple Web page updates. The Web site should
include the following information, as a minimum: description of the organization (mission, history, and recent events),
list of services, and contact information. The organization wants the Web site to include graphic s (photographs and
other images) and have an attractive, easy-to-use layout.
1. Project Scope Management
Create a WBS for this project. Create and include milestones and summary tasks. Assume that the main WBS
categories and some of the project management tasks are similar to tasks from the Project Tracking Database
project example in the appendix.
Some of the specific analysis, design, and implementation tasks will be to:
a. Collect information on the organization in hardcopy and digital form (brochures, reports,
organization charts, photographs, and so on).
b. Research Web sites of similar organizations.
c. Collect detailed information about the customer's design preferences and access to space on a Web server.
d. Develop a template for the customer to review (background color for all pages, position of navigation
buttons, layout of text and images, typography, including basic text font and display type, and so on).
e. Create a site map or hierarchy chart showing the flow of Web pages.
f. Digitize the photographs and find other images for the Web pages; digitize hardcopy text.
g. Create the individual Web pages for the site.
h. Test the pages and the site.
i. Implement the Web site on the customer's Web server.
j. Get customer feedback.
k. Incorporate changes.
l. Create training materials for the customer on how to update the Web pages.
m. Train the customer's staff on updating the Web pages.
2. Project Time Management
a. Enter realistic durations for each task, and then link the tasks as appropriate. Assume that you have four
months to complete the entire project.
b. Show a Network Diagram view for the project.
c. Indicate the critical path
3. Project Cost Management
a. Assume that you have three people working on the project and each of them would charge $20 per hour .
Enter this information in a Resource Sheet.
b. Estimate that each person will spend an average of about five hours per week for the four-month period.
Assign resources to the tasks, and try to make the final cost in line with this estimate.
c. Show a budget report for your project.
4. Project Human Resource Management
a. Assume that one project team member will be unavailable (due to vacation) for two weeks in the middle of the
project. Make adjustments to accommodate this vacation so that the schedule does not slip and the costs do not
change. Document the changes from the original plan and the new plan.

5. Project Communications Management
a. Create a 1 to 2 slide project update dashboard to be presented to your sponsor. Include:
a. High-level Summary Tasks & Milestones
b. Project schedule status summary
c. Cost & budgetary status summary
d. Human Resource Management highlight
e. Any other relevant data you will like to show.
b. Create a “Who Does What Report”
General Guidelines and Grading Criteria
 Required Answer Format
a) Header Data should include:
i. Student’s name
ii. “CS 660 Assignment 4”
iii. The due date of the assignment
b) It is recommended that your approach to organizing and writing this assignment follows the
guidelines in this
section, with the main body content aligned to the list of questions provided in the description
section above. Consider the project activities that the Project Manager would need to perform
for each of these projects considering its objectives. In other words, apply the relevant selection
of knowledge areas, tools and application area expertise, appropriate to this project.
c) The project manager (the student) must approve (sign) the scope planning document. The
signature shall be placed immediately below the following declaration:
i. “I certify that I have read the professor’s instructions regarding this assignment
and that the submitted work is solely my individual effort.”
 Use spell-check to minimize the potential for spelling errors. Proofread the paper prior to submitting it. Points will
be deducted for:
a. Grammatical errors
b. Spelling errors
 In order to score well on this assignment, the Integrated Project Plan should integrate the content of the lectures,
the chapters of the textbook, and the applicable chapters of the PMBOK.
 The intent of this assignment is to help the student perform the creation of the Integrated Project Plan
and conduct
analysis of the plan in order to manage a specific project. The assignment should accomplish that
intent by providing the student with the opportunity to prepare an Integrated Project Plan and answer
several questions for a case study.
 Use the generally accepted project management terminology correctly . Given the intent of item number 3,
points will be deducted each time that vocabulary from the ANSI standard for project management is used
inappropriately.
 Write the assignment according to specifications. Read and follow the instructions that have been provided. Up to
50 points will be deducted for each non-responsive answer.
 The length of this assignment should not exceed five single-spaced, typewritten pages (could be less),
excluding diagrams, tables and charts.
 Use font “Times New Roman,” size = 12 points.
 Page margins should be set to 1 inch on all sides.
 Use appropriae headings and subheadings in the assignment.

 Submit the assignment in printed paper format as well as via blackboard on 7/21/2016. 10 points will
be deducted for each unexcused delay in submitting the assignment.

Appendix A – Project Tracking Database Task List Example

The information in Table A-1is an example only to show you a listing of tasks that are similar to the base
level requirements of this assignment. Be aware that this example is much shorter and simpler than most
WBSs you will find in real life.
TABLE A-1 Project Tracking Database tasks
Order Task Name
1 Initiating
2 Kickoff meeting
3 Develop project charter
4 Charter signed
5 Planning
6 Develop project plans
7 Review project plans
8 Project plans approved
9 Executing
10 Analysis
11 Design
12 Implementation
13 System implemented
14 Controlling
15 Report performance
16 Control changes
17 Closing
18 Prepare final project report
19 Present final project
20 Project completed
NOTE:
 This WBS has not been updated with milestones
 Does not show summary or tiered level tasks associated with the structure of a WBS
 Has not been updated with the proper numbering convention.
The WBS for this Project Tracking Database example separates tasks according to the project management
process groups of initiating, planning, executing, controlling, and closing. These tasks will be the level 2
items in the WBS for this project. Remember that the whole project is considered level 1. It is a good idea
to include all of these process groups because there are important tasks that must be done under each of
them. Recall that the WBS should include all of the work required for the project. In the Project Tracking
Database WBS, the tasks will be purposefully left at a high WBS level (level 3). You will create these
levels, or the WBS hierarchy, next when you create summary tasks. For a real project, you would usually
break the WBS into even more levels to provide more details to describe all the work involved in the
project. For example, analysis tasks for a database project might be broken down further to include
preparing entity relationship diagrams for the database and developing guidelines for the user interface.
Design tasks might be broken down to include preparing prototypes, incorporating user feedback, entering
data, and testing the database. Implementation tasks might include more levels, such as installing new
hardware or software, training the users, fully documenting the system, and s o on.
Instructor: Course Information: