I am a big fan of boxes and arrows, but this time, Jeffrey Davidson found a great article by Dan Willis before I did, and told me about it. Thanks Jeffrey! The article is about how to deal with the what and how of requirements and design – and it […]
Business Analysis / Requirements
Posted on:
Stakeholder Goals: Principal vs. End User
In our earlier article about managing stakeholder goals, we looked at the relationships between principal stakeholder goals and end-user stakeholder goals. We also showed a way to trace those dependencies. But that approach does not provide us with any insight about the alignment (or lack thereof) between differing goals. This […]
Business Analysis / Interaction design / Product Management / Requirements / Software development / UX
Posted on:
Managing Stakeholder Goals
A couple weeks ago we wrote about Outside-in Software Development, by Carl Kessler and John Sweitzer. One of their ideas about stakeholders and goals has got us thinking about traceability.
Business Analysis / Project Management
Posted on:
Estimating an Inestimable Project
We create cost estimates at many times in a project. From budgetary estimates at the start of a project all the way to PERT estimates of tasks in a work breakdown structure. Creating a budgetary estimate seems impossible – you have to make many assumptions, your estimates are based on […]
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 Process Modeling / Business Rules / Product Management / Requirements / Requirements gathering
Posted on:
Elicitation Techniques for Processes, Rules, and Requirements
Each elicitation technique we have in our toolbox is a tool. But not every elicitation job is the same. If we have a hammer, we might be working with nails, or screws, or even an egg. In our analysis, we have to develop a deep understanding of our customer’s business(es). […]
Business Analysis / Business Rules / Communication / Consulting / Requirements / Writing
Posted on:
Why Separate Rules from Requirements
Separation of business rules from requirements is a good thing. Not because of semantic distinctions, but because it allows you to write better software, write it faster, and change it more easily. This article is a response to an excellent comment on our recent article about hidden business rules. Thanks […]
Business Analysis / Business Rules / Requirements / Requirements gathering
Posted on:
10th International Business Rules Forum
The 10th International Business Rules Forum is coming up fast in October 2007. Scott Sehlhorst and James Taylor will be presenting Getting it Right. Rules and Requirements in Software on Thursday at the conference. The articles on rules and requirements that he and I have been publishing on our blogs […]
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 […]