Home » Archives

Content in the Blogs category

[12 Mar 2012 | Comments Off on Visual Models for Software Requirements | ]

Software requirements are often thought to be textual material that can take the form of free “system shall…” statements, user stories, or “give when then” of behavior driven development. This blog post explore the usage of visual models to capture software requirements. It explains that models are not requirements, but they help us find and understand requirements.

[6 Feb 2012 | Comments Off on Using Use Cases or User Stories in Scrum | ]

This blog post defines the concept of use cases and user stories and discusses how and when they should be used in an Agile software development project. User stories are different from use cases because they are centred on the result and the benefit of the thing you’re describing, whereas use cases are more granular. The author recommends that you shouldn’t start writing use cases until the team specifically asks for them.

[5 Dec 2011 | Comments Off on Measuring the Success of Requirements Gathering | ]

The best metric to measure the success of business analysis is to evaluate if business objectives for each project were achieved. This is however not always easy to do and this blog post proposes other metrics to get good indicators of success of the business analysis efforts.

[23 Nov 2011 | Comments Off on Just In Time Software Requirements | ]

Elena Yatzeck shares in this blog post her thoughts about “value spike”. A “spike” is a short piece of work within an agile project in which one or two programmers may be assigned to do outside of the iteration structure. The goal is to investigates unknown technology problems well enough so you can estimate them. In the same intent, a “value spike” is time that the Product Owner takes to assemble the right Subject Matter Experts (SME) for a meeting to determine the authorship and impact of a requirement whose …

[29 Sep 2011 | Comments Off on 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 communicate requirements in a way that will make the developers more productive is for the Product Owner to write requirements as user stories.

[12 Sep 2011 | Comments Off on 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.

[18 Aug 2011 | Comments Off on We Are all Part of the Conversation | ]

In this blog post, Adriana Beal discusses the fact that all stakeholders in a project are part of the exploratory process of gathering requirements.

[10 Aug 2011 | Comments Off on 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.

[27 Jul 2011 | Comments Off on 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.

[14 Jul 2011 | Comments Off on 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.