Risk Data - Carnegie Mellon University - MSE Studio

Document Sample
Risk Data - Carnegie Mellon University - MSE Studio Powered By Docstoc
					Rank    Title

       1 Experiments

       1 R71

       2 R2

       2 R718

       3 R4

       3 R720

       5 GWT3

   999 R3

   999 R25

   999 R29

   999 R14

   999 R24

   999 R30


   999 R19

   999 R1

   999 GWT Javascript Debugging

   999 GWT prototyping

   999 R7

   999 R8

   999 R9

   999 R10

   999 R11
999 R12


999 R13

999 R15


999 R16

999 R17

999 R18

999 R20

999 R21

999 R22

999 R23


999 R52

999 R26

999 Missing Milestones

999 R31

999 Requirement risks

999 Architecture interface
999 Planning change

999 Requirement budget

999 R999

999 GWT2

999 R32


999 R33
999 EOSP_budget


999 Proof of concept




999 Summer transition

999 Tracking audit

999 borrowing time

999 R70

999 R72

999 R73

999 R74

999 R75

999 R76

999 R77

999 R78

999 R79

999 R79

999 R79

999 R710

999 R711

999 R712

999 R713

999 R714

999 R715
999 R716

999 R719

999 R901

999 R902

999 R903

999 R904
Statement                                                                                                  Closed
Not enough experiments are being done on the architecture. This may push off important design
decisions to Summer                                                                                          TRUE

UI Prototypes are developed "Just in time"; late prototypes may cause delays in development                  FALSE
There are open questions concerning step 4 (Privacy); might not be able to fully specifiy later steps in
the SQUARE process                                                                                           TRUE
The team is not reserving enough time for testing and doesn't the discipline for testing; Releases
may have bugs and the team miss its quality goal                                                             FALSE
Its unclear what steps of each technique used as part of the SQUARE process are inside or outside
the tool; might miss requirements or increase our project scope                                              TRUE

Team velocities are "low"; may not be on pace to finish the project                                          FALSE
GWT is making us make architectural (code-oriented) design decisions. These decisions may not
conform with our overall architecture.                                                                       TRUE
We haven't come to an agreement with the client abt quality attributes; might impact planning and
allocation of resources                                                                                      TRUE
Some of our proposals are unclear and open to interpretation; might make following them difficult
to do making us less productive                                                                              TRUE

GWT imposes certain architectural constraints; it may have a negative impact our middle tier                 TRUE

We are not finishing our milestones; might slip dependent tasks and not achieve semester goals               TRUE
We don't have an effective way of depicting individual progress; team milestones might slip between
iterations                                                                                                   TRUE

Integration test with rational failed because of license; Unable to come up with proof of concept            FALSE

Individual responsibilties are not effectivly mapped to team roles; Team members might not
coordiante and communicate effectivly or have access to relevant information in a timely fashion             TRUE
Some of our use cases are not detailed enough or exist only at a high level (or not at all); team
members undocumented knowledge about these might be forgotten                                                TRUE
We have no experience with GWT generated Javascript debugging in production. It may be difficult
to debug generated and optimized Javascript                                                                  TRUE
4) We are still new to learning GWT, and we are using it for our prototypes. We may get bogged
down in coding as opposed to using it solely for displaying prototypes.                                      TRUE

We are using Windows Server 2008; Future server based tasks might be difficult to achieve                    TRUE
We are using a virtual server with no physical access to the machine; backup might be more
difficult to do                                                                                              FALSE
We are having access rights issues with our virtual server; may cause collaboration
problems, require fixing effort and lower team and individual productivity                                   TRUE
We are using the virtual server as a development and testing environment; performance
data might not be reliable                                                                                   FALSE
This is the first time our team is using AUP with other iterative methods; might make tailoring
AUP without watering it down challanging                                                                     TRUE
We are not capturing our management overhead properly; might not know how much time
we have (is left) for non-overhead tasks                                                                 TRUE

We don't have specifically defined productivity goals; might not know if our plan is being
effectivly executed and when to make improvement adjustments                                             TRUE
Our workload in the program fluctuates and its always high; might make iteration planning
more difficult                                                                                           TRUE

There are high workload projects throughout the semester in different courses; external
dependencies (assignment postings) might make forward planning difficult to accomplish                   TRUE
The syllabus of some of the courses has an influence on our plan; might not be able
to optimally use the coursework (techniques, metohds) in our project                                     TRUE
Our client is remote; might require increased communications, more formal documentation
and longer wait times for client responses                                                               FALSE
We don't currently have a strategy for role changes within the team; might be ineffective in
accomplishing work during the transition period                                                          TRUE
We are not using subversion for our microsoft office documents; might lose important
information or create redundant work                                                                     TRUE
Not every meeting is attended by all team members; inidividuals might have difficulty
understanding the meeting context making them less effective in their contributions                      TRUE
Sneader has no expeirence in web development; might require the team to spend extra
effort on teaching the technology                                                                        TRUE
Condition: Not everyone is regularly involve with the requirements. Consequence: Individual loose
context and will not have good understanding of the overall the system resulting inefficient design or
code.                                                                                                    TRUE
Privacy use cases are not specify in good detail. The team may not have a full understanding
requirements and be unable to correctly implement that part of the tool.                                 TRUE
We would not finish Architecture Refinement 2 in Iteration 2; This may cause us to slip semester
goals                                                                                                    TRUE
There is uncertainty in the privacy requirements of the tool. Because it is in current research. We
may have problem scoping the project without this information.                                           FALSE
We don't have specific exit criteria for requirement milestones; We may forget to create important
artifacts                                                                                                TRUE
The interfaces of the modules of our architecture are not defined;We would not know how to
implement some modules.                                                                                  TRUE
We decided change our planning process; Planning may get even worse than before.                         TRUE
Detail Requirement milestone is not getting enough time; May not be ready to freeze requirements
at the end of iterarion 3.                                                                               TRUE
The team does not have common understanding of quality and style that the work should be done.
This might lead to rework and team dysfuntions.                                                          FALSE
Using GWT to design an evolutionary prototype is time consuming, therefore some prototypes may
not be finished on time.                                                                                 TRUE
Several aspects of the development environment have not been configured; may delay development
efficiency and negatively impact team coordination and effectiveness.                                    TRUE
It has traditionally taken us about two iterations (6 - 8 weeks) to "get into the saddle" with regards
to our team roles; since time is limited in the summer and productivity is critical this could impact
our abilities.                                                                                           TRUE
EOSP slides are going to take more time than planned. This may impact what we finish on other
milestones                                                                                                   TRUE

We have not agreed with the client or within the team how to provide the export import services to
Rational rose; We may have to change our architecture because of this.                                       TRUE




We are transitioning to 48 hours from 12 hours; Team may lose a lot of hours in the first two weeks.         TRUE
Currently we are seeing issues with tracking data at status meetings; In Summer this issue may
worsen because of additional hours between status meetings                                                   TRUE
We are borrowing time from architecture; Planning and tracking may not accurately indicate how
much progress we are making.                                                                                 TRUE
Privacy requirments are not clear; may be unable to implement the features in the tool by the end of
summer                                                                                                       FALSE
Traceability is still unclear to the team; Might result in delivering the wrong functionality or designing
features incorrectly                                                                                         FALSE
All code is compiled to a JavaScript in one html page; The single page might become too big and
cause performance issues for users                                                                           FALSE
Team members do not have a clear understanding of the GWT Asynchronous calling mechanism;
May lead to bugs where the results are unpredictable                                                         FALSE
Backend interfaces are defined "Just in time"; May not capture necessary functionality in a
predictable, verifiable way                                                                                  FALSE
There is a disconnect between the backend interfaces and the front end service calls ; Rework might
be required on either side to correct oversights and errors                                                  TRUE
The history stack gets blown away on refresh; may not be able to get the application to work like a
"normal" website                                                                                             TRUE
GWT-RPC service calls are not automatically tested; may not expose errors in communication
between the backend and front end                                                                            FALSE
We refactor our code regularly; Might take away time from building other features (in the form of
rework).                                                                                                     FALSE
We don't yet have access to a CyLab administrator (deployment machine); May not develop the
appropriate installation/deployment scripts                                                                  TRUE
We don't yet have access to a CyLab administrator (deployment machine); May not have enough
time to test the application on the deployment server                                                        TRUE
We have not yet told the new Cylab adminstrator what we need; Deployment machine may not have
the appropriate hardware/software                                                                            TRUE
Acceptance tests have not been approved by the client; May not be testing our application to the
client's expectations                                                                                        FALSE

This is the first time the team has used XP; May not execute all chosen XP elements correctly                FALSE
Not all members of the team follow the coding standard; The final product might be a difficult to
maintain mess                                                                                                FALSE
We are experimenting with Pair Programming; May not track the the experiment data well enough
to measure the effectiveness                                                                                 FALSE
Bug fixing has not been taken into account when planning iterations; Unplanned bug fixing tasks may
cause a delay in new feature development                                                                     FALSE
We haven't performed phase velocity analysis; We may develop an "ideal" and unrealistic plan - and
lose visibility on the big picture                                                                       FALSE
The team is not doing a good job of tracking progress within an iteration; May have surprises at the
end of iterations where features are not completed                                                       FALSE
The team might get too relax in the fall semester; this might affect delivering our studio and project
milestone.                                                                                               FALSE
It is not clear at what point we consider the project closed. This might leave the door open for more
functionality.                                                                                           FALSE
We have not validated the architecture documents with the client; She may ask for expensive
architectural changes.                                                                                   FALSE
There is no easy way to check architectural dependencies; We may not have enough time to review
the architecture in fall.                                                                                FALSE
Notes




Overcome by other risks.

We are addressing this risk being more predictable and stick to the plan


Te velocity is self correcting because we are taking more development task this should not be a
problem.




Individual progress is now shown each iteration (in the form of velocity) along with team progress.




Not closed because of coordination issues.

Detail is sufficient, prototypes supplement our understanding.

Debugging in Java seems sufficient, javaScript debugging does not appear to be required.
both long and short term productivity goals have been defined through the end of summer.

No classes in the summer.




We have a role-transition plan, and exectuted it.

We are using sharepoint. No longer applicable.
Meeting notes quality is sufficient and most team members attend all meetings. Longer common
time makes this moot.

Sneader is taking the webapp course. Dropped the class.


we're coding!




Requirements phase is over!

We're writing code, architecture has moved to maintenance vice design.




Transition over, success!
Issues seem to not be a problem through the firs two summer iterations.
Category                Impact         Probability   Timeframe

Architecture            Critical       High          Medium

Requirements            Critical       Medium        Short

Requirements            Critical       Medium        Medium

Implementation          Catastrophic   High          Short

Requirements            Critical       Medium        Short

Planning and Tracking   Catastrophic   High          Short

Requirements            Critical       High          Medium

Requirements            Critical       Medium        Short

Operations              Critical       High          Medium

Architecture            Critical       Medium        Short

Planning and Tracking   Marginal       Medium        Short

Planning and Tracking   Marginal       Medium        Short

Implementation          Critical       High          Medium


Operations              Marginal       High          Short

Requirements            Critical       Medium        Short

Implementation          Marginal       High          Medium

Requirements            Critical       High          Short

Other                   Catastrophic   High          Short

Other                   critical       medium        short

Other                   Catastrophic   High          Short

Other                   marginal       medium        long

Operations              marginal       medium        medium
Planning and Tracking   critical       medium   short


Planning and Tracking   Catastrophic   High     Short

Planning and Tracking   Catastrophic   High     Short


Planning and Tracking   marginal       high     medium

Planning and Tracking   Negligible     High     Short

Operations              marginal       high     short

Operations              marginal       high     short

Other                   marginal       high     short

Other                   Catastrophic   High     Short

Other                   marginal       medium   long


Requirements            Critical       High     Short

Requirements            Catastrophic   High     Short

Planning and Tracking   Critical       Medium   Short

Requirements            Critical       High     Short

Requirements            Catastrophic   High     Short

Architecture            Catastrophic   High     Short
Planning and Tracking   Catastrophic   High     Short

Requirements            Catastrophic   High     Short

Other                   Critical       High     Short

Requirements            Critical       High     Short

Implementation          Critical       High     Short


Operations              Critical       High     Medium
Planning and Tracking   Critical       High     Short


Architecture            Catastrophic   High     Medium




Planning and Tracking   Critical       High     Short

Planning and Tracking   Catastrophic   High     Short

Planning and Tracking   Marginal       High     Short

Requirements            Catastrophic   High     Short

Requirements            Critical       Medium   Short

Implementation          Critical       Medium   Short

Implementation          Marginal       Medium   Short

Detailed Design         Catastrophic   High     Short

Implementation          Marginal       Medium   Short

Implementation          Catastrophic   High     Short

Implementation          Catastrophic   High     Short

Implementation          Catastrophic   High     Short

Implementation          Catastrophic   High     Short

Implementation          Catastrophic   High     Short

Implementation          Catastrophic   High     Short

Implementation          Catastrophic   High     Short

Operations              Catastrophic   High     Short

Implementation          Catastrophic   High     Short

Operations              Catastrophic   High     Short

Planning and Tracking   Catastrophic   High     Short
Planning and Tracking   Catastrophic   High     Short

Planning and Tracking   Catastrophic   High     Short

Other                   Catastrophic   High     Short

Requirements            Critical       Medium   Short

Requirements            Critical       Medium   Short

Requirements            Marginal       High     Short
Mitigation Plan

Increase the number of experiments done on the architecture.
Make the prioritization with the client ahead of time so that we can have time to develop the
prototypes before the iteration starts.

Set a deadline with Nancy for clarification on privacy requirement.
Force the internal release on Thursdays, and set the client expectation that we will develop until
thursday.

Detail the context diagram and show what technique is inside and outslide.

Take more develoment task.
Review the static(interface) when you want to make a GWT prototype. Make sure you are not
violating it.




Change planning and tracking process so that it prioritizes important milestone tasks

Create charts listed out in the planning and tracking proposal.
Our semester plan and iteration plan define our productivity goals. Luhmi chart would show if the
productivity goals for the iteration is being met. Earned value chart would show if productivity goals
for the milestone is being met.




Show planned vs. actually done tasks every week, in the burn-down chart




Conduct a quality meeting

Time-box GWT experiments.
Transition plan(roles and responsibilities)
Design process
Implementation process
Construction plan

Print out the burn down chart at the daily standup meetings.

This is a problem already
Discovery Date

        3/29/2009

        6/15/2009

        1/20/2009

        6/15/2009

        1/20/2009

        6/15/2009

        4/29/2009

        1/20/2009

        1/20/2009

        1/20/2009

         2/1/2009

         2/1/2009

         2/1/2009


         2/1/2009

         2/1/2009

         2/3/2009

         2/3/2009

        2/10/2009

        2/10/2009

        2/10/2009

        2/10/2009

        2/10/2009
2/10/2009


2/10/2009

2/10/2009


2/10/2009

2/10/2009

2/10/2009

2/10/2009

2/10/2009

2/10/2009

2/10/2009


2/13/2009

2/16/2009

2/23/2009

2/27/2009

 3/5/2009

 3/5/2009
 3/5/2009

 3/5/2009

 3/6/2009

3/29/2009

 4/5/2009


 4/5/2009
4/25/2009


4/30/2009




 5/3/2009

 5/3/2009

 5/3/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009

6/15/2009
6/15/2009

6/15/2009

7/25/2009

7/25/2009

 8/2/2009

 8/2/2009
Mitigation Tasks




Refine the context diagram to show functionality within the tool and outside the tool;#460




Discussion on whether to use a three-tier or four-tier approach;#89




Research Proof Concept GWT;#36

Create charts to show task progress on sharepoint;#127;#Resource allocation;#53

Create charts to show task progress on sharepoint;#127




Survey Current State of Requirements;#90
Modify burndown chart;#417;#Status meeting preparation;#318;#Three Status Meetings;#296




2 client meetings;#381;#2 client meetings;#382;#2 client meetings;#384;#2 client meetings;#385;#2 client meetings;#386
Contingency Plan
Identify and complete architecture and technology experiment sessions immediately after the
contingency trigger has been tripped.
If we can not meet with the client, we can have conference call, or common un with a strategy to
start finish all the prototypes.
If Nancy does not clarify requirements by the set deadline, propose and document alternative
requirements.




Review context diagram with the team on the first two weeks of Summer.

Start budgeting time for extra development to push development work.

Refactor architecture so it conforms to the planned architecture.




Review semester plan and replan milestones.

Review charts to see if they are answering the quesitons.
If the team does not agree on the productivity goals set by the plan, or if it is vague, the planning
manager should call a meeting and review the semester plan with the team.




Decide which tasks must be finished. Decide if we need to do overtime.




Require everyone to attend a few client meetings. Conduct requirement workshops.




Change scope at the end of iteration 3.




Provide Guideline and agree on different levels of quality.(Slides, Coding Standards and Prototypes)
and Charts

Postpone lower priority GWT tasks.
Trigger for Contingency

If big architectural changes are proposed in Summer.

If we cannot meet with the client or she cannot prioritized.

Privacy requirements are not clarified by end of Spring




Team does not agree on what's inside and outside the tool in Summer.

Velocity do not increasing withing 2 iterations.
When our GWT code is added to our application, the resulting architecture is different from our
planned architecture.




Iteration reflection shows that milestones that we planned to finish are missed.

We miss milestones.
Team does not agree on the productivity goals in the iteration reflection.




Drop in the hours put into studio.




If at prototyping stage, people come up with radically different ideas, that indicates a requirement
misunderstanding.




We fail to meet some of the iteration 3 milestones.




quality of code in question in code reviews.

GWT tasks consistently going over estimates. This would show in iteration reflection.
First Indicator                                                                    Problem

If big architectural changes are proposed in Summer.                                 FALSE

If we are getting close to the iteration start without prototypes                    FALSE

Privacy requirements are not clarified by end of Spring                              FALSE

                                                                                     FALSE




                                                                                     FALSE

                                                                                     FALSE




Iteration reflection shows that milestones that we planned to finish are missed.

Earned value chart show a missed milestone at iteration reflection                   FALSE




                                                                                     FALSE

                                                                                     FALSE




                                                                                     FALSE




                                                                                     FALSE
Team establishes that productivity goals are unclear.   FALSE

                                                        FALSE


                                                        TRUE

                                                        FALSE




                                                        FALSE




Prototypes vary a lot from person to person.            FALSE




                                                        FALSE

                                                        FALSE




                                                        FALSE

                                                        FALSE


                                                        FALSE
TRUE


FALSE




FALSE

FALSE

TRUE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE

FALSE
FALSE

FALSE

FALSE

FALSE

FALSE

FALSE
Item Type   Path

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks


Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks

Item        Lists/Risks
Item   Lists/Risks


Item   Lists/Risks

Item   Lists/Risks


Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks


Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks
Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks


Item   Lists/Risks
Item   Lists/Risks


Item   Lists/Risks




Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks
Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

Item   Lists/Risks

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:4
posted:3/3/2011
language:English
pages:44