Briargrove Risk Assessment Matrix
Briargrove Risk Questionnaire
Grantham University
PM Integration/Assignment Week 6
May 9, 2017
Risk management seems to be the one strategy that is lacking for the majority of project teams. Very few project teams have a comprehensive risk management plan that includes a precise definition of the risks that may impact their projects. In order to improve risk management the ability to identify risks early is imperative. Presenting project members with a risk questionnaire and then compiling and analyzing the data is a good first step in early risk identification.
Risk Questionnaire
It is best to keep the questions to a few that are most relevant to the project you are currently working on. Kendrick (2015) believed that twelve questions was just enough to make the survey effective. The number of business areas being investigated should also be limited. The most effective surveys only focus on a few key areas. According to Kendrick (2015), there should never be more than 20 areas included in the risk survey. Additionally, the number of available responses should be limited as well. Kendrick (2015:230) suggested limiting the number of responses available for each question to “three to five clearly worded responses” (Kendrick, 2015).
Once all the questionnaires and surveys have been filled out and collected, the data should be analyzed so that an overall risk assessment of the project can be made. Another benefit of having all the risk survey data compiled is that it is much easier to spot trends. If there are certain questions that are consistently receiving high risk scores, then those should be looked at more closely (Kendrick, 2015).
To ensure that the risk survey is thorough, three mains sections should be addressed. The first is any external project factor. An example of this would be any schedule delays to the project because legal took longer than anticipated to go over contracts. The second is development issues. An example of this would be that the software that is being deployed will only run on a Windows 2013 server and the operating system of the current server is 2010. The last section is any internet project factor. An example of this would be if there is any conflict and/or animosity among the team members that is interfering with their ability to work together as a team to produce the project deliverables (Kendrick, 2015).
Project Risk Questionnaire – Briargrove Centralized Learning Network (Kendrick, 2015: 232-241)
Section 1: Project Parameter and Target User Risks
- Scope stability [pic 1][pic 2][pic 3]
1.2. Project Budget Resources[pic 4][pic 5][pic 6]
1.3. Project Deadline[pic 7][pic 8]
[pic 9]
1.4. Total Project Length[pic 10][pic 11]
[pic 12]
1.5. Total Effort-Months Estimated for this Project[pic 13][pic 14][pic 15]
1.6. Peak Size of Core Project Team (Key Contributors Critical to the Project)[pic 16][pic 17][pic 18]
1.7. Project Manager Experience[pic 19][pic 20][pic 21]
1.8. User Support for the Project Objectives (Scope, Schedule, resources)[pic 22][pic 23][pic 24]
1.9. Prioritization of Scope, Schedule and Resources (constrained, optimized, accepted) [pic 25][pic 26][pic 27]
1.10. Number of Different Types of Users (market segments)[pic 28][pic 29][pic 30]
1.11. Project Team Interaction with Users During Project[pic 31][pic 32][pic 33]
1.12. User Need for the Project Deliverable[pic 34][pic 35][pic 36]
1.13. User Environment and Process Changes Required to Use Project Deliverable[pic 37][pic 38][pic 39]