Software development is a risky
business and the key to its success is in the way those risks are
dealt with.
The problem is essentially due to
limitations in the use of language.
By its very usage, language attempts,
amongst other things, to communicate ideas, but in abstract terms.
The challenge for any project is in the effectiveness of that
communication in defining the requirements of the development
involved. It is only until those requirements are correctly defined
and also correctly understood that any bespoke development has the
opportunity for real success.
At MSM we have a robust methodology
that attempts to reduce the differences that might arise, through
thorough documentation and prototyping, to ensure the client is
fully aware of what is going to be delivered before it is too
late.
The SMP route enhances that methodology
by minimising the resources involved in those processes, and
therefore, differences of interpretation that may occur from one
resource to the next. This, in turn, offers greater effectiveness
and reduces the overall effort involved.
From the very outset the client is
presented with a Technical Consultant who will listen to their
requirements and advise on the approaches that can be taken,
utilising all of the previous experiences and expertise gained from
a vast list and depth of past projects.
It is often in these experiences that
new ideas can be offered to the prospective system with valuable
gains and new efficiencies not previously considered.
The very same individual then:-
documents, designs, prototypes, develops, and manages the project
throughout its life cycle.
The familiarity that continues from one
step to the next, keeps a rapid pace going, and because the size of
these projects are relatively small, it is fairly straight forward
to keep a track of things.
The success we have had to date with
our SMP projects, have been a testament to this model, with all
projects being delivered before the agreed deadline and under the
client's budget.
It's a classic cartoon but speaks
volumes about the essential problems between the various
phases of the project life cycle:
