Week 5
Due Week 5: Risk Management Plan
Remember, risk is an uncertain event or condition that can have a positive or negative impact on the project. This week, you will be identifying and analyzing your project risks and developing a risk management plan to monitor and track your project. You will evaluate each task in your project schedule to identify any risk factors associated with the execution of the deliverable. You will then add your list of risk to the risk register template in Doc Sharing. The number of risks will depend on the project deliverables in your schedule; however, 20–25 positive and 20–25 negative risks would be considered the minimum. Review the instructions on the first sheet of the template and complete your risk register in its entirety.
Deliverables for Week 5:
- Use the Risk ter Template spreadsheet found in Doc Sharing (there is a separate tab for each portion of the risk management plan).
- Statement of Participation and status update
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 the statement of participation is
not submitted, the entire team will receive the same grade (including any point
loss from other team members).
I.
Team
Information
PROJECT NAME: |
||||||
MEMBER NAME |
# |
PHONE # |
|
MEETING AVAILABILITY
|
||
1 |
||||||
2 |
||||||
3 |
||||||
4 |
||||||
5 |
||||||
6 |
||||||
7 |
II.
Weekly
meeting schedule
The most successful teams
schedule at least (2) meetings a week throughout the course. Scheduling
standing meetings allows everyone to schedule this time in advance and
coordinate other activities around the scheduled meeting times. Meetings can
change, based on the project leader for the week, however, it is highly
recommended that you set a meeting based on the majority team availability. In
addition to setting meetings, the most successful teams also set a deadline for
drafts to be turned into the project leader each week. Putting this structure
in place early in the course will help the team to achieve a high level of
organization and success.
|
MEETING |
DAY |
TIME |
|
Review weekly assignment |
||
|
Deadline for weekly drafts |
||
|
Review Draft |
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 |
Due |
Weekly |
|
Statement |
Week |
|
|
Project |
Week |
|
|
Project |
Week |
|
|
WBS |
Week |
|
|
Risk |
Week |
|
|
Resource |
Week |
|
|
Communications |
Week |
|
|
Final |
Week |
|
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 |
|
· |
Each |
|
· |
Each |
|
· |
Project |
|
· |
Each |
|
· |
Project |
|
Week 2: Project Charter |
Team Member Responsible |
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
Project leader for Week 2 (submit final |
|
Week 3: Scope Statement |
Team Member Responsible |
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
Project leader for Week 3 (submit final |
|
Week 4: WBS /Project Schedule |
Team Member Responsible |
|
The · |
|
|
· |
Project leader for Week 4 (submit final |
|
Week 5: Risk Management Plan |
Team Member Responsible |
|
The · |
|
|
· |
Project leader for Week 5 (submit final |
|
Week 6: Resource Management Plan |
Team Member Responsible |
|
· |
|
|
· |
|
|
· |
|
|
· |
Project leader for Week 6 (submit final |
|
Week 7: Communications Plan |
Team Member Responsible |
|
This is · |
|
|
· |
Project leader for Week 7 (submit final |
|
Week 8: Final Project Package |
Team Member Responsible |
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
|
|
· |
Project leader for Week 8 (submit final |
NOTE
FOR WEEK 8: If the assigned person places the updated component in the template
each week after grades are complete, you will be building the final project. If
everything works out with the updates, the only thing to do in week 8 review
the contents, format the document for consistency and professionalism and
you’ll be ready for submission.
V.
TIPS FOR CONFLICT MANAGEMENT RECOMMENDATIONS
a. Think about potential barriers and coping strategies
such as barriers to the achievement of the assigned goals, e.g. time zone,time
management, language skills, and identify coping strategies.
b.
Discuss your team operational GROUND RULES: (include
meeting schedule, attendance expectations, agenda, and communication methods.):
c. Consider
how will you manage conflict?Consider how team
members quickly identify conflicts to address them for resolution.
d. Plan
for minor disagreements, inability to agree on submissions? It’s ok to agree to
disagree!
e. Consider
who will have final say for major disagreements? Majority rule or leader?
f. Discuss
the method of communicating with team members who do not deliver?
g. Remember,
every team member may not receive the same grade.
h. If
you feel a situation is going to get out of control, contact the professor
early so that appropriate actions can be taken.
VI.
Commitment
Each
team member is to write an individual commitment statement indicating your
responsibility to the team for your participating, meeting attendance and
completing the assigned deliverables. (if on-site, each team member will sign
their commitment statement).
|
Team Member |
Statement of |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
WEEKLY
PARTICIPATION STATEMENT
Remember, the
weekly participation statement will serve as input to your individual grades. Your
participation statement is a short narrative status report which indicates how
the project went for the week, who did what on the project deliverables and any
additional comments, issues or concerns for the week.
ENTRY EXAMPLE:
Each person on the team completed their assigned work this week. Mary, Joe and
Nick attended all meetings, posted to the team meeting area and completed their
assigned sections on time. John was late with submitting his draft and did not
attend any meetings. Paul was not able to attend meetings due to work
commitments, however he completed all assigned work and submitted it on time.
The team is having problems with overall XYZ and would like the professor’s
direction on how to resolve these issues.
|
Week |
Participation Status Report |
|
Week 1 |
|
|
Week 2 |
|
|
Week 3 |
|
|
Week 4 |
|
|
Week 5 |
|
|
Week 6 |
|
|
Week 7 |
|
|
Week 8 |
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.
| Risk ter | ||||||||||||||||||||
| ID | Risk Name | Risk Description |
Impact | Probability | Risk Ranking |
Positive/Negative | Proactive Response Plan |
Trigger Event | Reactive Contingency Plan |
|||||||||||
| VH,H,M,L,VL | VH,H,M,L,VL | What is the risk color code ? |
Is this a positive or negative risk from the risk matrix? |
What proactively can be attempted to make the risk happen or prevent it? |
What do you think will trigger the event? |
What are your backup plans if the risk should occur? |
||||||||||||||
| 1 | Example: please remove before completing document. Critical equipment does not arrive on time. |
If critical pieces of equipment do not arrive on time, the project will fall behind schedule. |
H | H | Red | Negative | 1. Add activities to the WBS to ensure with the manufacturer that the equipment is being built or shipped as required. 2. Have a member of project team go to the manufacturing plant to ensure equipment parts are in progress and on schedule. 3. Add steps to the WBS to ensure the manufacturer ships on time. 4. Add steps to WBS to track the shipment as needed. |
Parts do not ship on assigned date. |
If possible, have a backup supplier identified and standing by. |
|||||||||||
| 2 | ||||||||||||||||||||
| 3 | ||||||||||||||||||||
| 4 | Very high | |||||||||||||||||||
| High | ||||||||||||||||||||
| Medium | ||||||||||||||||||||
| Impact | Low | |||||||||||||||||||
| Very low | ||||||||||||||||||||
| Very low | Low | Medium | High | Very high | ||||||||||||||||
| Probability | ||||||||||||||||||||
| Risk Matrix | ||||||||||||||||||||
