Creating User Stories For Product Owners

The user story is a core part of Agile Software Development. Where other methods of software development have functional requirements and technical specifications, Agile has user stories. These user stories serve to explain what the product should be able to do, without specifying details. This gives the team freedom to do things in a way that is efficient and practical while ensuring that stakeholders get the product that they want.

User stories usually consist of one or two sentences explaining who it is for, the desired behavior and the reason for the requirement. The typical form is: “As a [role], I can [feature] so that [reason].” By following this form when writing user stories, the team can cover the who, what, and why about a feature. Writing good user stories helps to ensure that the team creates valuable features for the product.

But who is responsible for writing user stories? The Product Owner is in charge of prioritizing and accepting user stories, but anyone on the team can write stories. If other team members write a user story, the Product Owner can accept or reject them before they are incorporated into the product backlog. If the Product Owner allows bad user stories into the backlog, it wastes time for the team because they do not contribute value to the product. Instead, the Product Owner should only allow user stories into the backlog that are independent, negotiable, valuable, estimable, small, and testable.

Independent

For a user story to be independent, it must address a specific action and contain all parts to fulfill that action. If a user story contains only a small portion of a process, it may depend on other actions to accomplish that goal. In that case, the user story is not independent. Alternatively, a user story may contain numerous actions that could each be an individual user story. These multiple actions should be split out into their own respective user stories.

59 Seconds Agile - Creating User Stories

59 Seconds Agile – Creating User Stories

A good judge of independence for a user story is to examine what a product will look like when that user story is finished. If that feature needs more work before it improves the value of the product, the user story may need more content to be independent. When the user story is finished, if the product has working new functionality, that user story likely satisfies the independence criteria.

Negotiable

A user story is negotiable if nuance and detail are left to the team to figure out. A good user story only hits the highlights, including the most valuable and critical details of a feature. Since most of the details about a feature are up for debate, the team can discuss the best way to implement the feature. During the development process, details about the user story should fall into place, while the team satisfies the criteria that are explicitly stated in the user story.

Valuable

To be valuable, a user story must contribute some information or idea to a project that improves the product for specific role or duty. Teams may try to create user stories by saying, “It would be nice if the product could [feature].” The problem with this type of thinking is that the suggested feature may not be useful for a particular type of user. The idea sounds nice on paper, but no users of the product actually need it. If the team spends time creating this feature, they have contributed no real value to the product.

User stories must be unique to be valuable. The team could write several different user stories for each individual role that might use the same feature, but the end result is the same as if the team had just written a single user story for that feature. The Product Owner must filter out or combine user stories that serve the same purpose, with only minor differences between them.

Prev <— Continue Reading —> Next

Our Favourite Agile Books

Read Our Reviews

Learn More about the Scrum Product Owner

The History of Agile For Product Owners

Agile project delivery principles evolved because industry leaders recognized that the linear nature of waterfall delivery created long windows of time between gathering requirements and delivering working software…

Read More

What is Agile to the Product Owners?

While traditional project management is still widely used, the benefits of an Agile approach to running a project are becoming more and more recognized. Where Agile has a distinct advantage over classic project management is the development of new products…

Read More

Why Use Agile as a Product Owners?

When determining if a move to Agile is right, a PESTLE can be used to simplify what factors should be considered. While Agile is sometimes thought of as a software development project management method, it isn’t just for these types of technology-centric companies…

Read More

59 Seconds Agile - Scrum Product Owner Training Course

59 Seconds Agile – Scrum Product Owner Training Course

The Agile Manifesto For Product Owners

Agile is a quick, simple, lightweight and effective way of managing projects. In traditional project management models…

Read More

The Agile Principles For Product Owners

When the Agile Manifesto was drawn up in 2001, it embodied four values and twelve principles that signaled a new approach to…

Read More

The Agile Fundamentals For Product Owners

Thinking of becoming a Scrum Master? Or are you already one, but you’re still new to the job? No matter what level of experience…

Read More

The Declaration of Interdependence For Product Owners

The Declaration of Interdependence establishes that all members, stakeholders, and customers are interdependent and…

Read More

The Agile Frameworks For Product Owners

There are many different Agile frameworks – all of them share the same philosophy and are built around the Agile Manifesto and Principles. But they vastly differ in their approaches, values, and structure. …

Read More

The Scrum Framework For Product Owners

The Agile Scrum framework is designed to deliver products and projects of any size. This includes projects, programs, and portfolios. Scrum provides guidelines on delivery techniques, events, and roles. Many of the same ceremonies are held within both a standard Agile scrum project and an Agile Scrum…

Read More

The Scrum Roles For Product Owners

Scrum is a useful tool for the creation, maintenance, plan, and execution of diverse products and services. The tool consists of…

Read More

59 Seconds Agile – Scrum Product Owner Training Course

59 Seconds Agile – Scrum Product Owner Training Course

The Scrum Team Size For Product Owners

The basics of Scrum can be easy but implementing them and succeeding with Scrum can be infinitely harder. Scrum …

Read More

The Agile Project Vision For Product Owners

At the heart of any great product is a great vision. It describes the primary goal or goals of a product and creates a focus that…

Read More

Forming the Scrum Team For Product Owners

Scrum is a framework that encourages delivery of potentially shippable product increments every 2-6 weeks. The work is…

Read More

Developing Epics For Product Owners

The term ‘epic’ in agile refers to a large user story that has not yet been defined in detail. Typically, an epic will cover a single…

Read More

The Agile Product Backlog For Product Owners

A Product Backlog is an organized collection of the existing User Stories (aka Wants and Needs) for an explicit business endeavor. Think of a shopping catalog of User Stories, ordered by urgency, that can be perused and selected from to determine what will be worked on during the current…

Read More

Release Planning For Product Owners

Although flexibility and adaptability are part and parcel of an agile methodology, this does not mean that no planning is required when…

Read More

Creating User Stories For Product Owners

User Stories are an integral part of the agile development process. They are an important agile technique that is used to frame…

Read More

Estimating User Stories For Product Owners

One of the principles of self-managing teams in Agile Scrum is working collaboratively with the Product Owner to effectively deliver…

Read More

Creating Tasks For Product Owners

According to The Agile Manifesto: “The best architectures, requirements, and designs emerge from self-organizing teams.” As a…

Read More

Estimating Agile Tasks For Product Owners

In Scrum, a list of user stories is produced and put together to form a product backlog, and each of these user stories will need to…

Read More

Creating the Sprint Backlog For Product Owners

The Sprint Backlog is defined as a group of user stories that are grouped together during the Sprint Planning Meeting.  This…

Read More

Creating the Deliverables For Product Owners

Agile Scrum provides the framework for delivery of the vision of an organization. Execution of the vision includes processes, ceremonies and project deliverables that are also known as artifacts…

Read More

The Daily Stand-Up For Product Owners

The daily scrum is an opportunity for developers or anyone committed to working in the sprint to talk to each other to make sure the…

Read More

Product Backlog Prioritisation For Product Owners

The product backlog is a key element of Agile software development. It facilitates a development environment that creates valuable features and products for stakeholders…

Read More

The Sprint Review Meeting For Product Owners

The Sprint Review meeting comes at the end of the sprint and the goal of this meeting is to have key people in the room to be able …

Read More

Demonstrating and Validating the Sprint For Product Owners

As organizations migrate to Agile principles, there may be questions about how the organization can prove that there is value…

Read More

The Sprint Retrospective For Product Owners

A very simple step by step guide to help you choose the appropriate product development methodology from…

Read More

Releasing the Product For Product Owners

One of the most important milestones any project will ever have is finally releasing their product and putting it out there. It’s the…

Read More

Regression Testing For Product Owners

In companies using agile development, it is common to introduce changes in a product incrementally. Along with the new changes, unexpected issues may arise, testing whether the existing functionality is broken or not becomes very important…

Read More

Scrum Master

Find out more about the Agile and the Developer Role

Read More

Product Owners

Find out more about the Agile and the Product Owner Role

Read More

Developers

Find out more about the Agile and the Developer Role

Read More

More Articles

Read More

  Chicken Appreciation Society

Share
Translate »