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.
Discover to Deliver is a book written by Ellen Gottesdiener and Mary Gorman. It aims is to help you to deliver a product that will please your customer. To achieve this goal, the book proposes a toolbox of techniques that are taken from multiple disciplines, from business analysis to software testing or product delivery.
Is your team struggling with unproductive requirements gathering meetings and workshops? Are you unsatisfied with how your Scrum team comes together to refine requirements and specify solutions? Have you heard about example mapping and want to know more?
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.
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.
Although many might tend to limit the concept of agile requirements to “user stories”, this book by Dean Leffingwell reminds us that there could be more than just a post-it on an information radiator when we talk about Agile requirements. The title of one of the initial chapters is “The Big Picture of Agile Requirements” and this book provides it, together with the small details that can help you write better user stories.
There are three roles in a Scrum team: the ScrumMaster, the developer and the product owner. This last role might be the most important for a team that uses an Agile project management approach in software development. The product owner has the responsibility of building and prioritizing the backlog. If this is not done properly, you will just not build the right product. This article presents the certifications available for product owners in Scrum.
Scrum Expert Copyright © 2009-2026 Martinig & Associates