Requirement Specification vs User Stories
This video explores what makes good requirements and how agile user stories help to improve the quality of requirements, whatever the nature of our software development.
user stories
Your User Stories Are Too Big
Product owners often struggle to translate their big ideas into small user stories that the team can deliver in a sprint. When a user story is too big, it is harder to understand, estimate, and implement successfully.
Technical User Stories Don’t Work
How do you organize the technical parts of your Agile software development work? Do you create Technical Stories or Technical User Stories alongside your User Stories? If so, we think that you are probably storing up some problems.
Driving Stakeholders Engagement with User Stories
The presenter designed this workshop during COVID times to engage stakeholders better by using User Stories more efficiently. The idea of the workshop is to help people move away from the notion that User Stories are merely a “As a .. I want .. so that” writing template.
Advanced User Story Mapping
User Story Mapping is one of the most powerful collaboration tools for planning complex development activities. However, what are the differences between a good story map and a great one? How does one design and lead a great mapping session?
Executable Specifications with Scrum
The book Executable Specifications with Scrum by Mario Cardinal starts with a strong statement: “This book aims to solve the recurring challenge encountered by many software development teams: They do not build the right software.” This is an ambitious goal, especially when you want to achieve it in a little bit more than 100 pages.
How to Value User Stories?
Business value, business value, business value. This presentation from Allan Kelly explores how to put a value on stories in a backlog while uncovering new requirements, elaborating specifications and valuable opportunities.