Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
The Requirements Question
Frank Winters has more than 30 years of consulting and Information Technology experience serving as a project/program manager, consultant and IT service industry executive.
Recently there has been some discussion about who should gather and document requirements during the systems development lifecycle. Should program or project managers do it, or does it require specialists? My answer was it should be a specialist or team of specialists because it’s extremely important to set the appropriate expectations early in the process. In my view, gathering and documenting requirements is a highly specialized, full-time job.
Strategy is Used to Measure Adequacy of Requirements
Michael Wood recently posted a response saying, “Developing requirements begins with clear, quantified objectives that are aligned with the strategic direction of the company.” Very true, and in today’s business environment, very difficult to achieve because strategy itself has become troublesome for some companies to articulate. Systems people have traditionally turned to business managers for business strategy. Recently, business people have turned the tables asking IT people for help with strategy. This is because for most businesses today, strategic decisions are related to electronic commerce and channel integration, and most people are unsure about how to take advantage of the related opportunities. Trouble is, the IT folks are not usually in any better position to develop the needed strategies. In some industries the fundamental …
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
I'm a great quitter. I come from a long line of quitters. I was raised to give up. - George Costanza |