Best Practices

Don’t Listen to Your Customer’s Needs

Part 3 in the series, “How to Shoot Yourself in the Foot: 7 ways to do software requirements poorly to set your project up for failure and what to do instead.” Want to torpedo your project before it even leaves the dock? I can think of no better way than not …

Read More

Tips for Turning “Fluff” Requirements into Real Requirements

Tips for Turning “Fluff” Requirements into Real Requirements Lately I have been getting a lot of “fluff” requirements from my stakeholders… The system must be flexible.  The system must allow for multivariate (A/B) testing.   The system must be more user-friendly.   The features should be re-useable.   These all sound great in …

Read More

People Have Different Styles

Have you ever worked with that one person who just seemed difficult?  Perhaps you were in a working session to gather software requirements with a subject matter expert, and they just seemed to bug you.  Others may even mention how a certain person is “difficult”. Recently on a project, I’ve …

Read More

Must a Requirement be Feasible?

Within a discussion on the Seilevel message board about the characteristics of a good requirement, Elaine and Gescober discussed whether a requirement must be feasible in order to be a good requirement. While initially it looked like they had opposite opinions–Elaine: No, Gescober: Yes– they’ve seem to have come to …

Read More

Good Faith

Let’s say you take your car in to have it worked on and you get a $1000 estimate and are told you have to leave it for 2 days to get the repairs. It turns out that once the repair shop opens up the engine, they find out the cost …

Read More