Request Analysis Questionnaire

Project Request Process Overview

o Describe the process and flow
o Clearly point out critical areas of the process, including all approval
gates
o Discuss Customer role and tasks they should expect
o Project Process – see PMO for documentation
o Change Management – see Change Board for documentation
o Describe IT Governance Guidelines/Requirements

 Provide Request Process Handout

Issue/Problem Statement (What and Why?)

o Issue / Problem Statement (Why?)
Additional questions:
 Causes of the problem
 Factors that make the problem worse or better
 How does the problem affect the customer’s goals
 How does the problem impact the clients of the customer
 the stake or importance that the customer holds in an
acceptable solution to the problem
 How does the issue affect ongoing operations
o Business Needs Assessment (High-level key facts and figures)
o Approach and Objectives (How do you see the problem being
resolved?) Note: Objectives should be, Specific,
Measurable, Verifiable, Feasible, and within a defined Time period.
Additional questions:
 What does it look like?
 What are the intended benefits?
♦ Reallocated personnel
♦ Decrease Cost of Lease, Rental, Maintenance
♦ Support Services
♦ Training
♦ Supplies and Utilities
♦ Security
♦ Reduced Staff Time
♦ Reduced Error Rates
♦ Expanded Capacity or Capability
♦ Data Storage and Retrieval
♦ Electronic Performance Reporting
♦ Centralized or Distributed Processing
♦ Reduced Error Rates
 ♦ Improved Timeliness
♦ Better Quality Products
♦ Eliminate Future FTE Expansion
♦ Eliminate Additional Equipment Requirements
♦ Increased Productivity
♦ Other

o Strategic Alignment (How does this initiative fit into the strategic goals
of the organization, and areas associated to the requesting area?)

 Enter Request

Demographics (Where and Who?)

o Organization
o Physical Location – Facility/Building
o Department(s)
o End-Users, and associated Stakeholders
Additional questions:
 Who knows about this request, or is included in this request?
 Who doesn’t know about it and should?

System/Process
o Current Process
o Associated Policies
o Inputs/Outputs – Staff, Interfaces, Print Jobs, Reports, Access Points,
Peripherals, System Interactions, etc.
o Technical Architecture – Ex. Server
Additional questions:
 What has been done thus far?
 What products, vendors, methods, other, has been identified
thus far?
 What are the top three?

Work Effort/Resources
o Estimate the resource type and amount
o Estimate schedule constraints
o Estimate dollars (Rough Order of Magnitude – ROM)
o Hardware
o Software
o Licenses
o Training
o Documentation
o On-going Maintenance and Support
 o Identify SME’s
o Documentation

 Create initial estimate of Project Size and Complexity

 TCO Estimate
 ROI - Estimate

Assumptions
o Facility availability

Constraints
o Infrastructure
o HIPAA
o JACHO
o Security
o Other

Communication
o How will they obtain/receive communications?
o Who on their team is the primary contact?
o How often will you provide written and/or oral update?
o Does the customer have a specific format they require, or media, they
require?
o Who makes the go/no-go decisions, including changes in project scope
or requirements?
o Does the customer know of, or expect particular development
methodology or standards to be followed?

Security
o Disaster Recover Requirements
o Protected Health Information
o Sensitive/Confidential Business Information

Network
o New area requiring data drops
o Network expansion
o Remote access
 Complete Project/Capital Review
 Create Initial Work Breakdown Structure (WBS)
 Complete Request For Information (RFI)