Project Manager's Toolkit: Practical Checklists for Systems Development

Type: To do
Use this checklist (and the checklists underlying this checklist) to plan how to attack a business analysis project.
Identify the business process for analysis see checklist 3.1 Nine key questions for high-level business understanding .
Identify the goal of the business analysis see checklist 3.3 Fourteen common business problems spotting which ones are yours .
List the types of information required:
what data do we need?
why do we need it?
when do we need it (what step in the investigation)?
what filters will we apply to screen out unneeded data (not all information is worth collecting)?
List the sources of information required:
Some possible sources are:
strategy, policy and planning documentation
organizational chart
process actors themselves (including who they call, email, memo and who calls/ emails/memos them)
process actors in-tray , out-tray , pending tray
document distribution lists
documented procedures and standards
job descriptions
quality manuals
existing systems documentation.
List the mix of people/user to involve/interview a matrix of:
level of involvement in the process:
dedicated does the process everyday
casual does the process on an ad-hoc basis
QA/authorizers
performance monitors (e.g. supervisor, accounts, personnel)
level of system use:
expert full understanding of entire application
capable full understanding of business process in application
simple understands only their screen/report-set
simple report/query only
MIS complex query possibly...