Part of planning for risk involves allocating each identified risk to a project milestone. Very often a milestone is attached to a payment, so a risk can also have an accurate value attached to it. By its nature, each risk will impact, if at all, at a certain time. For example, Milestone 1 is "Delivery of Software X, Issue A to the Customer".
If this risk impacts, we will not receive the Milestone 1 payment from the Customer. This payment has been planned to cover costs of staffing, materials, sub-contractor payments and a variety of other project expenses including finance charges up to this point. The cost of this risk, or any other associated with this Milestone, impacting is basically the cost of borrowing that amount of money, from the time it should have been received up until the time when it is actually received.
In order to manage this risk, regular project meetings will be held, a part of which will cover the progress of identified risks. The risk owner will report on each risk with their assessment of the likelihood its occurring. If the likelihood of any risk impacting increases, steps will be taken to implement the mitigation measures already identified.
In the case of this example, the mitigation measures might be "Introduce interim acceptance testing to identify problems early".
Let us assume that the introduction of this mitigation measure has become necessary and the interim acceptance testing has shown that the software is far from ready for delivery. This will mean that fall-back or contingency plans must be implemented.
This is a very undesirable state of affairs but such plans might be: "Introduce additional software engineering effort to identify and resolve bugs" or, assuming we don't have the personnel available to throw extra resources at the problem "Put project software engineers on overtime in order to identify and resolve bugs".
In themselves, these contingencies will, of course, have a cost but this must be weighed up against the possibility of delaying the milestone payment and worse, failing to meet the milestone timescale. Once one milestone is late, it's very hard to catch up and much rescheduling is needed in order to still meet the end delivery date. Failing to meet milestones is usually very unpopular with the Customer and not at all likely to do the company's reputation any good.
On the up side, if a risk does NOT impact and the milestone with which it is associated is met, that risk can be deleted and forgotten, leaving time and space to concentrate on the next one.
Next in this series, we'll look at managing the risks associated with suppliers or sub-contractors.
Insurance & Risk Management
Starting with the receipt of an invitation to tender from a potential customer, the steps to be taken to manage the risk associated with selecting suppliers are as follows.
The project technical lead must review all the technical documentation received from the customer. Following the project team's decision that certain items need to be sub-contracted, the technical lead will write, or have a representative write, a technical requirements specification for each item to be sub-contracted, which will form part of the sub-contractor invitation to tender.
In addition, all other members of the project team will review the areas of their own particular discipline (quality assurance, configuration management, etc.) and write their own specifications for flowing down to the sub-contractor invitation to tender.
For each item to be sub-contracted, a procurement package will be compiled. This will contain whatever documents are deemed necessary depending on the complexity of the item in question, but as a minimum the aforementioned technical specification.
To start the risk management process, all documents to be included in the procurement package will be peer reviewed. This involves at least one person of the same discipline comparing the customer requirements with those included in the sub-contractor specification to ensure that nothing has been omitted.
A list of potential suppliers for each item of supply is then drawn up. Ideally, in terms of risk mitigation, there will be a minimum of three companies thought to be capable of fulfilling the technical requirement for each item, preferably more in the first instance. This list is then reduced to a manageable number (the ideal three) by reviewing the possible sub-contractors in terms of the following.
Companies who have supplied goods in the past:
- Quality and reliability of items supplied
- Timeliness of delivery
- Adequacy of documentation
- Attitude, flexibility and co-operation of personnel
- Ease of contract negotiation
- Pricing policy
- After sales service, including warranty
Companies who have not supplied goods in the past
- Reputation in the market place
- Quality assurance certification
- Financial stability
This list is not exhaustive but contains the most important areas to be considered. The most objective way of reviewing the above, is to weight each one in order of importance, devise a scoring mechanism, create a grid to be completed by each member of the review team and calculate the numbers. This method isn't foolproof but is as close as it possibly can be.
At this stage, the project risk has already been reduced because the best few of the potential sub-contractors have been chosen to compete for the sub-contract.
Alternatively, the selection process has shown that there is only one supplier capable of fulfilling the requirements. This requires quite different handling and will be the subject of a future article.
Michael Russell has sinced written about articles on various topics from Celebrities, Dieting and Diabetes Treatment. Michael RussellYour Independent guide to . Michael Russell's top article generates over 2240000 views. to your Favourites.
Defending The Cave Man ANY good nutrition program - for health or for fat loss - is going to be focused on natural foods and it will teach you how to get the processed food OUT and the natural food IN.