Web application development can bring huge benefits to an organisation, either by delivering better services to their customers or streamlining internal processes. Linking internal systems or replacing previously manual tasks are making web based applications the way forward to all types of businesses, large and small.
There are number of ways to approach the production of a web application. Size of the application and the budget usually drive a client down one of two routes. There are benefits to both processes but we’ll always aim for the same target – to meet the requirements and business objectives (even if this is different to the initial perceived requirement).
1. Detailed and complete specification
Through a thorough briefing and scoping process we will work with you produce a detailed and complete specification before any designer’s pens touch paper or the developers start cutting code. Through an iterative process of wire-framing and prototyping we will work with you to develop the application one step at a time. We will question and test at every stage to make sure we stay true to the specification but also ensuring that the end goal or business objective is being achieved – test, review, test, review.
This is the best approach for smaller web applications where the requirement is well established and unlikely to change throughout the design and development process. A good example of this is an online calculator we designed and built for Fraedom (Spendvision). Rouge delivered a responsive, interactive, global, multicurrency application to help sell Spendvision services. The specification was developed with the client and agreed upfront, before production begins.
2. Agile / Scrum approach
It is not always possible to predict the best solution to a problem without rolling up your sleeves and working on prototypes or getting development underway. Rather than spend time on specification writing and planning (especially on larger projects) it is often more beneficial to work through options by starting development, on paper or with code. It is essential that the business requirement is understood and clearly defined before any other work begins – what problem are we trying to solve? Once this is clear and agreed, we can break the requirement down into manageable, deliverable chunks and start to attack them in order of importance – most important first. Working in “Sprints” of 3-4 weeks gives us regular review points. At the beginning of each Sprint we set out the goals for the coming weeks and review the previous Sprints' work. The intention is to deliver working code at the end of each Sprint and keep the project on track through continuous, gentle realignment. This way we spend precious client’s time and budget on collaboration and delivery rather than trying to stick religiously to a previously and more than likely out-of-date plan.
With an Agile approach we work closely with DataSift to continuously develop and improve their Web Developer’s portal.
