Sheet1
Risk Desription Probability Loss Weight
QARun compatibility QARun environment 7 8 56
problems is a third party
application, and
Compuware does not
consult us when
QARun changes. New
releases might mean
new bugs in the
QARun tool that affect
our work.
Workload estimation Workload is estimated 6 7 42
too low.
Members have too Because this is a 7 6 42
many other tasks course for HUT and
participants are
students there might
become problems with
other courses, part
time jobs and other.
Inefficient implement- 7 6 42
test-bugfix cycle
Members get sick One member must be 6 6 36
absent due
sickness/injury for a
longer time than a
week.
Opposition In the release phase 8 4 32
an opponent group
should make some
system testing. This
might become
problem because of
FS security needs.
Lack of motivation For some reason one 8 4 32
or more of members
loses his/hers
motivation to the
project.
Project resources not Delivery of some 4 7 28
available piece of hardware or
software is delayed
making work difficult.
Page 1
Sheet1
Lack of knowledge / In project we might 5 5 25
competence meet some area
where our knowledge
is poor.
Inefficient All communication 5 5 25
communication between between group
project members members are critical.
So if there are breaks
it can be fatal.
Responsibilities not Big project compared 4 5 20
clear enough to resources might
cause
misunderstanding
about who is
responsible for which
tasks.
Access restrictions Non-FS group 3 6 18
members are not
allowed in FS
premises by
themselves.
Product release Because we are 2 8 16
changes in the middle of working with and
project existing product
changes in the
product might cause
problems to our
system.
Requirements will For some reason 4 4 16
change in the middle of customer wants to
the project change the
requirements.
Instructor too busy Instructor is too busy 3 5 15
to give any instruction
or follow the project.
Poor coding style In a project with many 2 7 14
programmers, diverse
styles in coding might
become problem.
Major problems in the Some major problems 2 6 12
system design might occur in system
architechture during
implementation.
Unfamiliar tools Tools are not familiar 2 6 12
to members.
Page 2
Sheet1
The customer isn't End product must 3 4 12
satisfied with the satisfy customers
product needs.
Demo For demo we must 4 3 12
install QARun to
laptop. No one knows
if this can be done.
Customer goes out of 1 10 10
business
Source files are lost For some reason the 1 9 9
source files are lost.
Customers steering Customer try to steer 2 4 8
project to something
else that they wanted
in requirements
specification.
CAT does not fit to Some scripts could be 2 4 8
application hard or impossible to
implement with CAT
tools.
Project members leave Project member(s) 1 7 7
the project leaves the project for
some reason.
Page 3
Sheet1
Possible solution Outcome
Not much we can do. Written scripts are no
longer valid. Scripts
must be retested and
partly rewrited.
Though work is split in Project is delayed.
small chunks this still Members are
difficult. It is the overloaded.
number of chunks
which creates
problem. Just
watching the
estimates and
fulfillments and react
as fast as possible.
Follow members' time One member
usage in the project allocates too much
and discuss about work for a week and
timetables and cannot complete
possible workarounds, defined tasks and
if seems necessary. project delays.
Project is delayed
As a project manager Resources are
there is not much to dimished. Tasks must
do just hope and be reallocated.
avoid pushing
members too hard.
Just explain situation Opposition cannot be
to and discuss with completed.
courses
administrators.
Observe member time One member leaves
usage and frustration. group or is not longer
No-one should be counted as resource.
stressed too hard.
Make sure all possible Delays project.
resource changes and
extra requirements
are known as early as
possible and sent
forward to the
customer.
Page 4
Sheet1
Just training and This delays project
reading. and takes some
resources.
Weekly meetings, Member are
email and overloaded. member
documentation don't know what to do.
manager are the Other risk occur but
solution to this they not reacted fast
problem. enough.
Communications must Members don't know
be improved. Maybe it what to do and when
is best to make some to do.
kind common TODO-
list.
Plan working Make working
schedules in advance impossible.
and arrange for better
access if necessary.
There is not much we Written scripts are no
can do. longer valid. Scripts
must be retested and
partly rewrited.
Discuss with the Parts of the
customer and write implementation
exact requrements become obsolete.
specification.
Try arrange meetings Project slides to
as early as possible. wrong trails.
Inform customer
frequently how project
advances.
Guidelines for Code is not
programmers. At least maintainable and
in the beginning code quality is poor.
should be read also
by someone else.
Programmers must be Implemented code
included the design become partly
process, at least on obsolete.
the level of reading
and commenting on
the plans.
This can be solved by Members need more
training and with help training and this takes
of the other members. time so project is
delayed.
Page 5
Sheet1
Close work with Customer does not
customer. Quality gain any benefit from
measurements the end product.
through project.
Proper documentation
and following the
guidelines.
Discuss with course Project is delayed
administration or try to because hours must
install programs. be used to work which
is not progressing our
project anyway.
Not much we can do. Project is ended.
Backups must be All or part of the work
taken as frequently. is lost.
Try to keep our minds Project delays and
and refer back to the end product is never
requirements ready.
specification.
Do some testing. Script cannot be
implemented.
Workload must be Resources are
divided equally so that decreased and
no one gets workload is incresed.
overstressed. Tasks must be
Situation must be reallocated.
observed in the
weekly meetings.
Page 6
Sheet2
RiskDesriptionProbabilityLossQARun compatibility problemsQARun environment is a third party application, and Compuware does no
Workload estimationWorkload is estimated too low.6742Members have too many other tasksBecause this is a course for HUT and participants are students the
Inefficient implement-test-bugfix cycle7642P
Members get sickOne member must be absent due sickness/injury for a longer time than a week.
OppositionIn the release phase an opponent group should make some system testing. This might becom
Lack of motivationFor some reason one or more of members loses his/hers motivation to the project.Project resources not availableDelivery of some piece of hardware or software is delayed making work d
Lack of knowledge / competenceIn project we might meet some area where our knowledge is poor.Inefficient communication between project membersAll communication between group members are cri
Responsibilities not clear enoughBig project compared to resources might cause misunderstanding abo
Access restrictions Non-FS group members are not allowed in FS premises by themselves.
Product release changes in the middle of projectBecause we are working with and existing product chan
Requirements will change in the middle of the projectFor some reason customer wants to change the re
Instructor too busyInstructor is too busy to give any instruction or follow the project.3Poor coding styleIn a project with many programmers, diverse styles in coding might become problem.Major problems in the system designSome major problems might occur in system architechture during i
Unfamiliar toolsTools are not familiar to members.2612
The customer isn't satisfied with the productEnd product must satisfy customers needs.3DemoFor demo we must install QARun to laptop. No one knows if this can be done.4
Customer goes out of business11010Not much we can
Source files are lostFor some reason the source files are lost.199Customers steeringCustomer try to steer project to something else that they wanted in requirements sp
Page 7
Sheet2
D>LossWeightPossible solutionOutcome
application, and Compuware does not consult us when QARun changes. New releases might mean new bugs in the QARun tool that affect o
TD>742Though work is split in small chunks this still difficult. It is the number of chunks which creates problem
UT and participants are students there might become problems with other courses, part time jobs and other.76
TD>42Project is delayed
for a longer time than a week.6636As a project manager there is not much to do just hope a
ome system testing. This might become problem because of FS security needs.8432Just exp
his/hers motivation to the project.8432Observe member time usage and frustration. No-one
or software is delayed making work difficult.4728Make sure all possible resource changes a
ea where our knowledge is poor.5525Just training and reading.This delays proje
tion between group members are critical. So if there are breaks it can be fatal.5525Weekly m
s might cause misunderstanding about who is responsible for which tasks.4520Communicat
premises by themselves.3618Plan working schedules in advance and arrange for better acce
orking with and existing product changes in the product might cause problems to our system.2816
son customer wants to change the requirements.4416Discuss with the customer and write e
llow the project.3515Try arrange meetings as early as possible. Inform customer frequently h
s in coding might become problem.2714Guidelines for programmers. At least in the beginnin
ccur in system architechture during implementation.2612Programmers must be included the
D>612This can be solved by training and with help of the other members.Members need more train
fy customers needs.3412Close work with customer. Quality measurements through project.
his can be done.4312Discuss with course administration or try to install programs.10Not much we can do.Project is ended.
>199Backups must be taken as frequently.All or part of the work is lost.
that they wanted in requirements specification.248Try to keep our minds and refer back to th
Page 8
Sheet2
>Outcome
bugs in the QARun tool that affect our work.7856
ber of chunks which creates problem. Just watching the estimates and fulfillm
ther.7642Follow members' time usage in
er there is not much to do just hope and avoid pushing members too hard.Resourc
>432Just explain situation to and discuss with courses administra
r time usage and frustration. No-one should be stressed too hard.One member le
sure all possible resource changes and extra requirements are known as early as po
eading.This delays project and takes some resources.
525Weekly meetings, email and documentation manager are the
D>20Communications must be improved. Maybe it is best to make som
advance and arrange for better access if necessary.Make working impossible.2816There is not much we can do.Writte
scuss with the customer and write exact requrements specification.Parts of t
ossible. Inform customer frequently how project advances.Project sl
programmers. At least in the beginning code should be read also by someone else.Programmers must be included the design process, at least on the level of reading and
Members need more training and this takes time so project is delayed.Project is delayed because hours must be used to
art of the work is lost.
o keep our minds and refer back to the requirements specification.Projec
Page 9
Sheet3
4 10 11 4 6 17 7
28 174 1 1 2 19 82
19 30 1 1 2 184 43
33 136 1 1 2 116 99
39 0 1 1 2 0 18
16 76 1 1 2 90 50
10 127 1 1 2 66 31
18 80 1 1 2 78 61
31 80 1 1 2 127 15
30 63 1 1 2 26 46
49 93 1 1 2 82 103
33 104 1 1 2 85 45
20 66 1 1 2 77 24
48 107 1 1 2 28 82
53 58 1 1 2 68 44
19 69 1 1 2 91 31
17 82 1 1 2 95 45
35 78 1 1 2 110 40
16 34 1 1 2 66 69
45 41 1 1 2 114 56
4 75 1 1 2 62 98
29 0 1 2 2 19 17
21 42 1 1 1 36 32
18 95 1 1 1 71 46
Page 10
Sheet4
Desription
Risk Loss Possible solution
Weight
Probability Outcome
QARun7 8 party application, and Compuwaredo. are no longer valid.QARun changes. re
environment is a third
QARun compatibility problems 56 Written scripts
Not much we can does not consult us when Scripts must be N
Workload is estimated too low.
6
Workload estimation 7 42 Project is delayed. Members still difficult. It is the num
Though work is split in small chunks this are overloaded.Because this is a other tasks
7 6 42 Follow One member allocates project and with other course
members' time might become much work for a about tim
Members have too many course for HUT and participants are students thereusage in thetoo problemsdiscuss week and
7 6 42
Inefficient implement-test-bugfix cycle Project is delayed
One member must be absent due sickness/injurya project manager there week. to do just be reallocated.6
Members get sick 6 36 a longer time than is not much
As for Resources areadimished. Tasks must hope and avoid
In the release phase an opponent group should make some systemto and discuss with become administrators.
Opposition 8 4 32 Opposition cannot be completed.
Just explain situation testing. This might courses problem becau
For some reason 4 of members
8 Observe member time usage and frustration. No-one counted
One member leaves group or
Lack of motivation one or more32 loses his/hers motivation to the project.is not longershould beas
Delivery of some piece of hardware or software is delayed making work difficult. and extra requirements
4 7
Project resources not available 28 Delays project.
Make sure all possible resource changes
In project we might meet some
5 5 25 Just training is poor.
This reading.
Lack of knowledge / competence area where our knowledge anddelays project and takes some resources. All communication between projectmembers
5 between group members Member are and documentation manager are the to
Weekly meetings, email breaks it can be fatal.
Inefficient communication 5 25 are critical. So if thereare overloaded. member don't know whatsol
Big project compared to resources might cause misunderstanding aboutimproved. Maybe and best to make som
4 5 20
Responsibilities not clear enough Members don't know responsible for which tasks.Communications must be who iswhat to do it is when to do.
Non-FS group members are not allowed in
3 Plan working themselves.
Make working advance and arrange
Access restrictions 6 18 FS premises by schedules inimpossible. for better acces
Because we are working with and existing product changes in thescripts do.causevalid. Scripts our system
2 8 16 There is not much we can are no longer problems to must be re
Product release changes in the middle of project Written product might
For some reason 4 16
will change in the middle of the project Parts customer and write exact requrements specifica
Discuss with the of the
Requirements 4customer wants to change the requirements. implementation become obsolete.Instructor is too 5 15
3 Try arrange meetings as to wrong trails.
Project slides
Instructor too busybusy to give any instruction or follow the project. early as possible. Inform customer frequ
In a style
2 7 14 Guidelines for might become problem.
Code is not maintainable in the beginning code shou
Poor codingproject with many programmers, diverse styles in codingprogrammers. At leastand quality is poor.
Some major problems might occur
2 6 12 Programmers must implementation.
Implemented code become partly obsolete.
Major problems in the system design in system architechture during be included the design process, at least on th
Tools are not
2 6 12 Members training and with help of the other member
Unfamiliar tools familiar to members. This can be solved byneed more training and this takes time so p
End product must 4 12
isn't satisfied with customers needs. Customer does not gain any benefit from the end pro
The customer 3 satisfy the productClose work with customer. Quality measurements through projec
For 4 install QARun to laptop. Discuss with course administration or hours must be used to wo
Project is delayed because
Demo demo we must3 12 No one knows if this can be done. try to install programs.
1 10
Customer goes out of business 10 Project is ended.
Not much we can do.
For are lost 9 9 Backups must or part of as frequently.
1
Source filessome reason the source files are lost. All be taken the work is lost.
Customer try to steer project 8 Try to keep our minds andand end product is never ready.2 Project delays refer back to the requirements specific
Customers steering 4to something else that they wanted in requirements specification.
Page 11
Sheet4
e no longer valid. Scripts must be retested and partly rewrited.
d. Members are overloaded.
ocates too much work for a week and cannot complete defined tasks and project delays.
imished. Tasks must be reallocated.
ot be completed.
ves group or is not longer counted as resource.
ct and takes some resources.
rloaded. member don't know what to do. Other risk occur but they not reacted fast enough.
now what to do and when to do.
possible.
e no longer valid. Scripts must be retested and partly rewrited.
ementation become obsolete.
wrong trails.
tainable and quality is poor.
de become partly obsolete.
more training and this takes time so project is delayed.
not gain any benefit from the end product.
d because hours must be used to work which is not progressing our project anyway.
work is lost.
nd end product is never ready.
Page 12