Almost everything I’ve read about use cases focuses on describing what needs to be added to your product. Agile development says “get it working first, make it better second.” That means changing the way the software enables a user to do something they can already do. How do you manage […]
Administrivia / Agile / Business Analysis / Prioritization / Product Management / Project Management / Requirements / Requirements gathering / Requirements Models / ROI / Software development / Use Cases
Posted on:
Most Engaging Articles of 2009
Engagement – that’s what this whole product management blogging thing is about. Check out what Tyner Blain readers found to be the most engaging articles in 2009.
Agile / Business Analysis / Interaction design / Interface Design / Product Management / Requirements / Requirements Models / Software development / Use Cases / User Stories / UX
Posted on:
Design-Free Requirements
Design-Free requirements are important for two reasons, and hard for two other reasons. Design-free requirements are hard because you “know what you want” when you should be documenting “why you want it.” Writing design-free requirements can be hard when you don’t trust your development team to “do the right thing” […]
Agile / Business Analysis / Ishikawa Diagram / Product Management / Requirements / Requirements Models / Software development / Use Cases / User Stories
Posted on:
Concise Requirements
Concise requirements give your team a useful, easy to read and easy to change understanding of what must be done. Great requirements exist to do three things: Identify the problems that need to be solved. Explain why those problems are worth solving. Define when those problems are solved.
Business Analysis / Product Management / Requirements / Requirements Models / Uncategorized / Use Cases
Posted on:
Use Case To Actor Mapping
We know the importance of identifying the use cases that enable our business goals. We also know the value of understanding the actors that will use our products. This article shows how to demonstrate a simple but powerful view that maps the use cases to the actors.
Agile / Business Analysis / Product Management / Requirements / Requirements Models / Software development / Use Cases
Posted on:
Cockburn Affirms: Use Cases Rule for Agile!
We’ve been promoting use cases as the right way to approach agile requirements, and in a recent article, Alistair Cockburn stresses the importance of use cases. Over the last three years, he has found that teams that avoid use cases consistently run into the same three problems. We defer, of […]
Business Analysis / Interaction design / Prioritization / Product Management / Requirements / Requirements Models / ROI / Software development / Use Cases / UX
Posted on:
Use Case Management is a Tough Balancing Act
Learning how to write use cases can be tough, but it is simple compared to the balancing act of determining which use cases to write and how to manage the expectations of all the stakeholders that are involved. It can be a difficult balancing act to prioritize use cases to […]
Business Analysis / Business Process Modeling / Business Rules / Product Management / Requirements / Requirements Models / Use Cases
Posted on:
Global Processes and Business Rules
We’ve written before about the importance of separating rules from requirements, particularly in use cases. We wrote that with the goal in mind of reducing the costs of system maintenance. Low-level rules like decision, calculation and inference rules tend to change frequently – and independently of other requirements. So a […]
Business Analysis / Business Rules / Requirements / Requirements gathering / Requirements Models / Use Cases
Posted on:
Business Rules Hidden in Use Cases
Business rules are not requirements. Yet they are often gathered at the same time as requirements, from the same sources, by the same business analysts. And unfortunately, often documented in the same artifacts. In this article we look at some of the ways that business rules are commonly hidden inside […]