Programme Management may have many responsibilities, but the most important of all is the ability to identify and positively execute plans to manage the risks threatening the objectives.Through a process of structured interviews and plans the Assessment Analysis is used to highlight the specific Events which may turn into Risks. During the interviews Assessment Analysis is used to capture the key Events from the interviewees.In turn, the Assessment Analysis provides a life-cycle process, which highlights the primary prioritisation of the risks. In large, complex, and critical programmes, it is essential that a true prioritised report is available so that the imminent threats can be managed first. The process commences by identifying the most important events which may become threats to a project. These are given priority, support and management expertise. Once the prioritisation exercise is completed, the participating people are notified and subsequently interviewed to bring out and capture any possible concerns they may have.Within a programme, projects are prioritised to ensure that those most critical to the programme's success are given priority to scarce resources.1.2 RISK MANAGEMENT METHODOLOGYThe I.T. Risks Logical Analysis allows the capture of collective knowledge and expertise from those involved on the project, in a form that facilitates the communication of Events, Assessments and the pro-active management of risks. This method can be applied to any type of project, or programme.In essence, this is the mechanism by which the functions of programmes and projects are held together as a result of the principles operating within the I.T. risk analysis methodology.This is the systematic approach to the varied Events, their Assessments, and the consequential risks relating to or consisting of a system. Methodical in procedures and plans, these are addressed to those involved and deliberating within the parameters of their systems development responsibilities. The results being dependable on the interaction and the mutual or reciprocal action which encourages those involved in the programmes and projects to communicate with each other and to work closely with a view to solving the threatening Events before they impact on the development of the system. The individuals involved maintain a generic approach, which relates and characterises the whole group of those involved in assessing the Events and attacking the threatening ones before they become Risks to the development of the system. The end result being the avoidance of apparent problems within the pre-defined users' systems requirements. This is enabled by following the I.T. Risk Management methodology. The system architects and the risk management practitioners simply follow the approved body of systems development methods, rules and management procedures employed by their organisation. For practical or even ethical reasons, it must be noted that with such a philosophy, it is seldom possible to fulfil all requirements of very large organisational systems. As such, the I.T. Risk Management methodology is administered in applications; putting to use such techniques and in applying the Risk Management principles in the development of various applications will involve numerous and varied activities. A concrete issue in developing new applications is the problem of communication among the people involved, the motivation constantly needed for generic work, the ability to interact systematically and in using a structured systems methodology.