The Complete Software Project Manager

Glossary

Agile methodology:

A method of developing software with limited up-front definition and budgeting; the Agile process values constant collaboration, frequent deliverables, and continuous evolution of requirements.

Alpha:

The first view of a piece of software; software is able to be reviewed and initial testing begun.

Architect:

The person responsible for the choice, organization, setup, and configuration of the hardware that will run the software

Back-end programmer:

The person who programs databases and system integrations

Beta:

The second phase of software delivery; all features are complete and the software is ready for comprehensive testing and debugging.

Blended budgeting:

The process of using two or more budgeting methods to estimate a project

Blue sky:

Brainstorming about possible solutions and strategies

Bottom-up budgeting:

The process of using a detailed task list of which the project is comprised and estimating costs based on that list; the total budget is a sum of individual costs.

Budgeting:

The process of estimating costs for a project

Business analyst:

The business analyst (BA) is the person who collects, digests, and codifies all the software development requirements from the business stakeholders.

Business case:

A high-level statement of the project's purpose, including return on investment (ROI); the business case identifies how the project will benefit the business, often through potential profits, cost savings, and/or competitive advantages gained ...