At the start of every project, we take time to gather information in a phase we call ‘discovery’. Once we’ve had a few discovery discussions, we are able to fully finalize your Minimal Viable Product (MVP) and we can formally begin the planning. During this set of stages, we draw up user stories, technical documentation, system architecture capturing the MVP requirements.
Planning is often assumed to be a stage that can be rushed, however, in our experience this stage is by far the most critical, rushing it can and most likely would create significant issues ranging from scalability challenges to accessibility, which can impact the success of the product and in some cases warrant a complete redesign/redevelopment.
Once we’ve scaled through the planning, user story and technical documentation designs, we’re ready to start putting sketches and UI/UX flows together. In the wire-framing and prototyping set of stages, we create the entire journey of the users based on userstory created in manner that takes several key factors into consideration. These factors are based on the type of product, e.g. Social, FinTech, Market Place etc. Some factors include how quickly we want to take a user to a payment page or how engaged we want the user to be as they navigate through the product.
During the Wire-framing process, we piece the flow together in a manner that is easy, friendly and accessible for the proposed product end users, while considering the business model of the product itself. The end point of this phase is a prototype, the non functional walk through, that allows us to get a sense of what the finished product should look like. This is a crucial part of any development.
This is where the rubber hits the road. Once the prototype has been approved, we move into a full development phase. We can liken this to firm marching orders broken down into sprints, usually 2 weeks long, depending on overall size of the product and project. While we develop based on firmed up requirements and established UI/UX flows, we follow an agile methodology which allows us to make quick changes where necessary in support of the vision of the project owner. We do this through various iterations, stand up meetings, retrospective meetings and sprint reviews.
An important part of all development work is Quality Assurance and Testing. While testing is done as projects are developed to stay agile and manage efficiency. We engage in additional QA upon completion of every project to ensure the integrity of the project and product. During the QA and Testing phase, several scenarios are considered using both automated and manual tools. The purpose of this phase is to ensure robustness, scalability and endurance among others.
User Acceptance Testing is the last phase before a production launch. During this phase the product visioneer will review the product in full to reconfirm that it matches expectation and all requirements have been met. Upon confirmation, deployment is scheduled with the appropriate support put in place.
We are known for following a delicate yet simplified process in the delivery of our services.
We do the micromanaging, so you don’t have to. Heres 4 things about what we do that you should know.