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.
Uncertainty in the Product Backlog is a big risk for the schedule of a Scrum project. The problem is that the full scope of the release can be quite hard to estimate because the requirements are not well-know early on. Confounding this problem is that frequently the release date is a hard deadline.
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.
This customer focus listening workshop covers the basics of customer development: interview, building questions and adopting your customers’ language. You will learn: * How to get insight out of 90 seconds, stakeholder, customer or annoying boss * Basics of interview technique (open versus closed questions etc) * Cognitive Biases * Aspirational versus Experience driven Stories (stopping your customers lying to you)
Gojko Adzic is known in the Agile software development world for his work on requirements presented in his book “Specification by Example – How successful teams deliver the right software”. In this small and easy to read book, he focuses on a single tool that could be very useful for Scrum teams: impact mapping.
Copyright © 2009-2021 Martinig & Associates