Developing Software Requirements

By Christopher Hawkins •  Updated: 06/03/23 •  1 min read

You spend countless hours asking ever-more-specific questions of your client, in a process that feels like you’re pulling teeth. Finally, certain that you understand the project, you cobble together a set of project requirements and show them to the client, only to be told “no, that’s not right at all”.

What went wrong? The same thing that happens to 67% of all projects – you and your client allowed confusion to exist between you, and the project requirements suffered as a result. It happens every day to consultants just like you and I, and it feels awful.

The good new is, there is a clear and simple combination of habits that will help you create clear, testable, client-focused requirements that keep the profit in your project!