Author: Marc Talbot

General

First, break all the requirements

What? In 1999, Buckingham and Coffman authored First, Break All the Rules. They used Gallop data from manager interviews to identify how good managers drive employee satisfaction. Internally at ArgonDigital, we

Read More »
General

When ROI isn’t enough

When we work with IT teams, one area that we emphasize is the importance of understanding the business value of what we’re working on, whether that is at the feature,

Read More »
General

Design Patterns in Software Requirements

Ok.  I said it.  The dreaded “D-word”.  Design.  We’re not supposed to do that.  Let the designers do the designing, and let the business analysts define the requirements.  Actually, I’m

Read More »
General

The Importance of the Org Chart Model

When we train people in the use of different requirements models, we typically mention three models as being distinct by virtue of the fact that you can know they are complete: 

Read More »
General

When is IT the business stakeholder?

We use a well established model for looking at the relationship between business requirements and the software requirements that are derived from them. Using the Requirements Object Model (ROM), we

Read More »
General

No field length guidelines

I found myself last year working on a UI heavy project, in which we were specifying detailed requirements associated with individual UI elements.  One of the elements that the customer

Read More »