Year: 2011
Correct and Complete Requirements
Jim Hertzfeld discusses in this blog post the correctness and completeness of software requirements. These two characteristics of good requirement are the responsibility of the end-users.
Read More
Common User Stories Mistakes
In this article, Krystian Kaczor explains that expressing requirements as user stories causes a lot of trouble to Scrum teams. He shares the five most common mistakes people make writing user stories.
Read More
Communication Content in Software Requirements Elicitation
This article presents a study performed to investigate the communication content of the current communication practices between developer and customer in Malaysia. The results of this study revealed some important notes on the practices of communication content during software requirements elicitation process in Malaysia.
Read More
What Makes Good Requirements
With this blog post, Jim Hertzfeld list the characteristics of good requirements according to the IEEE standards and starts a series on on how these characteristics can improve requirements on your project.
Read More
Business Analysis and Agile Development
Lisa Crispin interviews Mary Gorman about getting “just enough” information about desired behavior of a new feature without creeping into “Big Up Front Design” which is a balancing act for many Agile practitioners.
Read More
The Importance of Backlog Prioritization
In this blog post, Maurits Rijk explains the importance of a prioritized backlog to deliver business value as quickly as possible in a Scrum project.
Read More