Agile Evolution

Client service, excellence in delivery and innovative solutions. They are part of how we work. Here are some other reasons that we think make working with Riskpoint different.

Solving complexity by evolution

IT history is sadly littered with examples of over-ambitious, expensive systems designed on paper that were either never delivered or parts of which were never used.

We believe that the best way to deliver very complex systems and websites is to start with the 'mission-critical' parts and evolve the functionality that end users demand. The theoretical danger of this more efficient approach is that the original design cannot cope with upgrades, or that the development cycles are overly long. We designed our framework specifically to eliminate these risks.

Follow the progress

We like our clients to see their project in progress - Alpha, Beta versions, warts and all. By seeing the real thing early on, we find clients are more satisfied with the end product.

Continuous development

Tweaking and changing your system is expected and a sign of healthy usage. No business stands still for long and its IT system or website needs to reflect this. We give maintenance and upgrade work same priority as new projects - we see both as one continuous line of development.

It's good to talk

You will never have to talk to someone who does not code. Our developers will never code in isolation without speaking to the actual users. We are more than happy to come and see you in person - emails are great, but there is nothing like a finger on the screen and face to face time to ensure you really get what you want and need.

Light specifications

It takes great time and effort by both client and developer to produce detailed and clear system specifications on paper. In fact, specifications require the same skill-set and development time to produce as the actual code - and they will almost always change by the launch.

We believe it is vastly more efficient to start prototyping and building the application straight away, using only very light documentation, capturing the main functional and navigational items.