When working with developers, it’s your job to remove roadblocks and motivate them to build the product according to Specs. Combine Agile development, scrum and user personas to create user stories, and you get a solid plan of action that’s easy to follow, and reduces the potential for miscommunication on feature design and development.

User Stories

1. Start with a feature or product

Once you have a feature design you need to document all this so your developer knows what to create. Depending on the product or feature you choose, you will have an Epic, which is a group of similar features or features that exist to accomplish a certain goal of the feature. 


2. Break that feature down into smaller goals

One of the key principles with agile and scrum is to break down the feature or product into digestible pieces that can be completed in one development cycle, called a sprint.

Most sprints range from 1-3 weeks. All features have to be broken down into tasks that can be done within that timeframe. 


3. Identify User Personas

These can come from your marketing team, but you may also need to develop user personas based on your own conversations with customers. For example:

Sara is a 29 year old, young professional who loves to use the latest, hottest apps, but she doesn’t have time to keep up with all the new ones or keep track of all her log-in information. She feels naked without her tech gadgets and enjoys browsing through sites like Engadget and VentureBeats.


4. Create user stories

How do you turn a feature into a small chunk that is actionable? Turn the features into user stories. A user story is a way to express feature requirements as told from the perspective of the person that wants that feature.

For example: “As a <type of user>, I want <some goal>, so that I can <reason>”

Or: “As an existing user, I want to edit my location in my profile, so that I can keep my profile up to date.”


5. Include details with user stories

Once you have your user story, you’ll want to include as much detail as you can with each of them. Include mockups, use cases and acceptance criteria and/or tests that QA engineer should perform. Going back to the first point, all of your user stories will be combined to support an Epic, to clearly show how and why to build certain elements. 



Want to read more? Check out our post, What is Agile Development and Why is Everyone Talking About It?.