![]() |
|||||||||
All our quotes to you will be based on the level of analysis we have performed. When we look at a system, certain elements are flagged up as being more technically difficult or business critical. We then try to address these risk elements first. This gives you confidence in the project progress. If we have only been able to perform a brief analysis of the requirements then there is always likelihood that some risks will be missed. If this happens we will let you know as soon as possible so you can decide how you want us to proceed. Because of this we may ask to do a scoping study before the project properly starts. This cuts down your risk of starting a project that may be better tackled in a different more cost effective way such as by just reorganising the working method slightly.
Another part of our risk aversion strategy is incremental development. Any
medium to large development will be broken up into a number of increments.
Each of these increments has a definite end point, which needs to be signed
off. Changes can still be made to the items produced in these increments but
they will go through change control first to ensure the impact is known.
[ Design visually ] [ Relevant documents ] [ Risk aversion ] [ Change control ] [ Verify quality ]