Year: 2011
Building the Right Scope
In this article from chapter 4 of Specification by Example, author Gojko Adzic explains how to work together with business users to come up with the right stories and that the key idea to achieve that is not to start with user stories but with business goals and derive the scope from that.
Read More
Discovering Business Architecture Value
In business use case (BUC), an abstraction of the system use case model, business actors with specific business goals interact with other business actors. It is primarily an external view of the business model or area of interest. This article explains how business use cases can help business architects, helping them to discover quality high […]
Read More
The Concept of the Minimum Viable Product
Does the word ‘minimum’ immediately raise your hackles? This article emphasizes that learning to prioritize, getting to production early, and subsequently delivering in small increments are key disciplines in the practices of Agile and continuous delivery. The term Minimum Viable Product (MVP) has been around, in various forms, for a long time. I’ve also heard […]
Read More
Agile Software Requirements by Dean Leffingwell
The title of one of the initial chapters of the book “Agile Software Requirements” by Dean Leffingwell is “The Big Picture of Agile Requirements”. This emphasizes that agile requirements are more than user stories on a small card. In this book, Dean Leffingwell presents the big picture of agile requirements, together with the small details that […]
Read More
Functional Requirements Are Not Always User Stories
What happens when Scrum projects do not have clear user stories? Because Product Owner has the subject matter expertise and decision making capabilities, that does not mean that he can clearly communicate the requirements in a way that will make the developers/testers as productive as possible. This blog post explains that the best way to […]
Read More
User Stories Lifecycle
In this blog post, Henrik Larsson explains the lifeycle of user stories from the Release planning meeting to the release tracking stage where the product owner checks if the release date and contents can be kept.
Read More