5. Recommendations
Cut the initial
awareness meeting
down to a few select
individuals who can
more precisely identify
the technology impacts
for a specific project
Small
awareness
project
meeting
Responsible
list
Standardized
intake forms
Enforce
timeframe
commitment
Centralized
database for
project
managers
Maintain a list of individuals
responsible for assessing
impact to each area, so the
project manager does not
have to rely on asking co-
workers who to contact and
what the estimate intake
process is
Standardize the intake
forms to request the same
data for every IT area,
rather than different forms
with different data. Store
the project intake request
data in a centralized
location
Store project estimates
and assumptions for each
IT area in a centralized
location, which can be
accessed by project
managers and used to
more accurately estimate
future projects
Create and
enforce
timeframes for
returning
estimates to
project managers
12. Queries
• For open projects, which application
owners have not submitted estimates?
• For a given project, how many application
owners are impacted?
• How many days on average, maximum,
and minimum is it taking to get estimates
for a specific project?
14. Queries
• Which of the IT departments is impacting
the project the most in terms of volume or
dollar amount?
• For a given business sponsor, which
senior leaders are they interacting with for
all their projects?
• How many of each project type are there,
ordered from highest to lowest?