It is the process of understanding your whole vision and gathering requirements for your app before heading into app development.
Think of it like hiring a building architect to design a house before you hire the builder.
To define scope writing, we first need to define what we mean when we refer to your project’s scope. The scope is essentially the extent or entirety of what it is involved to produce the end product. Every person who works on your project, including you, should have a clear understanding of what is included, more specifically, the technical requirements, deliverables and how the final build will look and function. Scope writing on the other hand, refers to the process of manually writing and identifying these requirements to set a timeline for each deliverable to be produced. While is sounds fairly simple, it is a highly involved and detailed process, which we have outlined for you below.
Scope writing dictates every step and requirement that is involved to development your final product. Identifying the scope early on in the project timeline, results in a more efficient development and reduces the risk of delays due to uncertainty and undefined project details. By defining a timeline for production, all persons involved will have a clear understanding of the expectations and individual requirements needed. At App Boxer, we work collaboratively with you to ensure that every step taken is within the scope defined and meets your expectations.
Failing to identify a clear and detailed scope can put the project as risk of delays, increased costs and ultimately lead to a lack of confidence in your final product. For this reason we have spent time ensuring that our scope writing processes are highly detailed. We also know that understanding the full extent of a projects scope can be an intimidating feat, therefore our team will take the time to sit down and explain each detail so you have the confidence that together we are building a product that you can be proud of!
While there is a lot that goes into building an app from the ground up, our scope writing process can be broken down into 4 steps. Below we have outlined what this process involves.
Our first meeting is set with the intention of getting to know each other and what your idea is all about. The focus will be on understanding your intentions and discovering your value proposition – what is going to make you stand out from the rest. This is the first step to understanding what will be involved and begin mapping out the scope. During this collaborative process, we are there to help guide you and create a plan that suits both the needs and requirements of the app.
User Flow Diagrams
Following our Discovery Workshop, our Solutions Architect will begin brainstorming and writing the User Flow Diagrams. This involves scoping out a high-level overview of your app and establishing the primary scope that will be carried through to development. This includes listing all the key features and functions that are necessary, as well as defining the technical requirements for development.
Next we move onto the wireframes. This is where you will start to the see the app begin to take shape. The designer on the project will take the flows as outlined above and begin to scope out the user interactions. These wireframes are essentially a black and white blueprint of how the app will function and at this point the designer will begin to replicate the users interactions. In this phase we start to establish the user’s expectations and needs and map out any tools required for integration.
The next phase, which involves writing the user stories document, is the most crucial part of the scope writing process. This is written by our experienced Business Analyst, who compiles the scope outlined in the User Flow Diagrams and Wireframes into a single document referred to as the User Stories. This process involves defining each step a user takes when interacting with the product. Each step is further broken down into the feature, functionality, interaction and technical back end development processes required to produce.
The user stories are essentially like a shopping list for your app, it dictates every detail involved in the development process, the cost and time required, and outlines plans for future iterations. They also give you the freedom to break down the development into phases so that you can launch with a lean MVP (Minimum Viable Product) and get to the market faster. It gives you and your investors the confidence in your product and a detailed roadmap to development.
We'll help you brainstorm the idea
or go straight into exploring