the development process at wirebox is broken up into different stages

brief

First stage is a list of requirements of the changes or functionality. Wirebox can help facility a brief and extramplote the correct information we need to move to the next stage.

wireframes

Wireframes are an important part of development. They help visualise the brief and concepts from a client perspective.

• Structured design — You know where everything goes before narrowing down the exact technical details.
• Creates foundations early on — Areas like navigation and layout determine how the rest of the project proceeds. If there’s a problem, it’s better to tackle it at the start, rather than later with hi-fi prototypes, where you may have to redo some work.
• Design centers on content — Wireframing is a content-first method that encourages you to think about what’s really important on a page before laying it out.
• More creativity and room for experimentation — Thanks to their simplicity, wireframes are easy to create, meaning you can experiment and develop new ideas without taking too much time or effort if they fail.

prototyping

Prototyping the wireframes of the site helps to process the flow and functions which are required.

Ironing these out as early as possible will help to element any changes or errors which do not get into the development process.

The wireframes are interactive as well, to help showcase to the client the interactions that would be on the final product.

design

Working with the preferred design route, we will apply the design to specific user journeys, exploring creative options to deliver against the practical needs of the client

• We look to rationalise and further develop the route that most interests the client.
• Progress prototype with further pages to prove the designs robustness where you may have to redo some work.
• We can add new copy to pages if required.
• Client can user test these ideas with user base.

functional specification

The functional specification document outlines all functions against the wireframes or Design.

The document identifies stakeholders, the document history and previous approvals. Aside from that, the document will also reveal:

Project scope – what are the project goals, deliverables, features, tasks, deadlines and cost?

Risks/Assumptions – what might affect the functional design of the product/system?

Solution overview – what are you proposing to create to solve a problem (sitemaps, screen flows etc.)

Use cases – put functional requirements into the context of a user action.

Requirement specifications – what should the product do?

System configurations – the steps required to configure a product.

Non-functional requirements – these are the nice to haves.

Error reporting/Exception handling – explain any error conditions that happen in the interface.

development

Product Development: In this phase, we start to develop the product.

We use an Agile methodology where tasks are split into phases. The team performs tests such as unit, integration and performance tests on this phase.

Once this phase is completed, the team will release for testing for internal and limited external users.

The development team is overseen by a dedicated project manager who will provide reports based on progress – offering clear communication throughout the project.

testing

Bugs come with all development projects, no matter how good the team working on the project is. Which is why we employ the best QA testers to thoroughly test any development work that has been completed across a range of browsers and devices.

All bugs found are reported to the project manager for clarity, the developers are then assigned to the relevant bugs to fix.

Once fixed, another round of testing occurs. This is repeated until we’re happy internally, then we’ll pass the testing over to you for review and then final sign off.