Scoping
The scoping process works alongside our discovery kit and is comprised of different activities we use to build our understanding and initiate the creation of artefacts. The scoping process has the following phases: Understand, observe, ideate, prototype, showcase. These phases are not linear but can be returned to at any point if required.
Uncovering the project
Scoping results in a library of artefacts which serve as the blueprint for development.
These artefacts, such as wireframes, user flow diagrams and the requirements backlog, catalogue the project from frontend interface to the functionality beneath. Typically, scoping is undertaken with the expectation that it will proceed into development, but scoping can also take place in isolation.
If you must develop a business case internally or externally to investors, then project scoping will give you all the materials you need to validate the project with stakeholders and progress.
Once the business case is approved, return to us to continue the journey or take the artefacts created during scope to other development companies. With our process and ownership of the IP, you are in the driver’s seat and get to choose how and when to progress.
The Process
The scoping process works alongside our discovery kit and is comprised of different activities we use to build our understanding and initiate the creation of artefacts.
The scoping process has the following phases: Understand, observe, ideate, prototype, showcase. These phases are not linear but can be returned to at any point if required.
During the understand phase, we unpack the problem statement and uncover the requirements of the project. Following this, the observation phase challenges our assumptions, drafting personas and getting to know the end user.
Our designers will then begin ideating on the user experience and user interface in the form of sketches and wireframes. Finally, prototyping crystallises these designs into artefacts which represent the proposed application. There is a showcase at the end of scope which includes delivery of the final estimations for development time and cost.
The Benefits
A detailed scope provides enormous benefits by not only highlighting the goals of the project but by uncovering risks and assumptions. The earlier these things can be mitigated; the smoother and more cost-effective development will be.
Many of our clients find that the scoping process provides them a great deal of new insight not only about software development in general, but about their business and the attitudes of their users.
The processes we use during scope are applicable to a range of projects, not just those with an intended software outcome, so can be used by our clients when tackling any other challenge.
