Our software development process takes 5 easy steps to complete:

• Discoverability Workshop
  • At the very beginning, we meet up with you and talk through your business processes and ideal business operations to capture everything in notes and workflows, which then support the next stages of development: wireframing, and blueprinting.
• Wire-framing the tool, & Design
  • In order to build a software platform or tool, the exact screens that the user well interact with need to be designed. To jump straight into design without a wireframe is costly, wireframes are like a quick and easy interactive design on roughly how things will look and work.
  • Once the wire frames are ready and approved, the job is much easier for the designer to create a style guide along with finished refined UI ready to go for developers.
• Analysis
  • Analysis happens alongside wire-framing, and designing, capturing requirements and cases into a business case, and an acceptance criteria on a task by task basis.
  • An analyst also writes up the SST, which is a single source of truth document. This document includes everything from underlying systems that affect the whole tool like statuses, user login, credentials, API documentation for the frontend and more.
  • Blueprinting & Estimation
    • After analysis, wireframes and designs are approved, it now makes sense for the developers to create a DB schema and API document to serve as the blueprints for technically building the infrastructure. This clears up any confusion about implementing features and anticipates problems that come up with prepared solutions.
• Active development phase with agreed SOWs
  • A SOW will be generated following developer estimations with a Gantt (timeline of resources based on tasks) as well as a task breakdown and expected costs.
  • Once approved, the dev team is in active development, with demos every Friday along with regular meetings to keep things moving until completion.‍
  • Deployment‍
    • Deployments occur throughout development to a staging environment that you have access to verify the work as it's being developed. It is also used to demo features completed like new pages or new components.
    • At the end of development there is a live deployment to your domain ready for active users.

Ongoing Maintenance

• After the initial development, you are free to market the app with confidence bringing in new users.
• During this time, you may not have a lot of ongoing development but incase issues come up or new features are requested it makes sense to have a dev team on hand to help.
• And if enough market feedback is gathered, a whole extension to the platform or tool can be planned.

‍

Below is a visual example of our process with discovery at the beginning along with analysis, wire-framing, blueprints and estimation. We also have an example of what happens when a change is added in the middle of the process.

At the end of analysis we usually update the SST (single source of truth) to include any made during active development.

Deployments happen regularly with a live deployment at the end of the process.