The document outlines requirements, planning, project control, risk management, and personnel considerations for software development projects. It lists specific questions to evaluate whether a project has clear requirements, detailed planning, proper project control through milestones and change management, identified risks and risk management strategies, and an appropriate team with the necessary expertise. The document contains a total of 99 evaluation questions across these categories.

1. Requirements
Does project have a clear and unambiguous vision statement? 3
Do all team members believe the vision is realistic? 3
Does the project have a business case the details the business
benefit and how the benefit will be measured? 3
Does the project have a user interface prototype that realistically
and vividly demonstrates the functionality that the actual system
will have? 3
Does the project have a detailed, written specification of what the
software is supposed to do? 3
Did the project team interview people who will actually use the
software early in the project and continue to involve them in the
project? 3 18
Planning
Does the project have a detailed, written software development
plan? 3
Does the projects's task list include creation of an installation
program, conversion of data from previous versions of the system,
integration with third-party software, meeting with the customer,
and other "minor" tasks? 3
Were the schedule and budget estimates officially updated at the
end of the most recently completed phase? 3
Does the project have detailed, written architecture and design
documents? 3
Does the project have a detailed, written Quality Assurance Plan
that requires design and code reviews in addition to system
testing? 3
Does the project have a detailed staged Delivery Plan for the
software, which describes the stages in which the software will be
implemented and delivered? 3
Does the projects's plan include time for holidays, vacation days,
sick days, and ongoing training, and are resources allocated at
less than 100%? 3

2. Was the project plan, including the schedule, approved by the
development team, the quality assurance team, and the technical
writing team - in other words, the people responsible for doing the
work? 3 24
Project Control
Has a single key executive who has decision-making authority
been made responsible for the project, and does the project have
that person's active support? 3
Does the project manager's workload allow him or her to devote
an adequate amount of time to the project? 3
Does the project have well-defined, detailed milestones that are
considered to be either 100 percent done or 100 percent not
done? 3
Can a project stakeholder easily find out which of these binary
milestones have been completed? 3
Does the project have a feedback channel by which project
members can anonymously report problems to their own
managers and to upper managers? 3
Does the project have a written plan for controlling changes to the
software's specification? 3
Does the project have a change control board that has final
authority to accept or reject proposed changes? 3
Are planning materials and status information for the project -
including effort and schedule estimates, task assignments, and
progress compared to the plan thus far - available to every team
member? 3
Is all source code placed under automated revision control? 3
Does the project environment include the basic tools needed to
complete the project, including defect tracking software, source
code control, and project management software? 3 30
Risk Management
Does the project plan articulate a list of current risks to the
project? Has the list been updated recently? 3
Does the project have a project risk officer who is responsible for
identifying emerging risks to the project? 3

3. If the project uses subcontractors, does it have a plan for
managing each subcontractor organization and a single person in
charge of each one? 3 9
Personnel
Does the project team have all the technical expertise needed to
complete the project? 3
Does the project team have expertise with the business
environment in which the software will operate? 3
Does the project team have a technical leader capable of leading
the project succesfully? 3
Are there enough people to do all of the work required? 3
Does everyone work well together? 3
Is each person committed to the project? 3 18
Totals 99