Year: 2012
Minimal Viable Products
In this blog post, Cory Foy discusses how to apply the Pareto law, the famous 80/20 rule, to the concept of minimal viable product. He defines two starting positions: you have to sell a solution for a problem or there is an actual need in a market. A Standish research shows that 45% of the […]
Read MoreDo Not Design for Users
In this blog post, Mike Long discusses the current trend to design applications for specific users or “personas”. His point is that “focusing on individuals might improve things for one person at the cost of others.” He prefers instead Activity-Centered Design (ACD) that focuses on the activity context in which individuals interact with the product.
Read MoreOrdering 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 MoreFour 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 MoreHow 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