Skip to content

Risk Management

DDraiman1990 edited this page Mar 27, 2016 · 3 revisions
Risk Severity (1-3) Probability (1-3) Measures to lower risk Response if risk will be realized
1 Customer changes some demands 1 3 Build a modular system with separated systems to accommodate later additions and changes We will sit down with client and try to understand what he wants as clear as possible while explaining the limitations (if they will arise)
2 Technical Limitations using MongoDB for our clients demands 3 1 Try to get as much information from the client as possible to determine if MongoDB will satisfy the needs of his demands, and read about MongoDB beforehand to understand its capabilities We have a qualified partner who knows SQL and we will also read about SQL capabilities and we will replace MongoDB with SQL if the need arise
3 The client will realize the use of a browser to access Web App will be cumbersome 2 3 We will read beforehand about mobile packagers to package our web application as an Android/IOS application for ease of use We will implement the chosen mobile packager and use it to create an easy to launch smartphone/tablet app
4 The Course time scope will not suffice for all the wanted features 3 2 We will sit with client and make sure the higher priority features will be implemented first and the lesser features will only be implemented if time is left We will sit with the prepared list of features with priority and simply cut certain less important features from our work plan
5 Prototype will consume more time than actual work on the project 2 1 We will set team meetings ahead of work to decide on specific features to be developed for each revision of the prototype to make sure no one tries anything new or time consuming we will simply stop making prototypes for the time being and start focusing more on actual features with place for changes later
Clone this wiki locally