Chapter 9

agile methodology

aims for customer satisfaction through early and continuous delivery of useful software components developed by an iterative process using the bare minimum requirements

analysis phase

the firm analyzes its end-user business requirements and refines project goals into defined functions and operations of the intended system

business requirement

the specific business requests the system must meet to be successful

change control board (CCB)

responsible for approving or rejecting all change requests

change management

offers procedures and policies managers can use to help manage change during system development

change management system

includes a collection of procedures to document a change request and identifies the expected impact associated with the change

critical path

estimates the shortest path through the project ensuring all critical tasks are completed from start to finish

dependency

a logical relationship that exists between the project tasks, or between a project task and a milestone

design phase

establishes descriptions of the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other documentation

development phase

takes all the detailed design documents from the design phase and transforms them into the actual system

executive sponsor

the person or group who provides the financial resources for the project

extreme programming (XP) methodology

breaks a project into 4 phases, and developers cannot continue to the next phases until the previous phase is complete

Gantt chart

a simple bar chart that lists project tasks vertically against the project's time frame, listed horizontally

implementation phase

the organization places the system into production so users can begin to perform actual business operations with it

in-sourcing (in-house development)

uses the professional expertise within an organization to develop and maintain its information technology systems

iterative development

consists of a series of tiny projects

kill switch

a trigger that enables a project manager to close the project before completion

maintenance phase

the organization performs changes, corrections, additions, and upgrades, to ensure the system continues to meet its business goals

methodology

a set of policies, procedures, standards, processes, practices, tools, techniques, and tasks that people apply to technical and management challenges

nearshore outsourcing

contracting an outsourcing arrangement with a company in a nearby country

offshore outsourcing

using organizations from developing from developing countries to write code and develop systems

onshore outsourcing

engaging another company within the same country for services

outsourcing

an arrangement by which one organization provides a service or services for another organization that chooses not to perform them in-house

PERT (Program Evaluation and Review Technique) chart

a graphical network model that depicts a project's tasks and the relationships between them

planning phase

establishes a high-level plan of the inteded project and determines project goals

project

temporary activity a company undertakes to creat a unique product, service, or result

project assumption

factors considered to be true, real, or certain without proof or demonstration

project charter

a document issued by the project initiator or sponsor that formally authorizes the start of a project and provides the project manger with the authority to apply organizational resources to project activities

project constraint

speicific factors that can limit options

project deliverable

any measurable, tangible, verifiable outcome, result, or item that is produced to complete a project or part of a project

project management

the application of knowledge, skills, tools and techniques to project activities to meet project requirements

project management institute (PMI)

develops procedures and concepts necessary to support the profession of the project management

project management office (PMO)

an internal department that oversees all organizational projects

project manager

an individual who is an expert in project planning and management, defines and develops the project plan, and tracks the plan to ensure the project is completed on time and on budget

project milestones

represent key dates when a certain group of activites must be performed

project objective

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

project plan

a formal, approved document that manages and controls project execution

project scope statement

links the project to the organization's overall business goals

project stakeholder

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

prototype

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

rapid application development (RAD) methodology (also called rapid prototyping)

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

rational unified process (RUP) methodology

provides a framework for breaking down the development of software into 4 "gates

scrum methodology

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

systems development life cycle (SDLC)

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

testing phase

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

waterfall methodology

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