Katipo Project Survival Kit

Software Development

Over the years we've continued to learn and adapt our processes so that you get the best web application possible for a reasonable price and to ensure that you are fully engaged with all aspects of your website development.

This gives you confidence in your budget by removing cost over-runs.

We've learnt that people find it hard to focus on the content of pages, so we try and remove distractions (like graphic design) when we're working on the flow and structure of the application, only adding in the graphic elements when we think we know how a section is going to work.

All our websites & applications go through a similar development process and we've based our timeline on following this process.

Web Application Development

For web applications, we run a sub-project that follows a similar process to our website development process, but applies the graphic design a little later.

1. Define the scope

  • Ask the big and small questions to confirm what you want to do.

2. Mock-ups of key pages/functionality

  • Once the parameters of the project are set, we go to work on the specifics. We will do some simple diagrams of key pages, like the admin page, and the pages that the public uses. Once we know exactly how we want to display the data, we will understand both how the database needs to be built, and what will need to be done to your data to achieve it.

  • The specific documents we will require sign-off on are

    • Deliverables and Output Requirements: a list of outputs from the system and examples.

    • Process diagram: how the system works.

3. Prototyping key aspects of the system

  • We will test some of the key ideas – particularly navigation and some of the data input screens, to make sure that they work in practice. You will be asked for feedback on usability and functionality.

4. Building the working site

  • Key development takes place so that a functional system is produced. It will be plain to look at, as we'll want you to focus on how it works, rather than what it looks like.

5. Testing, feedback & refinement

  • The application will need a workout, and some usability testing, to see if it "works" and people understand what it's all about. We would expect to have a period of rapid feedback and change, to iron out any problems people find.

6. Design and applying a theme

  • Once the functionality is in place, we'll wrap some design around it, applying the templates that have already been developed, and making any specific elements needed.

7. Testing and acceptance

  • You get the completed system to test, and to tick off the deliverables and outputs.

8. Go Live