Risk Categorization Table
Development Development
process in place, process
No formal process
Use of defined engineering process established, established, but L
used
effective, followed not followed or is
by team ineffective
Peer reviews are Team expects to
Peer reviews are
Early identification of defects incorporated find all defects M
used sporadically
throughout with testing
Formal change Change control
control process in process in place, No change control Terasoft has a successful change
Change control for work products L
place, followed, not followed, or is process used control process
effective ineffective
Defect tracking is Defect tracking
No process in
defined, process defined,
Defect tracking place to track L
consistent, but inconsistently
defects
effective used
Development environment factors
Stable, no
Platform under
changes Some changes
development
Hardware platform expected, under evolution, Too soon
along with
capacity is but controlled
software
sufficient
Tools available, Tools invalidated,
validated, some proprietary, or
Tools in place,
development major
Tools availability documented, Too soon
needed (or development
validated
minimal needed, no
documentation) documentation
Some
Configuration fully No configuration
Configuration management configuration Too soon
controlled controls in place
controls in place
Risk Categorization Table
All areas following
Some security
security No security
measures in place,
guidelines, data measures in
backups done,
backed up, place, backup Terasoft has standard security
Security disaster recovery L
disaster recovery lacking, disaster procedures, which we will follow.
considered, but
system in place, recovery not
procedures lacking
procedures considered
or not followed
followed
Complete support
Adequate support Little or no
at reasonable
at contracted support, high cost,
Vendor support price and in L
price, reasonable and/or poor
needed time
response time response time
frame
Staff factors
Staff in place, no
Staff available, Staff not available,
turnover
some turnover high turnover
expected, working
expected, some expected, many
Staff adherence to task on assigned L
conflict in time members spend
tasks, few
allocation, some much time fire
diversions and
fire fighting fighting
little fire fighting
Some disciplines Some disciplines
Good mix of
Mix of staff skills inadequately not represented at L
disciplines
represented all
Very experienced Some experience No experience in
Product knowledge at developing this in developing this developing this M
type of product type of product type of product
Extensive Some experience Little or no
Software development experience experience with with similar experience with M
this type of project projects similar projects
Risk Categorization Table
Subcontractor Subcontractor
Subcontractor
activity is falling activity is behind
activity is on-
behind schedule, schedule, or
schedule and all
or some subcontractors
Subcontractor retention required L
subcontractors may not be able to
subcontractors
cannot be remain committed
are available for
available for to the project as
planned activities
planned activities. required.
Training not
Training for some
required, or No training plan or
areas not available
Training of team training plan in training not readily L
or training planned
place and training available
for future
ongoing
Strongly
Little or no
committed to Willing to do what
commitment to the
Team spirit and attitude success of it takes to get the M
project, not a
project, job done
cohesive team
cooperative
Milestones met,
All milestones Productivity low,
some delays in
met, deliverables milestones not
Team productivity deliverables, Too soon
on time, met, delays in
productivity
productivity high deliverables
acceptable
Maintenance factors
Structurally
Certain aspects
maintainable (low Extremely difficult
difficult to maintain
Complexity complexity to maintain (high Too soon
(medium
measured or complexity)
complexity)
projected)
Team in place Team experiences
Team is unable to
can be responsive delays but
Change implementation respond to Too soon
to customer acceptable to
customer needs
needs customer
Risk Categorization Table
In place,
Significant
experienced, Missing some
Support personnel discipline or Too soon
sufficient in areas of expertise
expertise missing
number
Top 10 Risks Report template
ID Risk Item Probability Loss Risk Resolution Who Date
Exposure Approach
1
2
3
4
5
6
7
8
9
10
Risk Response Report template
ID Risk Item Trigger Value Risk Resolution Who Date
Exposure Approach
1
2
3
4
5
6
7
8
9
10
Weekly Risk Change Report template
Risk Item Rank This Last Rank # Weeks Resolution Approach
Week On List
1
2
3
4
5
6
7
8
9
10