Project Management

An iterative approach to project management and software development that focuses on collaboration, customer feedback, and small, rapid releases.

A temporary endeavor undertaken to create a unique product, service, or result with a defined beginning and end. Its boundaries are time, cost, and quality.

A group of related projects managed in a coordinated way to obtain benefits and control not available from managing them individually. It yields synergy.

A collection of projects, programs, and operations managed as a group to achieve strategic business objectives. It optimizes resource allocation.

The defined boundaries of a project, detailing all the work that must be done and everything that is excluded. It determines what the team commits to deliver.

A significant point or event in a project, used to measure progress toward the final goal. It has zero duration and marks a key achievement or decision point.

A relationship between two or more project tasks where the start or completion of one task relies on another. It determines the sequence work must follow.

A matrix used to clarify roles and responsibilities for project tasks, deliverables, or key decisions. Each task maps to exactly one Accountable person.

A horizontal bar chart that visualizes a project schedule, showing tasks, durations, dependencies, and milestones over time. Bars show start and end dates.

The longest sequence of dependent tasks that determines the minimum time required to complete a project. Any delay on this path directly delays the end date.

An uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives. Risks can be opportunities or threats.

A current problem or conflict that has already occurred and is affecting the project scope, budget, or timeline. Unlike a risk, it is happening right now.

An agile framework used to manage complex work, relying on small self-organizing teams, short iterations, and continuous feedback. Work is done in Sprints.

A visual workflow management method designed to help teams visualize work, limit work in progress, and maximize efficiency. WIP limits are its core constraint.

A timeboxed iteration of a consistent duration, typically one to four weeks, during which a Scrum team works to complete a set amount of work.

The total time that elapses from when a request is received to when it is fully delivered to the customer. It includes both waiting time and active work time.

The time it takes to complete a task from the moment active work on it actually begins. It excludes all time the task spent waiting in a backlog or queue.

A development principle stating that features should only be added when they are actually needed, rather than when they are anticipated. It prevents waste.