Software project management

creation and maintaining of programs and applications

group of iterative and incremental development methods

Agile software development framework

new program, and line of software development, derived from an existing one

list of actions or event steps typically defining the interactions between a user role and a system to achieve a goal

Phabricator is a free and open source suite of web-based development collaboration tools.

UML use case diagram

process by which software is developed

concept of software development

thumb|420px|The V-model of the systems engineering process.

process of planning and controlling a software build through different stages and environments, including testing and deployment

types of methodologies to develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental), allowing developers to take advantage of what was learned during development of earlier parts or versions of the system

observation that organizations design systems mirroring their communication structures (Melvin Conway, 1968)

iterative and incremental (agile) software development process aiming to deliver tangible, working software with client-valued functionality in a timely manner

1975 non-fiction work by Fred Brooks

principle in software development that, past some point, assigning more people to a software project ends up delaying it

technique for estimating

art and science of planning and leading software projects

humorous aphorism in computer programming

concept in software development

American computer scientist

product management of computer programs throughout their development lifecycles

In agile principles, timeboxing allocates a maximum unit of time to an activity, called a timebox, within which a planned activity takes place. It is used by agile principles-based project management approaches and for personal time management.

prioritization technique for a common understanding of the importance of the delivery of each requirement

1986 essay by Frederick Brooks distinguishing essential complexity from accidental complexity in software engineering

excessive ongoing expansion or addition of new precluded features in a product, especially in computer software, video games and consumer and business electronics

software development process applying manufacturing techniques and principles to to mimic the benefits of traditional manufacturing

in software engineering, development phase during which policy restricts making changes to the system

term

set of organization and workflow patterns intended to guide enterprises in scaling lean and agile practices

a sub-discipline of requirements management within software development and systems engineering

tools used to make software

Process of predicting the amount of effort required to develop or maintain a software

process used to ensure that changes to a product or system are introduced in a controlled and coordinated manner, minimizing the possibility of incurring unnecessary changes without forethought or introducing faults into the system

Peopleware can refer to anything that has to do with the role of people in the development or use of computer software and hardware systems, including such issues as developer productivity, teamwork, group dynamics, the psychology of programming, project management, organizational factors, human interface design and human–machine interaction.

poor practice in project management

agreed description in configuration management of the attributes of a product, at a point in time, which serves as a basis for defining change

use of open source software development best practices and open source-like culture

project management term