What makes a web application successful?

Planning the project

We approach all of our projects using a carefully planned mix of project management techniques. While progress success is of course the result of a great Project Management process, even greater success is achieved by choosing the right Project Management process for the project. At Rawnet, we practice two methods - Traditional and Agile.

The approach we use for your project depends on several factors, including clarification of scope, timescales, and of course what we believe will guarantee the most economical results for the client.

"Overall, the project was smooth from start to finish, it was on time, on budget and we are completely blown away by the final results" - Isaac Occhipinti, HHIC

Through years of experience we have refined our methods to ensure quality, speed and ultimately the complete satisfaction of both our customers and their customers.

Traditional Project Management

Before any code is written or designs produced, each element, feature and expectation of the project is carefully planned. To achieve this several documents are produced. The first is an Information Architecture (IA) plan – a model conceptualising the features and key areas of the site in the form of site maps and wireframes. The second is the Project Specification, this document details in writing, with the help of diagrams and illustrations, how each feature will work. An example Functional Specification document for a relevant project can be supplied as a reference if required.

We work closely with you when developing these documents, ensuring that we completely understand your requirements and that our solutions exceed your expectations. Once completed both parties will know the project inside and out, the goal posts are set and how we plan on reaching them is planned to the letter. We then move on to development.

This method is the preferred choice for when there is a clear and defined agenda from the project's inception. This allows for Rawnet to embark on a fixed scope and therefore fixed price.  

Agile Development

An alternative, more fluid approach is the Feature Driven Development (FDD) Web Development model.

Briefly, FDD consists of 5 clearly defined processes. The core of FDD is the concept of a feature which is a clearly defined Client-valued piece of functionality. The processes that make up FDD are structured around defining every element of a project as a feature, then designing and building each feature in an iterative manner.