The Process
Once a problem has been identified by a Client, there may be a need for Custom Software
to provide the desired outcome.
Success is stumbling from failure to failure with no loss of enthusiasm
Failure is the opportunity to begin again, only more intelligently
There are many famous people with famous quotes on failure that can be applied to
all walks of life and various scenarios. When it comes to software projects, there
are few more villified processes. The world is littered with failed projects, many
of which wasted millions.
By failing to prepare, you are preparing to fail
The singlemost important part of the software design process is the preparation.
Countless software projects have failed because of the lack of knowledge of what
the outcome should be: in other words
what does the User want/ need?
Our design process centres around the User Requirements Specification or URS. This
document contains all of the requirements of the finished product. It identifies
the functions of the software in non-technical terms. Projects cannot succeed without
a well-written, accurate and agreed URS. No amount of Scrum/ Agile Development or
any other design process can compensate for the lack of this important document.
As with real life, things change. Changes must be accommodated within the Design
Process but kept to a minimum. Requirements that change frequently point to poor
preparation and planning. We operate a Change Control process to ensure that changes
are properly thought out, executed and tested in the most efficient manner possible.
The bottom line though is that changes, no matter how well planned, cost time and
money and should be avoided wherever possible.