What are user stories?
User stories come in the form of “As a <User Type>, I want to <Function> so that <Benefit>.” The reason why scrum uses these user stories is to translate all functionality into a business benefit. It also avoids detail that might lock people into certain design options and avoids pigeonholing the functionality. They should be small enough to be coded within the course of a few days. Long stories will slow down release cycles.
How do you write a good user story?
Well-formed user stories follow Bill Wake’s INVEST acronym
Independent — Story should be self-contained and not dependent on another user story
Negotiable — User stories can always be changed until they are part of a sprint
Valuable — Must deliver value to the end user
Estimable — You should be able to estimate how big it is
Small — It should be not be so big to make it impossible to plan it
Testable — Must provide the information to make test development possible
Examples of good user stories
“As a power user, I can easily modify existing application configurations to streamline my work process.”
“As a system admin, I can give or remove permissions based on both profile and by specific projects that may require additional functionality.”
Our vision is to connect individuals and social organizations with fundamentally new opportunities. We are constantly inspired by their missions and want to assist them. Through our mobile app solutions, we hope make their lives easier.
If you are interested in our mobile app development process or want to find out more about us, check out our first post: Intro to Deverse athttp://bit.ly/introtodeverse