TAG: requirements

Author: Lorraine Pauls Longhurst Published: LPLSC Blog Date: 12 March 2009

What happens when Scrum projects do not have clear user stories?  What if the Business Analyst (or Product Owner) just provides functional requirements?

The best way to communicate requirements in a way that will make the developers more productive is for the Product Owner (or Business Analyst) to write requirements as user stories. They should be worded in the following way: ‘As a’ user ‘I want to’ do the following ‘so that’ the following benefit can be met. The only way to do this is to communicate with the user frequently which is a very important part of Agile Development.

Read more...