7 rules for effective requirement capture

It's one of the hardest parts of an IT development project and a major cause of project failure, so how should IT teams tackle requirements capture?

What's the secret that keeps the world's most innovative companies launching new products or services that consistently outperform rivals? According to analysts at consulting firm Booz & Company, it's the fact that companies such as Microsoft, Nokia and Pfizer are "good at the right things, not at everything."

One of the things that they’re particularly good at, they say, is requirements capture. Or, as Booz & Co analysts Barry Jaruzelski and Ken Dehoff put it in the company's 2010 Global Innovation 1000 study, these companies have "the ability to gain insights into customer needs and to understand the potential relevance of emerging technologies at the ideation stage." In other words, they work hard to understand what customers will expect a new product or service to do, before they create it.

You need to be a subscriber to read the rest of this article.

Already a subscriber? Sign in here