Our Development Process.
Failing to plan, is planning to fail – luckily we have an airtight process we can abide by to get your project up and running in the right direction. The development of cutting-edge software starts with a clear plan and process to follow, and here at JustSolve we trust in our process to ensure that every piece of software developed by us fulfils the needs of your business and clients no matter how big or small they may be. Using an Agile-Scrum methodology, we can take on some of the most complex projects and still come out with an end product that satisfies the client.
The team lead (usually the Scrum Master) will lead a session to understand at a high level what is required from the project and/or solution.
Landscape & Tech Research.
The strategy team looks at the current and future product landscape to understand what features and user journeys work well and which can be improved upon. In tandem, the development team will start to identify the tech which will may be required to make the project a reality.
User Journey Mapping.
Using insights gathered from the kickoff session and the landscape research, the team will start to map out (in as much details as possible), the core user journeys we expect the various users to encounter when using the solution.
Review – Pivot or Persevere.
Together with the dev team, the strategy team goes through each user journey to understand how they fit in with any tech boundaries or limitations, and where the user journeys will need to be adapted.
Using the agreed upon user journey maps, the team will start to quickly sketch some of the core screens that will form part of the system. This can either be very lo-fi sketches (pen and paper) or initial wireframes. This is entirely dependent on the needs and complexity of the project.
Hi Fidelity Mock-Ups.
Using Adobe XD, the design team will flesh out any required hi-fidelity screens into mock-ups and if required, connect them up into an interactive prototype.
Business Requirement Specification (BRS).
A business analyst will take the work done thus far and define the project by documenting the user stories, business processes, business rules and integrations related to each mock-up in the previous step, which will then define the BRS. NB: This step is not always necessary, especially if an agile approach is adopted.
Systems design is the process of defining the architecture, modules, interfaces, and data for a system to satisfy specified requirements. An Architecture Design Document or System Requirement Specification (SRS) is created to guide the delivery team as to why some technology and architecture choices where made.
The Scrum Master will break down the project into a series of user stories which form the backlog. These are prioritised and then grouped into sprints.
Setup meetings – planning, showcase, retrospective, steerco, VPN, planning tools, source control, system access, infrastructure, deployment pipeline, DevOps, hosting etc