Home » Archives

Content in the Blogs category

[11 Dec 2013 | Comments Off on Find Missing Requirements | ]

This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.

[12 Nov 2013 | Comments Off on Perfect Requirements | ]

In this blog post, James Christie starts from the fact that perfect requirements don’t exist to discuss the idea that the quality of requirements is directly influenced by the time and money you invest in crafting them.

[23 Oct 2013 | Comments Off on Why Should You Write Requirements | ]

In this blog post, By Scott Sehlhorst starts with a simple fact: if there is a lot of discussions on how to write requirements, there is not so much material on why to write requirements. His advice is that you should start by thinking about why you write requirements before you decide how to write your requirements.

[6 Sep 2013 | Comments Off on Do Agile Needs Business Analysts? | ]

There is no business analyst role in the Scrum Agile project management framework. Based on this fact and some perceptions about Agile, Roland Hesz tries to answer the questions “Do we need a business analyst on an agile project? Are there Agile business analysts?”.

[15 Jul 2013 | Comments Off on From Value to Solutions in Agile | ]

Agile uses mostly user stories to capture requirements. In his blog post, Jean-Jacques Dubray explains that there is a problem with user stories because they tend to focus on the solution and not on the problem definition.

[7 May 2013 | Comments Off on Describe User Interaction with Scenarios and Storyboards | ]

A user story is a tool to describe the product functionality, but it is less useful suited to describe in detail the user interaction. Agile scenarios and storyboards are tools you need to describe the interaction steps. In his post, Roman Pichler what scenarios and storyboards are, how they can be used effectively in an Agile approach and how they relate to user stories.

[25 Feb 2013 | Comments Off on Using Approval Branching for Business Requirements | ]

When the business changes rapidly, this is a problem for a development team that has in its current release trunk both approved and unapproved features. In this blog post, Jack Low presents a solution to minimise the issues created by unapproved features in the codebase at the time of a release and contrasts this approach with popular alternatives like Feature Branching and Feature Toggling.

[13 Feb 2013 | Comments Off on Creating a User Story Map | ]

A user story map is a technique created by Jeff Patton where you arranges you user stories into a useful model to help understand the functionality of the system. In this blog post, Steve Rogalsky explains how to create a user story map.

[7 Jan 2013 | Comments Off on Writing Better Requirements with Examples | ]

Gathering requirements for software development is not always easy and IT guys will often complains that customers have difficulties to express what they want to achieve with a new development project. In this blog post, Lars Hoidahl discusses this topic and explains how examples and screen sketches can help to write better requirements.

[12 Dec 2012 | Comments Off on User Stories That Are Too Big | ]

In this blog post, Jeffrey Davidson discusses the fact that a common issue for Scrum teams is that their user stories are too big. He explains that many teams ask for larger stories because they don’t know how to slice the work into smaller pieces. Writing smaller user stories will make your team happier and more productive. There are many reasons behind the need for small user stories.