So you have taken the plunge and signed on to develop an app with StayShure (or someone else, that's okay). What happens next?
Once your project begins active development, it is passed to a project leader who will help move the idea from the proposal stage to “let’s make the blueprints.” At this point in app development, there are three steps we work through:
Most clients have a simple site map in mind and also know what kind of users they want to target, but user stories are often unfamiliar to our clients.
What Are User Stories?
User stories have been around since the late 90s, but they aren't often utilized outside of the software development world. To be precise: a user story is a short description of an action a user wants to perform while using a piece of software.
User stories most often follow this formula: Who, What, Why. Sometimes they can be more complex, but we find keeping it simple is best. This pattern works well for us: As a <user> I <verb> (e.g., want to/can/am required to do something)> <some goal> (e.g., delete users from the system/verify my phone number, etc.)> so that <some reason>.
Examples of Good User Stories:
It's probably best to provide some examples of good user stories. Let’s imagine we are making an app for a vet clinic. Remember the pattern, Who, What, Why:
The Context of User Stories:
As you can see from the above examples, good user stories are concise and target the smallest action a user can perform in an app. If we use building blocks as a metaphor, user stories are the smallest block in the pyramid. For this reason, When a user story gets too complex, it needs to be broken down into more user stories. If we find conjunction words in our user story like, “but,” “and,” or “or” we know we should make multiple user stories. When we have similar stories, we group them under a heading called a “Story Epic.”
While user stories fall under the umbrella category of an epic, epics fall under the umbrella of Themes. This means User Stories and Epics support a specific Theme. Sometimes we can simply organize themes around the site pages: e.g., schedule, blog, dashboard, etc.).
Two Rules for Effective User Stories:
To use user stories effectively, we follow two basic rules to keep them as simple and valuable as possible:
Conclusion: User Stories Make App Developers Just as Happy as the Customer
Hopefully, you are convinced that user stories provide an excellent early step in app development! In addition, we have found that breaking down the development process into bite-size pieces makes everyone feel like progress is being made quickly and that the road map for development is easy to track. We believe everyone is more satisfied with custom app development when the client’s bulls-eye is defined as narrowly as possible. In other words…When an app development client wants to have custom software developed we ensure that we write clear user stories so that the software is built according to the owner’s vision. What’s your vision? Let’s connect to see how we can help bring it to life!
If you haven't heard, we offer fractional CTO services which can continue pre and post software development, or just be an add-on to your existing business so that your tech is the most efficient and profitable for your company. Here is a summary of how that can help digitally transform your company and here is the more detailed explanation for the curiously-minded.
We post our new articles to our Linkedin page each week- let's connect there!Follow StayShure on Linkedin