One of the integral results of the CabForward℠ Discovery Process is the development of User Stories, which define the features of a product or application. User stories are written in a short, 3-part format: As a [role] I can [function] so that [reason]. There are no technical or interface details at this level.
The next step is for our client to prioritize the stories, and we estimate the difficulty of each story on a scale of 1, 2, 4, or 8 points. Stories that are bigger than eight points are too complex and need to be broken into smaller pieces. What does this look like in practice? Here are some examples:
2. As a student, I can find my grades online.
3. As a diner, I can read reviews of a restaurant.
In the example above, each point represents four hours of work at $200 hr. When you arrive at this point of your planning, you can get an approximate idea of what the project might cost. Feature changes during development, however, will impact the investment required. So will making changes to functionality and appearance. Feature changes are usually the result of the client learning more about what the user wants the app to do and pivoting to address those features and benefits they value.
User Stories are very useful in helping the client gain clarity about the features and functions needed in the product, and help the development team make a plan for efficient engineering of each feature. These user stories will then go into a project tracking tool where they can be scheduled and edited as needed. You have complete visibility into the project tracking tool, so you can see the progress being made, and can change course as needed.
We pride ourselves in being transparent during the development process, and making sure that you are in the driver’s seat and we are supporting you. We want to earn the role of Strategic Technology Partner. Why not contact us today?
Request a Discovery Session
Request a copy of the CabForward℠ Startup Handbook