Building the Right Scope

December 15, 2011

Use cases, user stories, or backlog items already define broadly the scope of a project. Many teams consider requirements as something provided by the business users, product owners or customers. Asking business users to provide the scope is effectively relying on someone who has no experience designing software solutions to give us a high level solution design. This article explains how project teams can work together with business users to come up with the right scope. To reach this goal, you need to start with business goals, and not with user stories, and derive the scope from that.

Advertisements

Agile Requirements

October 3, 2011

The clarity of requirements is an issue for many  software development projects. Based on a course on Agile Requirements, this article at summarizes the levels of Agile (and frankly non Agile) requirements and how you can use a four step process for gathering them.


%d bloggers like this: