MGMT- 404 PROJECT MANAGEMENT
STATEMENT OF PARTICIPation
This document will contain the information needed for your team operations, guidelines and commitment. It should be kept in doc sharing and each update should have a version control identifier (e.g., Team A SOP v1, v2, v3, etc.).
IMPORTANT NOTE: The statement of participation must be posted in the team’s doc sharing area and the final submission must be available for the team to review and approve each week. Approval can be achieved by downloading the document. If you have disagreements, it is critical to contact your project leader and get a correction posted immediately. The professor should be notified of any disagreements. If ...view middle of the document...
MEETING | DAY | TIME |
Review weekly assignment | Mon/Wed | 9pm |
Deadline for weekly drafts | Saturdays | 9pm |
Review Draft | Saturdays | 9pm |
III. PROJECT Description
Brief synopsis of your proposed project in 200 words or less. Describe the overall project with enough information to gain approval for your team to use this project as the course project. If you are working on a project in the instructions, you do not need to gain approval. Approval is only needed if you select a project outside of the list in the course project instructions.
IV. Team Management Plan
a. Team Leadership: Designate the project leader for each major deliverable. Project leader can be rotated so that each team member experiences the leadership responsibilities or you can establish one primary project leader with a back-up to assist. The project leader has specific responsibilities each week as follows:
a. Schedule the weekly meetings in i-Connect, facilitate and record the meetings.
b. Set the deadlines for submissions each week.
c. Compile the team submissions into one document and submit to the dropbox. “ONLY ONE” submission is required and this is submitted by the project leader.
d. Update the statement of participation status each week and submit to dropbox for the team review.
e. Place the final submission and updated statement of participation in the team’s doc sharing area each week.
f. Contact the professor with any team questions, issues, or conflicts.
Weekly Deliverable | Due | Weekly Project Leader Assignment |
Statement of Participation | Week 1 | Raquel Godoy |
Project Charter | Week 2 | Jade Xiong |
Project Scope Statement | Week 3 | Jade Xiong |
WBS and Network Diagram | Week 4 | Jade Xiong |
Risk Management Plan | Week 5 | Jade xiong |
Resource Management Plan | Week 6 | Jade Xiong |
Communications Plan | Week 7 | Jade Xiong |
Final Project | Week 8 | Jade Xiong |
b. Task assignments: How will tasks be assigned? Every team member should have an active role in creating the tasks for each major deliverable. All (8) weeks of assignments must be completed.
Week 1: Statement of Participation | Team Member Responsible |
* Team Information | Each team member submit to project leader |
* Project Leadership | Each team member submit to project leader |
* Task Assignments Weeks 1-8 (Each project leader can assign the task for their week or team members can select what they want to work on each week). | Project leader for Week 1 |
* Commitment statement | Each team member submit to project leader |
* Weekly Status Update | Project leader for Week 1 update the status update at the end of the SoP document and submit to dropbox and place copy in doc sharing for team review. |
Week 2: Project Charter | Team Member Responsible |
* Mission/Project Purpose | |
* Project Description, Product and deliverables | |