Year: 2010
User Stories are a Reminder to Collaborate
User stories are not a highly documented series of requirements but rather a reminder to collaborate about the topic of the user story—in other words, in agile development (good agile at least), the documentation is secondary to the collaboration. Source: “New to User Stories?“, William F. Nazzaro and Charles Suscheck, ScrumAlliance.org
Read More
New to User Stories?
Having coached traditional requirements, use cases, user stories, and agile development, I’ve fielded a lot of questions around the differences among the three major ways of specifying requirements, particularly by people migrating to user stories. This article compares requirements, use cases, and user stories against each other.
Read More
Concordion
Concordion is an open source tool for writing automated acceptance tests in Java. There are also versions for .NET, Python, and Ruby.
Read More
Agile, Multidisciplinary Teamwork
The article “<a href=”http://www.methodsandtools.com/archive/archive.php?id=17″>Agile, Multidisciplinary Teamwork</a>” by Gautam Ghosh presents techniques and tools used to create requirements with a team composed of the different participants of agile projects.
Read More
Understanding Non-Functional Requirements
This blog post is about understanding what non-functional requirements are, how they work, how to write them, and how to use them in real-life projects,
Read More
Requirements Engineering Qualifications Board
When having problems in projects these problems are mostly related to badly written requirements. the Requirements Engineering Qualifications Board (REQB) realized that problem and tries to change that by setting international standards for Requirements Engineering. By becoming REQB Certified Professional for Requirements Engineering you show that you are an expert in the field of Requirements […]
Read More