What is the right level of detail for writing requirements? What about for writing specifications (functional, non-functional requirements, etc)? The answer is that there is no one answer. But there are guidelines, and reasons to write more detail, or less detail – for any given product or project, and any […]
Business Analysis / Expert systems / Prioritization / Product Management / Project Management / Requirements / Requirements Models / ROI / Use Cases
Posted on:
Prioritization and Value Maximization
We all know the story about the emperor’s new clothes. I’ve been thinking about prioritization and scheduling, and as far as I know, no one is promoting that we maximize value – they (and we) have been promoting that we do the most valuable stuff first. Doing the most valuable […]
Business Analysis / Product Management / Requirements / Requirements Models / Use Cases
Posted on:
Elastic Users, Actors, and Roles
In About Face 2.0, Alan Cooper describes the elastic user as an ill-defined user who’s characteristics change to suit the needs of the developer – sometimes an expert and sometimes a novice. However, some of the otherwise good techniques for managing actors and use cases exacerbate this problem instead of […]
Business Analysis / Business Rules / Product Management / Requirements / Requirements Models / Use Cases
Posted on:
Use Case Example With Business Rules
In our ongoing exploration of how to meld the worlds of business rules and requirements, we look at an example use case and see how to extract the business rules.
Agile / Product Management / Project Management / Requirements / Requirements Models / Software development / Use Cases
Posted on:
Benefits of Agile Story Decomposition
When you plan a release, agile user stories, or classic use cases are the best sized pieces to use in the planning – from the perspective of your customers. Each user story can be further decomposed into a set of specifications, and those into development tasks. Development tasks are the […]
Agile / Agile Project: Ratings / Requirements / Requirements Models / Software development / Use Cases
Posted on:
Nexus – Use Case Definition for Bundles
Yesterday, we identified the high priority goal for the third release of nexus to be supporting creation of bundles of articles. In this article, we will define the use cases we need to support.
Agile / Agile Project: Ratings / Product Management / Requirements / Requirements gathering / Requirements Models / Software development / Software requirements specification / UML Modeling / Use Cases
Posted on:
APR: Mixing It Up With Design And Requirements
With a definition of the important use cases for our agile project, we can move to the logical next step – which is what exactly? Prototyping.
Agile / Agile Project: Ratings / Business Analysis / Product Management / Requirements / Requirements Models / Software development / Use Cases
Posted on:
APR: Prioritizing Use Cases – Vote Three Times
In our agile project case study we defined corporate goals and user personas, and from our understanding created a list of use case names. We refined those use cases into use case briefs, filtering out some of the use cases (for the first revision) narrowing the list to six use […]
Agile / Agile Project: Ratings / Business Analysis / Product Management / Requirements / Requirements Models / Software development / Use Cases
Posted on:
APR: Use Case Briefs
Each of the use cases defined as part of our use case names post is described at a high level of detail here. The goal is to get a broad view of the domain for our project so that we can focus on the most important elements. This is a […]