Projects & Business Analysis terms
199 Projects & Business Analysis terms explained in plain English.
- Acceptance CriteriaAcceptance Criteria is the specific conditions a deliverable must meet to be accepted by the business or customer.
- Acceptance Test ScenarioAcceptance Test Scenario is a business-focused scenario used to check whether a requirement or solution works in practice.
- Action ItemAction Item is a specific task assigned to someone with an expected outcome or due date.
- Adoption MetricAdoption Metric is a measure used to show whether people are actually using and embedding a change.
- Agile (Methodology)Agile is a way of working where teams build things in small steps rather than trying to plan everything upfront.
- API ContractAPI Contract is the agreed definition of an API's endpoints, requests, responses, and rules.
- Architecture Review Board (ARB)Architecture Review Board (ARB) is a governance forum that reviews solution architecture for alignment, risk, and strategic fit.
- AssumptionAssumption is something a team believes to be true for planning purposes even though it is not yet confirmed.
- AssuranceAssurance is independent or semi-independent checking that work is being managed and controlled appropriately.
- Audit TrailAudit Trail is a record showing what changed, who changed it, and when it happened.
- BacklogBacklog is a prioritised list of work items, improvements, defects, and ideas.
- Backlog RefinementBacklog Refinement is the ongoing activity of clarifying, splitting, and preparing backlog items for future delivery.
- BaselineBaseline is the approved reference version of scope, schedule, cost, or another plan component.
- Benefits Dependency NetworkBenefits Dependency Network is a map showing how enabling changes, business changes, and outcomes connect to expected benefits.
- Benefits MapBenefits Map is a visual view showing how project outputs are expected to lead to business outcomes and benefits.
- Benefits RealisationBenefits Realisation is the practice of tracking whether expected business benefits actually happen after change is delivered.
- BPMNBPMN is a standard notation used to model business processes with consistent diagram symbols.
- Budget VarianceBudget Variance is a measure showing how far actual spending differs from the approved budget.
- Burndown ChartBurndown Chart is a chart showing how much work remains over time during a sprint or release.
- Burnup ChartBurnup Chart is a chart showing completed work against the total scope over time.
- Business AnalystBusiness Analyst is a professional who turns business needs into clear requirements, models, and decisions.
- Business CapabilityBusiness Capability is a business ability the organisation needs in order to achieve an outcome.
- Business CaseBusiness Case is a structured justification for investing time, money, and effort in a proposed change.
- Business OwnerBusiness Owner is the person accountable for the business outcome and ongoing ownership of a process, service, or capability.
- Business RequirementBusiness Requirement is a statement of the business need or outcome that a change must achieve.
- Business Requirements Document (BRD)Business Requirements Document (BRD) is a document describing the business problem, objectives, scope, and high-level requirements for a change.
- Business RuleBusiness Rule is a policy, calculation, condition, or constraint that the business expects work or systems to follow.
- Canonical Data ModelCanonical Data Model is a common data structure used to standardise data exchanged across multiple systems.
- Capacity PlanningCapacity Planning is the practice of checking whether available people or systems can handle expected demand.
- Change Advisory Board (CAB)Change Advisory Board (CAB) is a group that reviews significant proposed changes before they are implemented in live environments.
- Change ControlChange Control is the method used to review, approve, reject, and track proposed changes.
- Change Management (Tech Projects)Change management in technology projects is about helping people adapt to new systems and ways of working.
- Change RequestChange Request is a formal proposal to alter agreed scope, design, timeline, cost, or another baseline.
- Communications PlanCommunications Plan is a plan describing what messages need to be shared, with whom, when, and by which channel.
- ConstraintConstraint is a fixed limit that restricts what choices a project or team can make.
- Context DiagramContext Diagram is a simple diagram showing a system and the external actors or systems that interact with it.
- Contingency PlanContingency Plan is a backup plan describing what to do if a significant risk or disruption happens.
- Cost Benefit AnalysisCost Benefit Analysis is a structured comparison of expected costs and expected benefits.
- Critical PathCritical Path is the longest sequence of dependent tasks that determines the shortest possible project duration.
- Cross-Functional TeamCross-Functional Team is a team that brings together different skills needed to deliver work end to end.
- CRUD MatrixCRUD Matrix is a matrix showing which roles, processes, or systems create, read, update, or delete each data entity.
- Cumulative Flow DiagramCumulative Flow Diagram is a chart showing work accumulation across workflow stages over time.
- Current Operating ModelCurrent Operating Model is the present-day operating model for how a business capability or service currently works.
- Current State (As-Is)Current State (As-Is) is a description of how work, systems, or data operate today.
- Customer Journey MapCustomer Journey Map is a visual story showing a user's steps, feelings, and pain points across an experience.
- CutoverCutover is the set of activities that switch operations from an old state to a new live state.
- Cutover ChecklistCutover Checklist is the detailed list of checks and tasks used during a cutover.
- Cycle TimeCycle Time is the time taken from starting work on an item to finishing it.
- Daily StandupA daily standup (also called a daily scrum in the Scrum framework) is a short daily team meeting designed to coordinate work and surface blockers.
- Data CleansingData Cleansing is the process of fixing, standardising, or removing poor-quality data.
- Data DictionaryData Dictionary is a reference list that defines data fields, meanings, formats, and allowed values.
- Data LineageData Lineage is the trace of where data comes from, how it changes, and where it goes.
- Data MappingData Mapping is the act of linking data from one source, format, or structure to another.
- Data MigrationData Migration is the movement of data from one system, structure, or environment to another.
- Data ModelData Model is a structured representation of data entities, attributes, and relationships.
- Decision GateDecision Gate is a formal point where a key project or programme decision must be made before progress continues.
- Decision LogDecision Log is a record of key decisions, why they were made, and who made them.
- DefectDefect is a flaw in a product, process, or configuration that causes incorrect behaviour.
- Definition of DoneDefinition of Done is an agreed checklist describing what must be true before work is considered complete.
- Definition of ReadyDefinition of Ready is an agreed checklist describing when an item is ready to be taken into delivery.
- DeliverableDeliverable is a defined output that a project or team is expected to produce.
- DependencyDependency is a relationship where one task, team, system, or decision relies on another.
- Dependency MappingDependency Mapping is the activity of identifying and visualising dependencies across work, teams, systems, or decisions.
- Design AuthorityDesign Authority is a governance group or role that reviews whether designs align with agreed principles and standards.
- Discovery PhaseDiscovery Phase is an early project stage focused on understanding needs, constraints, users, and options before delivery begins.
- EnablerEnabler is work that supports future delivery such as architecture, infrastructure, or technical preparation.
- Entity Relationship Diagram (ERD)Entity Relationship Diagram (ERD) is a diagram showing data entities and how they relate to each other.
- EpicEpic is a large body of work that is too broad to deliver in one small piece.
- EscalationEscalation is the act of raising a risk, issue, or decision to a higher level when normal handling is not enough.
- EstimationEstimation is the practice of forecasting the likely effort, time, or size of a piece of work.
- Exception ReportException Report is a report explaining where agreed tolerances or expectations have been exceeded and what decision is needed.
- Feasibility StudyFeasibility Study is an assessment of whether a proposed idea is realistic and worthwhile.
- FeatureFeature is a noticeable piece of capability that delivers value to users or the business.
- Functional RequirementFunctional Requirement is a statement describing what a system, process, or product must do.
- Functional Requirements Document (FRD)Functional Requirements Document (FRD) is a document describing the functions and behaviours a solution must provide.
- Future State (To-Be)Future State (To-Be) is a description of how work, systems, or data should operate after change is delivered.
- Gantt ChartGantt Chart is a timeline chart showing tasks, dates, durations, and dependencies.
- Gap AnalysisGap Analysis is a comparison between the current state and the future state a team wants to reach.
- Go LiveGo live is the moment when a new system, application, or feature is officially switched on and made available to real users.
- GovernanceGovernance is the framework of decision rights, controls, reporting, and oversight around work.
- Governance FrameworkGovernance Framework is the structure of decision rights, controls, forums, tolerances, and reporting around delivery.
- HandoverHandover is the transfer of responsibility from one person, team, or phase to another.
- Highlight ReportHighlight Report is a short summary report showing progress, status, risks, and decisions for a project or programme.
- HypercareHypercare is a short period of heightened support immediately after go-live.
- ImpedimentImpediment is anything slowing or blocking a team's ability to deliver effectively.
- IncrementIncrement is the usable outcome produced by one or more completed backlog items.
- Interface SpecificationInterface Specification is a detailed description of how two systems exchange data or interact.
- IssueIssue is a problem that already exists and needs action or a decision.
- KanbanKanban is a flow-based method that visualises work and limits how much is in progress at one time.
- Knowledge Transfer (KT)Knowledge Transfer (KT) is the structured sharing of know-how so another person or team can support or continue the work.
- KPI (Key Performance Indicator) in TechKPI stands for Key Performance Indicator.
- Lead TimeLead Time is the total time from request to delivery for a piece of work.
- Lessons LearnedLessons Learned is captured reflections on what worked, what did not, and what should change next time.
- Master DataMaster Data is core business data shared across processes and systems, such as customers, products, or locations.
- Meeting MinutesMeeting Minutes is a written record of what was discussed, agreed, and assigned in a meeting.
- MilestoneMilestone is a significant point in time used to show progress or readiness in a plan.
- Minimum Viable Product (MVP)Minimum Viable Product (MVP) is the smallest usable version of a product or service that can test value with real users.
- MoSCoW PrioritisationMoSCoW Prioritisation is a prioritisation method that sorts work into must have, should have, could have, and will not have now.
- Non-Functional RequirementNon-Functional Requirement is a statement describing how well a system or process must perform.
- Objective and Key Results (OKR)Objective and Key Results (OKR) is a framework for setting a clear objective and measurable results that indicate progress toward it.
- Operating ModelOperating Model is the way an organisation organises people, process, technology, and controls to deliver a capability or service.
- Operational ReadinessOperational Readiness is the state of being ready to operate, support, and govern a change in live use.
- OutcomeOutcome is the change in behaviour, performance, or value achieved because work was delivered.
- OutputOutput is the tangible thing produced by a project, team, or activity.
- PersonaPersona is a realistic profile representing a user group with shared goals, needs, and behaviours.
- PI PlanningPI Planning is the event where teams plan work together for an upcoming program increment.
- PilotPilot is a limited real-world rollout used to test a change with a small group before wider release.
- PMOPMO is a project management office that supports standards, reporting, governance, and delivery oversight.
- PortfolioPortfolio is the full collection of projects, programmes, and change investments managed together.
- Portfolio ManagementPortfolio Management is the practice of selecting, governing, and balancing change investments across an organisation.
- Post-Implementation Review (PIR)Post-Implementation Review (PIR) is a review carried out after implementation to assess results, issues, and lessons.
- PrioritisationPrioritisation is the act of deciding what should be done first based on value, urgency, effort, or risk.
- Process FlowProcess Flow is a visual map showing the steps, decisions, and handoffs in a process.
- Product Backlog Item (PBI)Product Backlog Item (PBI) is a single item of work recorded in the product backlog.
- Product ManagerProduct Manager is the role responsible for product direction, market fit, and value over a longer horizon.
- Product OwnerProduct Owner is the role responsible for maximising product value by prioritising work and clarifying what should be built next.
- Program Increment (PI)Program Increment (PI) is a larger planning and delivery window used by some scaled Agile approaches.
- ProgrammeProgramme is a coordinated group of related projects and change activities managed together.
- Programme ManagementProgramme Management is the coordination of related projects and change activity to deliver a larger strategic outcome.
- ProjectProject is a temporary piece of work created to deliver a defined outcome within agreed constraints.
- Project CharterProject Charter is a document that formally starts a project and summarises its purpose, scope, authority, and key assumptions.
- Project Initiation Document (PID)Project Initiation Document (PID) is a formal document describing how a project will be controlled, delivered, and governed.
- Project ManagerProject Manager is a professional who plans, coordinates, and tracks work so a project reaches its agreed outcome.
- Project SponsorProject Sponsor is the senior person who champions a project and is accountable for its business outcome.
- Proof of Concept (PoC)Proof of Concept (PoC) is a small experiment used to show that a concept or approach can work.
- PrototypePrototype is a model or mock-up used to explore, test, or demonstrate an idea before full build.
- RACI MatrixRACI Matrix is a responsibility model showing who is responsible, accountable, consulted, and informed for a task or decision.
- RAID LogRAID Log is a structured log used to track risks, assumptions, issues, and dependencies.
- Readiness AssessmentReadiness Assessment is a structured review of whether the conditions for the next step or launch are actually in place.
- Reference DataReference Data is relatively stable data sets used to classify or describe other data, such as country codes or status lists.
- Regression TestingRegression Testing is testing performed to check that recent changes did not break existing behaviour.
- ReleaseRelease is a version of a product or service made available to users or operations.
- Release PlanRelease Plan is a plan showing what changes are expected to be released and when.
- Release TrainRelease Train is a planned cadence on which multiple teams release or coordinate delivery together.
- Request for Information (RFI)Request for Information (RFI) is a document used to gather general information from suppliers before buying decisions are narrowed.
- Request for Proposal (RFP)Request for Proposal (RFP) is a document asking suppliers to explain how they would solve a defined need.
- Request for Quotation (RFQ)Request for Quotation (RFQ) is a document asking suppliers to provide pricing for a clearly defined requirement.
- RequirementRequirement is a clear statement of a need, capability, rule, or condition that must be met.
- Requirements BaselineRequirements Baseline is an approved reference version of requirements used for control and change management.
- Requirements ElicitationRequirements Elicitation is the work of gathering information about needs, problems, rules, and expectations from relevant sources.
- Requirements Traceability Matrix (RTM)Requirements Traceability Matrix (RTM) is a table that links requirements to design, build, test, and delivery evidence.
- Requirements ValidationRequirements Validation is the activity of checking that documented requirements reflect the real need and are fit for purpose.
- Resource PlanResource Plan is a plan showing what people, skills, time, or other resources are needed and when.
- RetrospectiveRetrospective is a session where a team reflects on how it worked and decides what to improve next.
- Return on Investment (ROI)Return on Investment (ROI) is a measure comparing the value gained from an investment with its cost.
- RiskRisk is a possible future event that could affect objectives if it happens.
- RoadmapRoadmap is a time-based view of intended outcomes, themes, or major pieces of work.
- Rollback PlanRollback Plan is a documented approach for reversing or backing out a change if serious problems occur.
- RunbookRunbook is a practical set of operating instructions for support or operational tasks.
- Schedule VarianceSchedule Variance is a measure showing how far actual schedule performance differs from the approved plan.
- ScopeScope is the defined boundary of what work, outcomes, and deliverables are included or excluded.
- ScorecardScorecard is a structured view of selected measures used to review performance against expectations.
- ScrumScrum is a specific way of practicing Agile.
- Scrum MasterScrum Master is the role that supports the Scrum team by improving flow, removing impediments, and protecting effective Scrum practice.
- SDLCSDLC is a structured lifecycle describing how software moves from idea to design, build, test, release, and support.
- Service Acceptance Criteria (SAC)Service Acceptance Criteria (SAC) is the conditions that must be met before a service or solution is accepted into live operation.
- Service OwnerService Owner is the role accountable for the ongoing performance, support, and improvement of a live service.
- Service TransitionService Transition is the controlled movement of a service into live operation and ongoing support.
- SIPOCSIPOC is a high-level process model showing suppliers, inputs, process, outputs, and customers.
- Software Requirements Specification (SRS)Software Requirements Specification (SRS) is a formal specification describing software requirements in a structured way.
- Source to Target MappingSource to Target Mapping is a specification showing how source data fields should populate target data fields.
- SpikeSpike is a time-boxed piece of work used to reduce uncertainty or learn something before delivery continues.
- SprintA sprint is a short, fixed period of time — usually one to four weeks — during which a team works to complete a specific set of tasks.
- Sprint GoalSprint Goal is the short statement describing what a sprint is trying to achieve.
- Stabilisation PeriodStabilisation Period is the period after release during which performance is monitored closely and issues are resolved.
- Stage GateStage Gate is a formal checkpoint where progress is reviewed before work moves into the next stage.
- StakeholderStakeholder is a person or group affected by a project or able to influence it.
- Statement of Work (SOW)Statement of Work (SOW) is a document describing the work to be delivered, its boundaries, responsibilities, and commercial terms.
- Status ReportStatus Report is a regular report summarising current progress, issues, risks, and next steps.
- Steering CommitteeSteering Committee is a senior group that reviews progress, resolves escalated issues, and makes key project decisions.
- Steering PackSteering Pack is the set of papers prepared for a steering committee or governance meeting.
- Story MappingStory Mapping is a way of organising work visually around the user's journey and the steps they take.
- Story PointsStory Points is a relative sizing method used to compare the effort or complexity of work items.
- Subject Matter Expert (SME)Subject Matter Expert (SME) is a person with deep knowledge of a business area, process, rule, or system.
- Success CriteriaSuccess Criteria is the agreed conditions used to judge whether an initiative or deliverable has succeeded.
- Support ModelSupport Model is the agreed structure for how a service or solution will be supported after release.
- Swimlane DiagramSwimlane Diagram is a process diagram that shows steps in lanes based on role, team, or system ownership.
- System Integration Testing (SIT)System Integration Testing (SIT) is testing that checks whether connected systems and interfaces work together as expected.
- Target Operating Model (TOM)Target Operating Model (TOM) is the intended future operating model for how a business capability or service should work.
- Test CaseTest Case is a defined set of steps, inputs, and expected results used to test something.
- ThroughputThroughput is the number of work items completed in a given period.
- TimeboxTimebox is a fixed amount of time allocated to an activity or piece of work.
- Total Cost of Ownership (TCO)Total Cost of Ownership (TCO) is the full cost of owning, running, supporting, and retiring something over time.
- Training PlanTraining Plan is a plan showing how users or support teams will gain the knowledge needed for the change.
- Transaction DataTransaction Data is data created by business events such as orders, claims, payments, or bookings.
- Transition PlanTransition Plan is a plan describing how work will move from delivery into live operation or a new business state.
- UAT (User Acceptance Testing)UAT stands for User Acceptance Testing.
- Use CaseUse Case is a structured description of how a user and a system interact to achieve a goal.
- User FlowUser Flow is a visual sequence showing the path a user takes through screens, decisions, or steps.
- User StoryA user story is a short, simple description of a feature written from the perspective of the person who will use it.
- VelocityVelocity is a measure of how much work a team tends to complete in a sprint or iteration.
- Vendor Evaluation MatrixVendor Evaluation Matrix is a scoring tool used to compare suppliers against agreed criteria.
- WaterfallWaterfall is a sequential delivery approach where major phases are completed largely in order.
- Weighted Shortest Job First (WSJF)Weighted Shortest Job First (WSJF) is a prioritisation method that compares relative value and urgency against job size.
- WireframeWireframe is a simple layout sketch showing the structure of a screen or page without full visual design.
- Work Breakdown Structure (WBS)Work Breakdown Structure (WBS) is a hierarchical breakdown of project work into smaller manageable parts.
- Work in Progress (WIP)Work in Progress (WIP) is the amount of work currently being actively worked on.
- WorkflowWorkflow is the sequence of tasks, rules, and approvals through which work moves.
- WorkshopWorkshop is a structured working session where people collaborate to explore, decide, or design something together.