Year: 2012

Ordering the Product Backlog
In this article, Brent Reid discusses the fact that in Scrum, the product backlog should be ordered and not prioritized. His point is that priority has a meaning only within a certain context. Thus what is high priority one day could be low priority in the future. Thus, the product owner must deliver a totally […]
Read More
Four Mistakes to Avoid in Requirements Meeting
Adriana Beal has wrote an interesting post discussing four mistakes to avoid when leading a requirements meeting. The first mistake is to create unnecessary meetings and/or failing to recognize when one is needed. The second mistake is failing to prioritize the order in which items will be discussed, and whenever possible, the amount of time […]
Read More
How Long Do Requirements Take?
In this blog post, Karl E. Wiegers tries to answer the question: How long will it take to “do requirements” on your software project? The answer is naturally: it depends! The post lists conditions that can accelerate requirements development and other factors that lengthen the time needed for effective requirements development. Things are also different […]
Read More
Minimum Viable Hypothesis
In this blog post, James Shore suggests that the concept Minimum Viable Hypothesis should replace the idea of Minimum Viable Product (MVP). His point is that when you focus on the product you could end up being in love with it.
Read More
Busting the Myths of BDD
The ideas behind Behavior-Driven Development (BDD), Specification by Example and Agile acceptance testing are deceivingly simple, but have proved far from easy to implement. Yet most of the complaints online come from misunderstood ideas which lead to misguided attempts. This talk busts the myths around these techniques and shows how successful teams all over the […]
Read More