Utilize Use Cases, User Stories, Personas, and Scenarios to Define Requirements

One good approach to reducing unnecessary code growth is to think about who is using the system and how to develop what the user needs.

Too many projects attempt to define requirements by defining functional and nonfunctional requirements. But these requirements don’t explain how a person will use the system or under which scenarios this functionality has to perform. Use a requirements approach that provides the project team with the context to understand the requirements.

Who Wants That Checking Account?
by Clarissa, senior manager
Clarissa

My project team was stuck. They had partly implemented a whole bunch of features, but nothing was working. I called a meeting ...

Get Manage It! now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.