Projects must be planned and executed to deliver timely, viable solutions that are both relevant and realistic. To meet these goals, every project must begin with an fully vetted and approved requirements specification. But, before project requirements can be vetted and approved, they must be collected, organized and transformed into an actionable project scope, vision and work effort. Read on for more.
IT projects are complex projects. Requirements are typically multi-faceted, covering technical, financial, and operational elements, and are also subject to perception, bias and stakeholder interests. As such, the requirements collection process must incorporate and address all these realities - to identify requirements at all levels and perceptions. This is best achieved through standardized steps, designed for consistency, but equipped with built-in flexibility.
Requirements collection is performed as part of the project definition process. For an illustrated view of project definition, see our informative infographic Defining Projects for Action and Approval.
The following techniques and strategies are used to "fast track" the requirements collection process so that project needs can be quickly identified and organized for analysis:
"Face to face" interviews with one or more project stakeholders. These "requirements" interviews can occur as one-on-one meetings or group brainstorming sessions. Tip: Interviews are most appropriate for projects with a small number of "requirements contributors", where requirements must be gathered from a select, concentrated group.
Documented questions (on paper or in electronic format) designed to collect "written" requirements feedback from one or more project stakeholders. Tip: Surveys are most appropriate for projects with a large number of "requirements contributors" where requirements must be gathered from a diverse group.
Direct "interaction" with project customers (i.e. end-users) to observe and identify requirements based on current workflows and practices. Tip: Observation is most appropriate for "performance or productivity improvement" projects where problems must be translated into actionable requirements.
In practical application, most projects will involve some combination of these various methods in order to collect a full set of useful requirements. Requirements collection is initiated when the project need is first identified and the project “solution” is to be proposed. Requirements refinement continues after the project is “selected” and as the scope is defined, aligned and approved. The requirements collection process must be designed to address the following primary issues:
Once requirements data has been collected, analyzed and finalized, validating deliverables must be produced, in order to document requirements for review and acceptance. This deliverable, formally known as a "Requirements Statement/Specification" must be prepared and approved before project work begins. It's very risky to initiate costly project work without a full understanding and an acceptance of properly stated requirements. The requirements deliverable also provides a baseline for managing inevitable project change.
About Us- ITtoolkit.com has been around since 2001. What will you find here? We have articles (covering a wide range of topics relating to our IT service strategy and project fast tracking methodologies). We have templates and whitepapers to download. We have our series of IT management infographics. And, we have our "Toolkit productivity packages", combining "education and execution" - with time-saving concepts, steps and templates packaged in digital downloads. Our current Toolkit offerings include the Fast Track Project Toolkit and IT Service Strategy Toolkit.
If you are, then you need the IT Service Strategy Toolkit from ITtoolkit.com! The Toolkit teaches you how to "add value" to IT projects and services -- using our time-saving "service strategy process". It's ready for instant download, filled with 400+ pages of steps, guidelines, practices and templates. Find Out More
Strategic fast tracking is a streamlined project management process, used to level the playing field when "project problems" get in the way of on-time success. Our informative "fast tracking" article series explains more:
Sign up for the ITtoolkit.com newsletter and be the first to know about our latest blog articles, templates, white papers, infographics, and special offers.
We won't overload your inbox and we don't share or sell subscriber information. Just enter your email address below.