Explanation/Reference:
Explanation:
Organizational process asset is not a tool and technique, but an input to the quantitative risk analysis process. Quantitative Risk Analysis is a process to assess the probability of achieving particular project objectives, to quantify the effect of risks on the whole project objective, and to prioritize the risks based on the impact to overall project risk. Quantitative Risk Analysis process analyzes the affect of a risk event deriving a numerical value. It also presents a quantitative approach to build decisions in the presence of uncertainty. The inputs for Quantitative Risk Analysis are:
Organizational process assets

Project Scope Statement

Risk Management Plan

Risk Register

Project Management Plan

Incorrect Answers:
A: Data gathering and representation technique is a tool and technique for the quantitative risk analysis process.
B: Expert judgment is a tool and technique for the quantitative risk analysis process.
C: Quantitative risk analysis and modeling techniques is a tool and technique for the quantitative risk analysis process.

is incorrect. Impacts represent the outcome or result of a threat exploiting a
vulnerability. The stem does not describe an impact.

Involve the development team in planning is the best recommendation to help reduce IT risk associated with scheduling overruns when starting a new application development project. This is because involving the development team in planning can help ensure that the project scope, requirements, resources, and timeline are realistic, feasible, and agreed upon by all stakeholders. It can also help improve the communication, collaboration, and commitment of the development team, as well as identify and mitigate potential risks and issues early in the project life cycle. According to the CRISC Review Manual 2022, one of the key risk identification techniques for IT projects is to involve the project team and other relevant parties in the risk assessment process1. According to the CRISC Review Questions, Answers & Explanations Manual 2022, involving the development team in planning is the correct answer to this question2.
Implementing a tool to track the development team's deliverables, reviewing the software development life cycle, and assigning more developers to the project team are not the best recommendations to help reduce IT risk associated with scheduling overruns. These are possible actions that can be taken during or after the planning phase, but they do not address the root cause of the risk, which is the lack of involvement of the development team in planning. Implementing a tool to track the development team's deliverables can help monitor the project progress and performance, but it does not guarantee that the deliverables are aligned with the project objectives and expectations. Reviewing the software development life cycle can help ensure that the project follows a structured and standardized process, but it does not account for the specific needs and challenges of the project. Assigning more developers to the project team can help increase the project capacity and productivity, but it can also introduce new risks such as coordination, communication, and quality issues.