The first part of the IRC process is the creation of the IRC item. There are five types of IRC item, these include:
We have defined an Issue as a negative (or sometimes positive) influence which will cause a relatively minor impact on the Project’s plan and/or quality. An Issue by definition would not have already been anticipated (as a Risk). Issues are identified during a project’s execution by Team members or the Project Manager throughout the project’s execution. Issues are addressed by either a Change Request or Resolution plan (with associated tasks). See the section on Issues in this manual for more details on creating and managing Issues.
We have defined Risks as a potentially negative (or sometimes positive) influence which may cause a major impact on the Project’s plan and/or quality. A Risk will be assessed for probability of occurrence and impact. Risks are addressed by either a Change Request, Resolution Plan (eg changing circumstances to negate Risk such as transferring responsibility), Impact Plan (captures tasks and effort if Risk is accepted and then realised), Contingency Plan (captures a resolution plan if Risk is realised) or Prevention Plan (reduce probability of occurrence). Risks are identified and assessed by the Project Manager, particularly in the planning stages of a project although they may be proposed via an Issue. See the section on Risks in this manual for more details on creating and managing Risks.
We have defined Change Requests as a significant change to the Business Requirements. Change Requests in bSmart are not meant to be used to manage detailed Technical Changes (Configuration Management) or Contract Change Management. Change Requests will likely result in Technical Changes and Contract Changes however. Change Requests are considered significant, that is they are not meant for minor detailed changes. See the section on Change Requests in this manual for more details on creating and managing Change Requests.
The application includes functionality specifically aimed at the client such as the Client web site and Clients Requests. They represent issues or requests which are raised by the client (entered by the Project Manager on behalf of the Client). Project Managers are responsible for assessment and processing of client requests. See the section on Clients Requests in this manual for more details on creating and managing Clients Requests.
The application includes a category of requests which do not necessarily reference a Project and/or Tasks. These are ideal for capturing broader organisational initiatives in the early stages. Service requests are addressed through Resolution plans (tasks) or Change Request (projects).