Software Project Risk Management Flashcards Preview

SENG 511 > Software Project Risk Management > Flashcards

Flashcards in Software Project Risk Management Deck (10)
Loading flashcards...
1
Q

Murphy’s Law

A
  • If anything can go wrong it will.
  • If there is a possibility of several things going wrong, the one that will cause the most damage will be the one to go wrong.
  • If everything seems to be going well, you have obviously overlooked something.
  • If you perceive that there are four possible ways in which something can go wrong, and circumvent these, then a fifth way, unprepared for, will promptly develop.
2
Q

What is a risk?

A

All events or conditions that may occur in a (software) project and potentially ahve negative consequences on the project outcome.

3
Q

What is risk impact?

A

Potential loss associated with a risk.

4
Q

What is probability?

A

Probability that the event will occur.

5
Q

What is risk control?

A

Set of actions taken to reduce or eliminate the risk.

6
Q

What is a risk plan?

A

A list of all risks that threaten the project, along with a plan to mitigate some or all of those risks.

7
Q

What is a risk planning session?

A

The project manager selects team mambers to participate in a risk planning session:

  • The team members brainstorm potential risks
  • The probability and impact of each risk estimated
  • Prioritization of the risks
  • A risk plan is constructed
8
Q

Sample risks

A
  • Staff turnover
  • Management change
  • hardware unavailability
  • Reqruiement change
  • Specificaiton delays
  • Size underestimate
  • CASE tool underperformance
  • Technology change
  • Project competition
9
Q

Types of Risks

A
  • Technology
  • People
  • Organizational
  • Tools
  • Requirements
  • Estimation
10
Q

Top 10 Risk Items and Recommended Actions

A
  1. Personnel shortfalls: staffing with top talent; job matching; team building; morale buildig; cross-training; pre-scheduling key people
  2. Unrealistic schedule and budgets: Detailed multiscource cost and schedule estimation; design to cost; incremental development; software reuse; requirements scrubbing
  3. Developing the wrong software functions: Organizational analysis; mission analysis; operational concept formulation; user surveys; prototyping; early user’s manuals.
  4. Developing the wrong user intergace: Prototyping; scenarios; task analysis.
  5. Gold Plating: Requirements scrubbing; prototying; cost-benefit analysis; design to cost.
  6. Continuing stream of requirements change: High change threshold; information hiding; incremental development (defer changes to later increments)
  7. Shortfalls in externally performed tasks: Reference checking; pre-award audits; award-fee contracts; competitive design or prototyping; team building
  8. Shortfalls in externally furnished components: Benchmarking; inspections; reference checking; compatibility analysis
  9. Real-time performance shortfalls: Simulation; benchmarking; modelling; prototyping; instrumentation; tuning.
  10. Straining computer science abilities: Technical analysis; cost-benefit analysis; prototyping; reference checking.