PMAN 634 Spring 2011 Team Project Requirements

PMAN 634 of 12 Team Project Requirements

Copyright © 2006-2011 by Moe Shahdad Revised by Rudy J. Watson with permission

PMAN 634

Team Project Requirements



Table of Contents

INTRODUCTION ........................................................................................................................................ 3 PROJECT SELECTION GUIDELINES ................................................................................................... 3 PROJECT DELIVERABLES ..................................................................................................................... 4

PROJECT PROGRESS REPORTS..................................................................................................................... 4 FINAL PROJECT DELIVERABLE ................................................................................................................... 6

PROGRESS REPORTS............................................................................................................................... 7 MICROSOFT PROJECT ........................................................................................................................... 7 PROJECT SCHEDULE .............................................................................................................................. 8 PROJECT EVALUATION AND GRADING............................................................................................ 8 APPENDIX A: RUBRIC FOR TEAM PROJECT DELIVERABLES.................................................. 10 APPENDIX B: TEAM MEMBER CONTRIBUTION............................................................................ 12



Introduction The purpose of the team project is to develop an integrated project management plan for a project and to organize and track the project throughout its life cycle. The project requires the students to apply project management tools and techniques covered in this course to a project that closely models a real-life situation. In practice, the development of a project plan such as this is usually the result of a group effort. Therefore, for the purposes of this assignment, the instructor will assign each student to a team. This document specifies the detailed requirements of the team project, including selection guidelines, schedule, progress reports, deliverables, and evaluation criteria.

Project Selection Guidelines Each team will select a project based on the interests of its members and consensus of the team. Each team must select a project, assuming that the team is a contractor making a competitive project proposal to a senior manager in a customer company for a service contract. The project management plan is to be evaluated by the customer company, in a competitive setting, where the proposing team is competing to win a contract. The students will have flexibility in choosing their projects. For example, the projects may include:

• Event management (presidential elections, conferences, Olympics)

• Custom system development (IT projects, computer networks)

• Construction (remodeling, new high-rise, new home) The project should involve about 25 to 50 extremely high level tasks (this may result in an artificial situation for academic purposes where the plan is not as detailed as it would be for execution in real life). What is most important here are the project management processes utilized not the project execution. The project could involve development of a new product or service, or a major



revision or release of an existing product or service. It must be a long-term one, with fixed price and duration of at least three years. The proposed price includes cost (budget) plus profit. The budget must include at least the following three categories of resources:

• Human resources • Equipment • Consumable materials

The emphasis of this assignment is on the management of the project, rather than the technology used in the project. In a real life project, the technological viability of a project is paramount. However, in this course, although the project must be reasonably achievable, its soundness is not a critical factor. For example, in a remodeling project, it is not critical to lay out detailed architectural floor plans, or to make sure all the equipment and material are accounted for. Rather, it is important that the project have a plan, work breakdown structure, schedule, cost, and etc. For reference purposes, it is easier if each team chooses names for the proposing company as well as the customer organization.

Project Deliverables Project Progress Reports Each team will prepare project reports and a project management plan for review, discussion, and approval. In writing your plan, assume that you are working for a company, submitting a project management plan to an executive committee for approval. The first two progress reports are the statement of work and the project charter.



Project Statement of Work Each team will first prepare a statement of work for their project for approval by the instructor, as outlined on Page 67 of Heldman. Project Charter The next step for the team is to prepare a project charter for review, discussion, and approval. Chapter 2 of Heldman includes an outline of the charter on Page 72, as well as tools and techniques for developing the charter. The rest of the progress reports are drafts of the project management plan leading up to the final deliverable. The project management plan should cover the following topics, as well as any other topics that are of interest to your particular project:

• Overview

• Objectives • Scope • General approach • Contractual aspects

• Schedule • Resources

• Personnel • Risk management plans

• Evaluation methods Each team can decide on a suitable outline for their project management plan. The scope of the project should be broad enough to cover at least the following knowledge areas:

• Project Integration Management • Project Scope Management • Project Time Management • Project Cost Management • Project Risk Management • Project Human Resource Management



Final Project Deliverable The final project deliverable should elaborate on the items in the project management plan, and at a minimum, it should include the following details:

• Project selection • Project scope statement • Work breakdown structure (WBS) • Project budget • Project schedule • Project resource allocation • Methods and techniques for monitoring controlling the

project • Project risk management • Project organization • Any Assumptions and dependencies • Any analysis models and/or techniques • Procedures for terminating the project

The final report must be submitted to Tycho by the deadline specified by the instructor. The final report must be in MS Word with embedded Excel, PowerPoint, screen shots or other diagrams, as necessary. The accompanying Microsoft Project (MSP) plan should be submitted as a separate document.



Progress Reports As specified in the Project Schedule section, each team will present their project progress reports at the specified sessions. Class members will review the reports, providing insights, comments, or questions. Progress reports must be posted to Tycho for review and discussion. Each progress report must be self-contained so that the reviewers would have all the necessary information to review the project up to that point. The reviewers should not need to consult previous progress reports to review the current one.

Microsoft Project MS Project must be used in all cases where it provides the necessary functions for project management. This includes at least the following:

• Project planning • Budgeting

• Scheduling

• Resource allocation • Reporting



Project Schedule Your project has a number of milestones and a final report. Several of the milestones require progress reports to be submitted to Wed Tycho, as specified below: Session Progress

Report Project Phase

1 No Team Formation - Project Selection 2 Yes Project Proposal - SOW 3 Yes Project Organization - Charter 4 No Project Scope Statement - Planning 5 No Budgeting 6 Yes Scheduling 7 No N/A 8 No Risk Analysis 9 No Resource Allocation 10 Yes Refining 11 No Monitoring 12 Yes Final Project Review All project progress reports must be self-contained so that the reviewers can follow, understand, and evaluate each report independent of the previous reports. Project Evaluation and Grading Your project grade has three components:

• Team Project Deliverables • Team Member Contribution • Project Review

The percentage of each grade is specified in the syllabus.



Your project grade is a function of the following:

• Degree of complexity of the project o Number, variety, and inter-dependence of tasks

• Completeness of the project • Responses to questions • Clarity of written presentation • Handling of questions following progress report

presentations • Reviewing progress reports presented by other students

and providing input following their presentations • On-time posting of your reports to Tycho for class

review Appendix A specifies the evaluation criteria for Team Project Deliverables (TPD). All team members will receive the same grade for this item. Note that your TPD grade is not just for your final report; rather, it is a reflection of all the progress reports that you have submitted throughout the semester. Upon completion of the project, each team member will evaluate the contributions of other members. The instructor will use this evaluation to assign a Team Member Contribution (TMC) grade to each student. The Team Member Evaluation form in Appendix B must be submitted the Assignments Folder. The Team Project requires a number of progress reports, specified in the Project Schedule Section of this document. All progress reports must be posted to course conferences for review and discussion by other class members. Each class member will receive a Project Review (PR) grade for his/her contribution to these conferences. The rubric for this grade is the same as the rubric for Class Contribution.



Appendix A: Rubric for Team Project Deliverables A (Superior)

1) The project scope is sufficiently complex to demonstrate all required Project Management Knowledge Areas

2) All the required knowledge areas are substantively and thoroughly addressed by the final report

3) Each progress report thoroughly covers the topics that are assigned to that progress report

4) There is evidence of extensive use of MS Project for all applicable phases of project life cycle

5) There is evidence that the team has studied extensively external references for their project, and references are cited in the final project report

6) When reviewing their progress reports, the team responded satisfactorily to all the questions asked of them by class members

7) The final report adheres to APA guidelines 8) All deliverables are posted on time 9) Each progress report, as well as the final deliverable,

is clear, easy to read, free of grammatical errors, and can be understood independent of other reports

B (Satisfactory)

1) The project scope is reasonably complex to demonstrate all required and optional Project Knowledge Management Knowledge Areas

2) All the required knowledge areas are reasonably addressed by the final report

3) Progress reports contain mostly relevant information about the topics that are assigned to the reports

4) MSP have been used for some of the phases of project life cycle

5) The team has studied external sources, and references are cited in the final project report

6) The final report substantially adheres to APA guidelines 7) All deliverables are posted on time 8) Progress reports and the final report are reasonably

clear to read and follow



C (Poor)

1) The project scope is not complex enough to demonstrate all the required Project Knowledge Management Knowledge Areas

2) Only a subset of required knowledge areas are substantively and thoroughly addressed by the final report

3) Progress reports contain insufficient relevant information about the topics that are assigned to the reports

4) There is insufficient evidence of the use of MSP for the project

5) The team has not referred to external sources for their project

6) The final report has some violations of APA guidelines. 7) The final report is posted on time 8) The report is not easy to follow



Appendix B: Team Member Contribution Team Name ___________________________ Evaluating Member Name ___________________________ Team Member Last Name

Proactively communicated with other team members

Contributed to research and understanding

Contributed to preparing progress reports

Contributed to preparing the final report

Proactively moved forward the task of the team

Overall evaluation (1 – 5)

• Evaluating member is the name of the person filling in this form and the name to put into the system file name.

• Across the top row, write the names of your team members that you are evaluating, putting your name last.

• Evaluate your team members and yourself for each characteristic according to the following scale and then enter your overall evaluation of 1 through 5 in the last row:

o 5: Excellent contribution o 4: Good contribution o 3: Some contribution o 2: Very little contribution o 1: No contribution at all

PMAN 634 Spring 2011 Team Project Requirements

Documents

Transcript of PMAN 634 Spring 2011 Team Project Requirements