Jazz Rockers
Name: Date: 07/13/09 A B J NY A B J N Y
Team: Jazz Rockers Instructor: -
Cycle: 4
A B J N Y A B J N Y
Impact Probability Followup date Date Resolved
Risk # Condition Consequence RE Mitigation Plan Status Notes
New Risks
Retired Risks
Risk ID Risk (Condition)
3 We have only a rough idea which
relationship to tackle first such as
One member (the chief architect)
2
leads design of the architecture
Our workload in the program
fluctuates and its always high. Some
13
of us wishes to take more than one
elective in Summer.
Not all team members track time
10
accurately.
Lack of commitment has been
17 observed at time among team
members.
Lack of initiative and proactiveness
18
exists in the team.
We don't have enough standards of
12
our artifcacts.
So far, very less/no understanding
of HLD exists among the other team
members of the team
33
29 Y/N
25 A
23 J/N
30 B
28 Y
32 Y
24 A
26 A
31 B
34 J
4 A/N/Y
Risk (Consequence)
We lose focus from the most important requirements or we do not develop what the client wants.
We will lose the person most technically competent, and the team might be stuck with the design activity.
Productivity of individual is affected.
We might collect unuseful historical data.
This may hamper the schedule of the project
This may results in reactive attitude towards the project than having a proactive attitude
We might produce incomplete/unsound artifacts.
The team members may not be able to contribute to the low level design as effectively as required without the
understanding of overall design.
We are not sure we can implement all our requirements and Not sure if we can complete the product on time or
how much we accomplish by the end of this semester
We will prepare the high level design at beginning and in each iteration we have planned to refine the design
Majority of team does not have experience with Jazz/RTC technologies and documentation from vendor is poor.
Clients have very high expectations from the team with respect to implementation but 12 weeks are not enough to
stand by their expectation
There are MANY technologies we have to learn: EMF, GMF, plugin-development, and Jazz.
We need to learn jazz apis.
Jazz forum is not active as we expected it to be.
We still do not have enough information regarding Jazz API’s to access file revisions.
The release plan seems to be too tight and extremely rigorous
Most team members do not fully understand the HLD due to a
lack of prose documentation (JavaDoc level with a couple sentences for each
class, method, etc.) and method signatures not being fully specified.
We have very little historical productivity data (e.g. LOC/hour) to use in estimating development time.
Impact Prob. Time Strategy
15 18.0
18 20.0
13 26.0
14 24.0
15 32.0
14 32.0
10 22.0
4
2.8
We may end up not
meeting the goal of
3 3 5
100% must have
requirements
We might encounter
interface type
3 3 3
design defects in
later cycles.
Not everyone gets
to work on Jazz 3 3 4
technology despite
the team desires to
We might end up
disappointing our
clients and not 3 2 5
meeting their
expectations
This makes
knowledge transfer
more difficult since 3 2 4
we are dealing with
multiple non-trivial
Even though the
component using
those apis, GSD-RTC
bridge, is isolated
from other parts of
the system, sooner
3 2 3
or later we have to
know the details:
we might not
complete the
implementation
otherwise.
We might not get
the required
information 3 3 3
pertaining to
RTC/Jazz from it.
This might create
obstacles in detailed
design that requires 3 2 3
use of these or
related apis.
Even slip in one of
the milestones /
release on time will
have a disastrous 4 3 3
effect on the entire
product schedule
deliveries
The team may
spend excess time
studying/trying to
understand the high-
level design and
working
with/depending on
the 3 3 5
development
manager explaining
in person what the
various classes,
interfaces, and
methods are
supposed to do.
It might be difficult
to show our client
quantitatively what
3 2 3
we can do within
the time
constraints.
Mitigation Plan
Review and formally inspect SRS and send it to the
clients for an initial approval.
No restriction on taking courses. Courses other
than studio must be given lower priority. Everyone
must put in efforts worth 48 hours every week
Align individual goals with team goals and revisit it
Have thorough HLD reviews and KT sessions and
understand the resources (technical resources like
APIs etc.) required and prepare a list of questions
ith specific doubts that can be answered by the
dev manager to help you through the completion
of your module
Scope negotiation with clients after cycle 1 and 2,
possibely prioritizing requirements
Spend more time on reviewing interfaces of
methods
Conduct knowledge transfer session
Make sure all features are delivered at each
release. If not, discuss with and promise Marcelo
what can be delivered by the subsequent releases.
Have a technology expert for each technology or
examine code generated by the technology
Continue performoing experimentation
Inform clients of this risk and get them to contact
with the person with IBM
Perform another experiment
Nice-to-have requirements have been scheduled
to be delivered in the last cycle, so missing any of
the milestones will have a lesser impact on must
have requirements schedule.
Detailed design should be done by the component
owner with the help of development manager and
design should be updated accordingly.
After cycle 1, go ask Eduardo to perform better
esitmate for subsequent cycles.