Solution

1. Risk Management Techniques (Any Two)

Risk management is the process of identifying, analyzing, and controlling risks that may affect a software project.

1. Risk Avoidance

Risk avoidance means eliminating the source of a risk so that it does not affect the project.

Example: If the requirements are unclear or technically uncertain, a prototype can be developed first. This helps validate the requirements and feasibility before full-scale development.

2. Risk Transfer

Risk transfer means shifting the responsibility or impact of a risk to a third party.

Example: A company may outsource a technically complex module to an experienced vendor or purchase insurance to transfer the financial impact of a risk.

Other risk-management techniques:

• Risk Reduction/Mitigation: Reduce the probability or impact of a risk, e.g., use incremental development and regular testing.
• Risk Retention/Acceptance: Accept a low-impact risk when the cost of avoiding it is greater than its possible loss.

---

2. Capability Maturity Model (CMM)

The Capability Maturity Model (CMM) defines five levels of software-process maturity. Each higher level represents a more disciplined, measurable, and continuously improving development process.

Neat Diagram

        Level 5 — Optimizing
        Continuous Process Improvement
                    ↑
        Level 4 — Managed
        Quantitatively Managed Process
                    ↑
        Level 3 — Defined
        Organization-wide Standard Process
                    ↑
        Level 2 — Repeatable
        Basic Project Management Processes
                    ↑
        Level 1 — Initial
        Ad-hoc / Chaotic Process

Level 1 — Initial

• The software-development process is ad-hoc and chaotic.
• There are few defined processes or controls.
• Project success depends heavily on individual effort and experience.

Level 2 — Repeatable

• Basic project-management practices are established.
• Requirements, cost, schedule, and project progress are tracked.
• Successful practices from previous projects can be repeated.

Level 3 — Defined

• Software processes are documented, standardized, and integrated across the organization.
• A common standard process is followed by different projects.
• Activities such as training, peer reviews, and process definition are established.

Level 4 — Managed

• Processes and product quality are measured quantitatively using metrics.
• Statistical and quantitative techniques are used to monitor and control processes.
• Management can predict process performance and quality more reliably.

Level 5 — Optimizing

• The organization focuses on continuous process improvement.
• Defects are prevented and processes are improved using measurement and feedback.
• New technologies and improved development practices are adopted when beneficial.
• Key improvement areas include defect prevention, technology change management, and process change management.

Conclusion

Thus, CMM progresses from an uncontrolled/ad-hoc process at Level 1 to a continuously improving process at Level 5.