INFO 210

Quantifiable criteria that must be met for the project to be considered a success

A formal, approved document that manages and controls project execution

Links the project to the organization's overall business goals

Individuals and organizations actively involved in the project or whose interests might be affected as a result of project execution or project completion

A smaller-scale representation or working model of the users' requirements or the proposed design for an information system

Emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system, to accelerate the systems development process

Provides a framework for breaking down the development of software into four "gates"

Uses small teams to produce small pieces of software using a series of "sprints," or 30-day intervals, to achieve an appointed goal

The overall process for developing information systems, from planning and analysis through implementation and maintenance

Brings all the project pieces together into a special testing environment to eliminate errors and bugs, and verify that the system meets all the business requirements defined in the analysis phase

A sequence of phases in which the output of each phase becomes the input for the next