le, who is aware of the current working practices and can judge the practicalities of any proposals. - A member who is technically knowledgeable in the particular skills being utilized in the development. - A representative of a key supplier - e.g. where priority databases are being used, as required. Risk Drivers These are possible risks within the system Client understanding of requirements Modularity of the project Duration of project Maturity of development environment Designer understanding of application domain Availability of existing products as examples Technical capability of project team Team experience of target operating system Sub-contractor/third party involvement Ease of liaison with client/user Clarity of liaison with client/user Project team turnover Complexity of product requirements Volatility of requirements Stability of interfaces Inflexible specification Project team size These risks are evaluated using techniques such as software evaluation packages, experience. Difficulty of application Ability to do testing out with the live environment Designer experience of the environment Maturity of hardware and software base Contingency Planning After identifying the possible risks to the project a contingency plan must be drawn up to counter act, to solve the problem if anyshould occur. Things such as having flexible time would be good helping the team as they would not have to be to rush aboutgetting in on time just as long as the hours are made up in the end. The other areas that can cause problems is the outsidedelivery staff which bring various stock for the project. These outside companies might have ran out of stock or cannot deliver onrequired days. The team members will have to be set up working on another part of the project till the parts are delivered. Activities, which are at risk, are identified and a cost/benefit analysis is applied to the following options Reduce high technology dependence Increase the skil...
