Session Details

Writing Requirements as User Stories

Regular Session

Product Owners in Agile software development are tasked with writing requirements as user stories. Furthermore, Product Owners have to manage the value of these stories and prioritize them in Product Backlog so that the development team can deliver the most valuable functionality first and get it into customers hands for quicker feedback than in traditional Waterfall development. Product Owners really cannot do this alone, they need help from the development team. The development team can help by asking pertinent questions, by helping the PO determine what the acceptance criteria may be and by showing the PO how to break user stories down when they are too large. The better understanding the PO has of the development team is looking for, the better he will get at writing them on his own. As a result, the better user stories can be estimated more accurately by the development team that will be doing the work. This session will focus on each of these aspects of user stories and estimation.
Emily Harshman

Agile Practice Lead


A software development conference in the Louisville, KY area on March 28 - 30, 2018 designed to cover all aspects of software development regardless of development stack.

Contact Us
Keep in Touch