PM Software Glossary — Key Terms & Definitions for Project Management

A–B C–D E–F G–H I–K L–N O–P R–S T–Z

A B C D E F G H I J K L M N O P R S T U V W

A – B

Agile Methodology: An iterative approach to project management where work is delivered in small increments called sprints. Teams adapt to changing requirements throughout the project rather than following a rigid upfront plan. Common frameworks include Scrum, Kanban, and XP (Extreme Programming).
Artifact General: Any tangible or digital output produced during a project — a document, a design mockup, a code module, a deliverable. In PM software, artifacts are often attached to tasks or projects as reference materials.
Backlog Methodology: A prioritized list of tasks, features, or requirements that need to be completed. The product backlog contains all work items for a product; the sprint backlog contains items selected for the current sprint. Backlogs should be regularly groomed (reviewed and reprioritized).
Baseline Metric: The approved version of a project plan — scope, schedule, and budget — used as a reference point to measure actual progress. When actual results deviate from the baseline, project managers can identify variances and take corrective action.
Board (Kanban Board) Feature: A visual workspace with columns representing workflow stages (e.g., To Do, In Progress, Done). Tasks move from left to right as they progress. Most PM tools offer a board view alongside list and timeline views.
Burndown Chart Metric: A graphical representation showing the amount of work remaining in a sprint or project against time. The ideal burndown line is diagonal from top-left to bottom-right. When actual work remaining stays above the line, the team is behind schedule.
Business Case General: A document that justifies the investment in a project by outlining expected benefits, costs, risks, and alternatives. Used to secure stakeholder approval before a project begins.

C – D

Change Request General: A formal proposal to modify the project scope, timeline, or budget. All scope changes should go through a change request process to assess impact and obtain approval before implementation.
Critical Path Metric: The longest sequence of dependent tasks that determines the minimum time needed to complete a project. Tasks on the critical path have zero float (they cannot be delayed without delaying the entire project). Identifying the critical path helps prioritize where to focus resources.
Dependency General: A relationship where one task cannot start or finish until another task is complete. Common types: Finish-to-Start (Task B starts after Task A finishes), Start-to-Start (both tasks begin together), and Finish-to-Finish (both tasks end together).
Deliverable General: A tangible or measurable outcome that must be produced to complete a project or phase. Deliverables can be internal (for the team) or external (for the client). Each deliverable should be clearly defined with acceptance criteria.
Dependency General: The relationship between tasks where one task depends on another being completed first. PM software can track dependencies automatically and warn you when scheduling conflicts arise.
Disk / Milestone Feature: A significant point or event in a project schedule — a major deliverable completion, a review gate, or a deadline. Milestones mark progress checkpoints and are typically zero-duration markers on a project timeline.

E – F

Epic Methodology: A large body of work that can be broken down into smaller user stories or tasks. Epics are typically used in Agile contexts to organize related work under a single theme. Example epic: "Redesign the customer checkout flow" containing 12 specific user stories.
Estimate General: An approximation of the time, cost, or resources required to complete a task or project. Estimates should always include a confidence range (e.g., "3–5 days") rather than a single number. Accuracy improves with historical data from past projects.
Float (Slack) Metric: The amount of time a task can be delayed without delaying the project deadline or dependent tasks. Tasks with zero float are on the critical path. PM software can calculate float automatically once dependencies are defined.
Free Tier Feature: A no-cost subscription level offered by many PM tools. Free tiers typically limit the number of users, projects, or storage. Useful for evaluation and for very small teams, but usually insufficient for growing organizations.

G – H

Gantt Chart Feature: A bar chart that illustrates a project schedule — tasks are listed on the vertical axis, time on the horizontal axis, and bars represent task duration. Gantt charts show task dependencies, milestones, and the critical path. Available in most mid-to-enterprise PM tools.
Goal (OKR) General: A measurable objective that a project or team aims to achieve. Objectives and Key Results (OKRs) are a popular goal-setting framework used alongside PM software: an Objective states the goal, Key Results define how to measure achievement.
Grooming (Backlog Refinement) Methodology: The practice of regularly reviewing, updating, and prioritizing the product backlog. The team ensures backlog items are well-defined, estimated, and prioritized. Typically done weekly or at the start of each sprint planning session.

I – K

Integration Feature: The ability of a PM tool to connect with other software (Slack, Google Workspace, GitHub, CRM systems). Native integrations are built into the PM tool; third-party integrations connect through platforms like Zapier or native APIs. Integration quality varies significantly between tools.
Issue Log General: A record of all problems, risks, or blockers encountered during a project. Unlike a task list (what needs to be done), an issue log tracks current problems that need resolution. PM tools often have dedicated issue or risk tracking modules.
Kanban Methodology: A visual workflow management method that helps teams visualize work, limit work-in-progress (WIP), and maximize efficiency. Unlike Scrum's fixed sprints, Kanban is continuous — tasks flow through columns as capacity allows. Suitable for operational work and support teams.
Kickoff Meeting General: The first meeting held after a project is approved, bringing together the project team and stakeholders to align on goals, roles, communication plans, and initial schedule. Sets the tone for the project and ensures everyone starts with the same understanding.

L – N

Lead Time Metric: The total time from when a task is created until it's completed. Unlike cycle time (which measures only active work), lead time includes time spent waiting in the backlog. Shorter lead times generally indicate a healthier workflow.
Milestone General: A significant checkpoint in a project — a deliverable completion, a review gate, or an external deadline. Milestones are zero-duration markers on the timeline and are used to track progress against major goals.
Non-Functional Requirement General: A quality attribute that a product or system must have — performance, security, scalability, usability, or reliability. Non-functional requirements are often overlooked but critical for enterprise adoption of PM tools.

O – P

Onboarding (PM Tool) Feature: The process of training team members to use a new PM tool effectively. Good onboarding covers: basic navigation, how to create and assign tasks, how to use board/list views, and how to integrate with existing workflows. Tool complexity varies significantly — some tools require weeks of training.
Per-User Pricing Feature: A subscription model where the cost is calculated based on the number of users accessing the tool. Per-user pricing is standard for most PM SaaS tools. Enterprise tiers often offer unlimited users at a flat rate, making them more economical for large teams.
Priority General: A rating that indicates the importance or urgency of a task relative to other work. Common priority levels: Critical, High, Medium, Low. PM tools often use a numeric scale or color-coded labels. Prioritization should be collaborative — agreed upon by the team, not dictated unilaterally.
Project Charter General: A formal document that authorizes the existence of a project and provides the project manager with authority to apply organizational resources. Includes project purpose, objectives, key stakeholders, budget summary, and success criteria.

R – S

Release Methodology: A deployment of completed features to users. In Agile, releases may contain multiple sprints of work. PM software with release management features allows teams to bundle related tasks into a single deployment unit.
Report (PM) Feature: Formatted output from PM software that summarizes project data — task completion rates, time tracking summaries, workload distribution, and project health. Reporting depth varies widely: basic tools offer simple charts, enterprise tools offer customizable dashboards and data exports.
Resource Allocation Feature: The process of assigning team members, equipment, and budget to specific tasks. PM software with resource management features shows who is over- or under-utilized and helps balance workloads across the team.
Retrospective Methodology: A meeting held at the end of a sprint or project phase where the team reflects on what went well, what didn't, and how to improve. A key Agile ceremony. Retrospectives build continuous improvement into the team culture and are one of the highest-value Agile practices.
Risk Register General: A document listing identified risks, their likelihood and impact, and planned responses. PM software often includes risk tracking modules or allows teams to build risk registers as a custom project artifact.
Scope Creep General: Uncontrolled expansion of project requirements beyond the original agreed scope, often caused by unclear requirements, stakeholder pressure, or inadequate change control. The most common cause of project overruns. Managed through formal change request processes.
Sprint Methodology: A fixed time period (typically 1-4 weeks) during which a specific set of work must be completed and ready for review. Scrum uses sprints as its core cadence; each sprint starts with planning and ends with a review and retrospective.
Standup (Daily Standup Meeting) Methodology: A brief daily meeting (usually 15 minutes or less) where team members share: what they did yesterday, what they plan to do today, and any blockers. Originally from Scrum, now widely adopted across all project management styles as a lightweight coordination mechanism.

T – Z

Task General: The fundamental unit of work in project management. A task has a description, assignee, due date, priority, and status. Tasks can be organized hierarchically (subtasks, parent tasks) and linked via dependencies. Most PM tools allow tasks to include attachments, comments, and custom fields.
Time Tracking Feature: A feature that records time spent on tasks. Built-in time tracking captures hours directly within the PM tool; external time tracking uses integrations with dedicated tools. Time tracking data supports billing, capacity planning, and process improvement.
Timeline Feature: A visual representation of project tasks plotted against time — the digital equivalent of a Gantt chart. Most modern PM tools offer a timeline view (sometimes called a Gantt view) that shows task durations, dependencies, and milestones.
Velocity Metric: A measure of how much work a team can complete in a single sprint, typically measured in story points or ideal hours. Velocity is calculated by summing the completed story points from past sprints. Used to forecast future sprint capacity and project completion dates.
Waterfall Methodology: A sequential project management methodology where each phase (requirements, design, implementation, testing, deployment) must be completed before the next begins. Linear and structured — best suited for projects with fixed requirements and regulatory compliance needs.
WIP Limit (Work in Progress) Methodology: A constraint on the number of tasks allowed in a particular workflow stage at any given time. WIP limits are a core Kanban practice that prevents overloading team members and highlights bottlenecks. When a column is full, the team finishes existing work before pulling in new tasks.
Workload View Feature: A PM feature that shows how much work each team member has assigned over a given period. Helps managers identify overloaded team members and rebalance assignments before burnout occurs. Most useful for teams of 10 or more.

Disclaimer: This glossary provides general educational definitions of project management terminology. We are not affiliated with any PM software vendor. Term usage may vary between tools and methodologies.