Agile development methodologies succeed because they help development teams be as effective as possible. Development teams do not, however, work in complete isolation. The company they work for has a strategy. The company manages a portfolio of products, and targets a particular product at specific market problems. Within that context, […]
Ishikawa Diagram / Marketing / Product Management
Posted on:
Buyer Personas And User Personas
A lot of people stand up a variation of “If you build it, he will come” (from Field of Dreams) as a copy-writing hook for whatever they are about to tell you about creating products/services/whatever. We’re no better. We’re going to tell you that there is a big difference between […]
Austin TX / Business Analysis / Ishikawa Diagram / Product Management / Requirements / Requirements Models
Posted on:
Defining Problems at ProductCamp Austin 1
Jun 14th was the first productcamp in Austin (and the second one anywhere). It was a great event, and here’s the presentation that I did on how to define the strategic problems that drive our products.
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.
Business Analysis / Communication / Ishikawa Diagram / Product Management / Requirements / Requirements Models / Writing
Posted on:
Defining Problems With Cause And Effect Diagrams
The Cause and Effect diagram is also known as a fish bone diagram, because it resembles the skeleton of a fish. Using a cause and effect diagram can be the most effective way to define the problems that you intend to solve with your product. Get your stakeholders engaged in […]
Requirements / Requirements gathering / Requirements Models / UML Modeling
Posted on:
Uncovering Requirements With UML Class Diagrams Part 5
In this article, we build on our ability to represent straight forward business relationships in UML class diagrams. These relationships describe how two objects are related to each other. Representing relationships in class diagrams helps us to better understand the domain and helps us to uncover hidden requirements. Occasionally, we […]
Requirements / Requirements gathering / Requirements Models / UML Modeling
Posted on:
Uncovering Requirements With UML Class Diagrams Part 4
The hardest part of gathering requirements effectively is uncovering the requirements that people don’t immediately tell you. You have to ask the right questions. And one of the best ways to find the right questions to build a class diagram of the business domain. This article continues our introduction to […]
Requirements / Requirements gathering / Requirements Models / UML Modeling
Posted on:
Uncovering Requirements With UML Class Diagrams Part 3
UML Class Diagrams are very effective at uncovering requirements. They give us insight into how the business thinks about objects and their relationships. And from that understanding, we think to ask questions we might otherwise overlook. In this part of our series, we look at how to represent when one […]
Requirements / Requirements gathering / Requirements Models / UML Modeling
Posted on:
Uncovering Requirements With UML Class Diagrams Part 2
We continue our exploration of UML Class Diagrams with this article that explores how to represent basic business relationships in a class diagram. Drawing these relationships can dramatically clarify requirements documents. Using a class diagram to supplement other requirements documents provides for a centralized reference that enables a shared understanding […]