Software Risk Management Software Engineering n Risk Management

Software Risk Management

Software Engineering n Risk Management n Risk concerns future happening n Risk involves change n Risk involves choice and uncertainty that choice itself entails n We cannot eliminate the risk but we can minimize it n It is essential that the risk taken be the right risk

Software Engineering n Reactive vs. proactive Reactive Never worry about the problems un till they happen Proactive It begins long before the technical work is started

Software Engineering n Software Risks n Uncertainty n Loss n Technical Risk n Business Risk n Known risk n Not known risks

Software Engineering n Generic Risk n Product specific risks

Software Engineering n Product size risks 1. Estimated size of the product in LOC 2. Estimated size of the product in number of 3. 4. 5. 6. programs, files etc. Division of work among developers Size of the database created or used by the product Number of users of the product No of changes before and after delivery

Software Engineering n Business impact risks 1. Effect of this product on company revenue Reasonableness of the delivery date Number of users who will use this product Govt. Constraint on the product Costs associated with late delivery 2. 3. 4. 5.

Software Engineering n Customer related risks All customers are not equal Some customers will accept the bad product, some will mention the defects in the product and other will always point out the errors although the product is ok

Software Engineering Have you work with customer in the past Does the customer have the solid idea of the product 3. Will the customer will spend time in formal technical reviews 4. Is the customer is willing to let your people do their job or will the customer resist looking over your shoulder 1. 2.

Software Engineering n Process risks n Does your senior management support the importance of standard process for software development n Are staff members willing to use the software process n Is the software process used for other projects n Has your organization developed a series of software engineering training courses for the managers

Software Engineering n Documentation n Are formal technical reviews after each phase in the organization n Are we working according to software engineering standards

Software Engineering n Technical Risks n There is communication between customer and n n developer Do you use specific methods for testing Are software tools used for analysis and design process. Are quality metrics collected for software. Are tools used to create prototypes

Software Engineering n Technology Risks n Is the technology to be built new to the organization n Do the customer demands the creation of new alogs n Does the software interfaces with new and unproven hardware n Does the software interacts with that database whose performance has not been tested

Software Engineering n Development Environment risks 1. Is the software project management tool available (Ms project) Tools for design Testing tools Is the documentation and help available Have members of the project received the training on each tool Code generators (UML) 2. 3. 4. 5. 6.

Software Engineering n 1. 2. 3. 4. Risks associated with staff Best staff is available Do the people have the right combination skills Are enough people Have staff received training

Software Engineering n Performance Risks The product will meet its requirements n Cost risks Project budget will be maintained n Support Risk The software will be easy to change n Schedule The project schedule will be maintained