Aims for customer satisfaction through early and continuous delivery of useful software components developed by an iterative process using the bare minimum requirements
Agile Methodology
The firm analyzes its end user business requirements and refines project goals into defined functions and operations of the intended system
Analysis Phase
The specific business requests the system must meet to be successful
Business Requirement
Responsible for approving or rejecting all change requests
Change Control Board (CCB)
Offers procedures and policies managers can use to help manage change during system development
Change Management
Includes a collection of procedures to document a change request and identifies the expected impact associated with the change
Change Management System
Estimates the shortest path through the project ensuring all critical tasks are completed from start to finish
Critical Path
A logical relationship that exists between the project tasks, or between a project task and a milestone
Dependency
Establishes descriptions of the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other documentation
Design Phase
Takes all the detailed design documents from the design phase and transforms them into the actual system
Development Phase
The person or group who provides the financial resources for the project
Executive Sponsor
Breaks a project into four phases, and developers cannot continue to the next phase until the previous phase is complete