Your learning profile
Project management
Delivering projects on scope, time and cost, agile ways of working and the craft of business analysis. 111 terms.
This part of the Stockertim Dictionary explains 111 terms from project management in plain English. A full entry gives the definition first, then how the term is used in practice and the free lessons that teach it.
Topics in this subject
- Scope and planning
- Scheduling
- Cost, risk and control
- Agile delivery
- Governance and stakeholders
- Business analysis
- Acceptance criteriaThe specific, testable conditions a requirement or deliverable must meet before the business agrees it has been delivered.
- Actual costThe money actually spent on the work completed by a given date, taken from the project's cost records.
- Adaptive approachA way of running a project in which work is delivered in short iterations, each reviewed with users, so the scope can change as the team learns.
- Administrative closureThe paperwork of ending a project: final payments, closed contracts, archived records, released resources and a closure report.
- Adoption rateThe share of transactions, or of intended users, that goes through a new system rather than the old route over a period, used to judge whether a change has tak…
- Analogous estimateAn estimate made by taking the actual cost or duration of a similar past project and adjusting it for known differences.
- Analysis planA table listing each hypothesis, what would have to be true for it to hold, the analysis and data that test it, its owner and its deadline.
- As-is processA model of how a process actually runs today, including workarounds and delays, drawn before any improvement is designed.
- Benefits ownerThe named manager accountable for a specific benefit in a business case being measured and achieved after the change is delivered.
- Benefits realisation reviewA check made after a project has closed, comparing the benefits promised in the business case with those actually achieved.
- Benefits trackingGiving each promised benefit a measure, a baseline from before the change, an owner and a review date, then reporting progress against it after go-live.
- Bottom-up estimateAn estimate built by costing every work package or activity in detail and adding the results together to give the project total.
- Business analysisThe practice of understanding what an organisation needs, defining those needs clearly and recommending solutions that deliver value.
- Business analystA person who investigates business problems and opportunities, elicits and documents requirements, and helps choose and deliver the right solution.
- Business caseA document that sets out a need, the options considered, their costs, benefits and risks, and recommends one for a decision to invest.
- Business needA problem to solve or an opportunity to take, stated as the outcome an organisation wants rather than as a particular solution.
- Communication planA table of who needs what information about a project, in what form, how often and from whom, agreed early and kept up to date.
- Contingency reserveMoney or time held inside the project baseline for identified risks that may occur, usually controlled by the project manager.
- Continuous improvementThe ongoing practice of measuring a process, finding further problems and making small, regular changes rather than waiting for a large project.
- Cost performance indexEarned value divided by actual cost: below 1 the project gets less than a unit of budgeted work for each unit spent.
- CrashingShortening a project schedule by adding resources to activities on the critical path, which usually raises cost.
- Critical pathThe longest chain of dependent activities through a project network, which sets the shortest possible project duration and has no float.
- Cut-overThe planned, rehearsed sequence of tasks that moves an organisation from the old system to the new one, from the data freeze to opening the new system to users.
- Cycle timeThe elapsed time from the start of a process to its end for one item, including waiting time as well as working time.
- Data cleaningPreparing raw data for analysis by removing duplicates, correcting formats, handling missing values and recording every change made.
- Descriptive analysisSummarising data to show what happened, using counts, averages, spreads and simple charts, without yet explaining why.
- Do-nothing optionThe option in a business case that describes what happens if no change is made, used as the baseline against which other options are judged.
- Earned valueThe budgeted cost of the work actually completed by a given date, used to measure progress in money terms whatever the work really cost.
- ElicitationDrawing out needs, constraints and knowledge from stakeholders and other sources, using techniques such as interviews, workshops and observation.
- EscalationEscalation is passing a conflict, risk or decision to a more senior person or a formal process because it cannot be resolved properly at the current level.
- Estimate at completionA forecast of a project's total cost by the time it finishes, often found by dividing the full budget by the cost performance index.
- Expectation managementKeeping a client's understanding of what will be delivered, when and with what confidence in line with what the team can actually achieve.
- Expected monetary valueThe probability of a risk multiplied by its financial impact, giving one figure that can be compared across risks or with a response's cost.
- Fast-trackingShortening a schedule by doing in parallel activities that were planned to run one after the other, which adds risk of rework.
- FeasibilityAn evaluation test asking whether an organisation has, or can obtain, the money, people, skills and time needed to carry out a strategic option.
- Fishbone diagramA cause-and-effect diagram with the problem at the head and possible causes grouped along bones by category, used to explore root causes.
- Five whysA questioning technique that asks why a problem occurred, then why that cause occurred, repeatedly, until a cause that can be fixed is found.
- Fixed feeA pricing model in which the adviser agrees one price for a defined scope and carries the risk if the work takes longer than planned.
- Formal acceptanceWritten confirmation from the customer or sponsor that a deliverable meets its agreed criteria, transferring it from the project to its owner.
- Functional requirementA statement of something a solution must do, such as record a payment or send a confirmation, that can be demonstrated and tested.
- Gantt chartA schedule drawn as horizontal bars against a calendar, so the length, timing and overlap of each activity can be seen at a glance.
- Gap analysisA comparison of the current state with a target state, measured in the same terms, to show the distance a change must close.
- HandoverThe transfer of a project's deliverables, documents, training and support arrangements to the people who will operate and maintain them.
- Hard benefitA benefit of a change that can be measured in money with reasonable confidence and traced to it, such as hours of work removed or a licence no longer paid for.
- Hybrid approachA project approach that combines predictive planning for stable, well-understood work with adaptive delivery where needs are uncertain.
- HypercareA period of intensive support right after go-live, with extra staff on hand to resolve issues quickly while users settle into the new way.
- Implementation roadmapA plan setting out the actions, owners, timing and milestones needed to carry out a recommendation, usually shown as phases over time.
- IncrementThe usable, tested piece of a product that an iteration adds to everything delivered so far.
- Intangible benefitA real benefit of a change that cannot be measured reliably in money, such as better morale, reputation or customer trust.
- Issue treeA diagram that breaks a central question into sub-questions, and those into smaller ones, until each branch can be answered by one piece of analysis.
- IterationA short, fixed period of work in an adaptive project, typically one to four weeks, that ends with a working, tested increment of the product.
- Job shadowingAn elicitation technique in which an analyst watches a person do their normal work for a period, noting what is done, how and why.
- Lessons-learned reviewA structured meeting at the end of a project or phase in which the team records what went well, what did not and what to do differently next time.
- Management reserveMoney or time held outside the project baseline for risks nobody has identified, released only with the sponsor's approval.
- MeanThe sum of a set of values divided by how many values there are, the figure most people call the average.
- MedianThe middle value when a set of values is arranged in order, so that half the values lie below it and half above.
- MobilisationThe first days of an engagement, when the team is assembled, access and data are arranged, the plan is confirmed and the team meets the client.
- MoSCoWA prioritisation method that sorts requirements into must have, should have, could have and will not have this time.
- Must-have requirementA requirement whose absence rules a system out whatever else it does well, used as a pass or fail gate in selection while other requirements are scored.
- Network diagramA drawing of a project's activities as boxes joined by arrows that show which activities must finish before others can start.
- Non-functional requirementA statement of how well a solution must perform, covering qualities such as speed, availability, security, capacity, accessibility and usability.
- Options appraisalThe part of a business case that compares different ways of meeting a need, including doing nothing, on costs, benefits and risks.
- Parametric estimateAn estimate made by multiplying a measured quantity, such as floor area or number of users, by a known rate per unit.
- PilotA live trial of a solution with a limited group of real users or sites, run to learn what works before a wider rollout.
- Planned valueThe budgeted cost of the work scheduled to be done by a given date, read from the project's time-phased cost baseline.
- Power and interest gridA stakeholder map with power on one axis and interest on the other, giving four quadrants that each call for a different level of engagement.
- Predictive approachA way of running a project in which scope, schedule and budget are planned in full before building starts, then delivered in sequence.
- Problem statementA short written definition of the question an engagement must answer, naming the decision, the decision maker, the measure of success and the constraints.
- Process mappingProcess mapping is drawing every step, decision, queue and hand-off in a process in sequence, so that delays, repeated work and waste become visible.
- ProgrammeA group of related projects and activities managed together to achieve benefits and control that would not be available if they were managed separately.
- ProjectA temporary piece of work with a defined start and end, set up to create a unique product, service or result.
- Project charterA short document that formally authorises a project and names its sponsor, manager, purpose, high-level scope, budget and success criteria.
- Project lifecycleThe sequence of phases a project passes through from start to finish, commonly initiation, planning, execution, monitoring and closure.
- Project sponsorThe senior person who owns the business need for a project, secures its funding, champions it and is accountable for its benefits.
- Proof of conceptA small, limited build or trial that tests whether an idea or technology can work at all, before any commitment to a full solution.
- Quick winsQuick wins are small, visible improvements delivered early in a change effort to show the change works, reward supporters and build momentum for the harder ste…
- RACI matrixA table showing, for each activity or decision, who is responsible, who is accountable, who is consulted and who is informed.
- Readiness assessmentA structured check before go-live of whether the people, processes, data and technology are prepared to operate the new way.
- Requirements lifecycleThe stages a requirement passes through, from being elicited and documented to approval, delivery, testing and eventual retirement.
- Rework rateThe share of items passing through a process that must be corrected or done again, usually expressed as a percentage.
- Risk registerA risk register is a structured record of an organisation's or project's identified risks, with their causes, consequences, owners, ratings, controls and plann…
- Risk responseThe planned action for a risk: avoiding, transferring, reducing or accepting a threat, or exploiting, sharing, enhancing or accepting an opportunity.
- Root cause analysisA structured search for the underlying cause behind a pattern of errors, complaints or failures, so it can be fixed and not just treated.
- Scope creepThe gradual, uncontrolled growth of a project's scope through small additions that are never formally assessed or approved.
- Scope statementA written description of what a project will deliver, its boundaries, main deliverables, acceptance criteria, assumptions and exclusions.
- Scoring matrixA table that rates each option against weighted decision criteria and adds the weighted scores to compare options on one scale.
- Scripted demonstrationA supplier demonstration in which the buyer writes the scenarios and every shortlisted supplier shows the same ones, with the same sample data, to the same pan…
- Soft benefitA real benefit of a change that is hard to price or attribute with confidence, such as better engagement or faster decisions, usually described rather than cou…
- Solution scopeThe set of capabilities a chosen solution will deliver to meet a business need, marking what is inside and outside its boundary.
- Stakeholder mappingListing the groups with a stake in an organisation or decision and deciding how much attention and engagement each one needs.
- Stakeholder registerA list of everyone who affects or is affected by a project, with their role, interest, influence and the planned way of engaging them.
- Statement of workThe signed document that sets out an engagement's scope, deliverables, timing, team, fees, assumptions and exclusions, forming the basis of the contract.
- Status reportA short regular update, often one page, covering progress against plan, risks and issues, decisions needed and the next steps.
- Steering committeeThe group of senior client leaders, often joined by the engagement partner, that meets at set points to review progress, make decisions and remove obstacles.
- Success criteriaThe measurable conditions, agreed before a project starts, against which it will later be judged a success or a failure.
- Super userA member of a user team who is trained early and in depth, then supports colleagues with a new system or process before and after go-live.
- Swimlane diagramA process diagram in which each role or team has its own lane, so every hand-off between roles is visible as a line crossing lanes.
- SymptomA visible effect of a problem, such as a complaint or a delay, that signals something is wrong without explaining why.
- Tangible benefitA benefit of a change that can be measured directly in money or countable units, such as hours saved, errors avoided or extra sales.
- Team charterA team charter is a short written agreement recording a team's purpose, goals, roles, ways of working and decision rules, so that everyone starts with the same…
- Terms of referenceThe written document setting out a committee's or project's purpose, membership, powers, duties and how it reports.
- Three-point estimateAn estimate that combines optimistic, most likely and pessimistic values, usually weighting the most likely value four times.
- Time and materialsA pricing model in which the client pays for the hours or days actually worked at agreed rates, plus expenses, without a fixed total price.
- To-be processA model of how a process should run after a change, designed to remove the waste found in the as-is and to meet the requirements.
- Total floatThe time an activity can be delayed without delaying the end of the project, found as its latest start minus its earliest start.
- Transition planA plan setting out how an organisation moves from its current state to a target state: what changes, in what order, over what period and with what safeguards.
- Triple constraintThe linked limits of scope, time and cost on a project, where a change to one forces a change in at least one other.
- User storyA short requirement written from a user's point of view, naming who wants something, what they want and why they want it.
- Weighted scoring modelA weighted scoring model compares options by giving each criterion a weight, scoring every option against each criterion, and adding the weighted scores to ran…
- Work breakdown structureA hierarchy that breaks all the work of a project into smaller pieces, ending in work packages that can be estimated, assigned and tracked.
- Work packageThe lowest level of a work breakdown structure: a defined piece of work that one person or team can own, estimate, schedule and report on.
Other subjects
- Finance
- Markets
- Investing
- Business
- Accounting
- Technology
- Artificial intelligence
- Fintech
- Regulation
- Financial law
- Crypto
- Cybersecurity
- Political economy
- Financial ethics
- Economics
- Personal money
- Marketing
- Media
- Advertising
- Public relations
- Brand
- Audit and assurance
- Risk management
- Strategy and management
- Consulting
- Human resources
Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.