Английский для управления проектами: ключевая лексика

"project charter"

A formal document that authorises a project, defines its objectives, and names the project manager.

"The sponsor signed the project charter before any resources were allocated to the initiative."

"scope creep"

The gradual, uncontrolled expansion of a project's scope beyond what was originally agreed, often without additional time or budget.

"The development team warned that adding new features without approval was causing serious scope creep."

"work breakdown structure"

A hierarchical decomposition of a project into smaller, manageable deliverables and tasks, abbreviated WBS.

"The project manager created a detailed work breakdown structure to assign responsibilities to each team member."

"milestone"

A significant event or achievement in a project schedule that marks the completion of a major phase or deliverable.

"Delivering the beta version to the client was the most important milestone in the first quarter."

"deliverable"

A tangible or intangible product, result, or capability that must be produced to complete the project or a phase of it.

"The final deliverable was a fully tested software application ready for deployment."

"baseline"

The approved version of a project plan — scope, schedule, and cost — against which actual performance is measured.

"Any changes to the budget must be compared against the original baseline to track variance."

"stakeholder register"

A document listing all stakeholders in a project along with their interests, influence, and communication requirements.

"Before kick-off, the team updated the stakeholder register to include the newly appointed department heads."

"feasibility study"

A preliminary analysis that evaluates whether a proposed project is technically possible and financially viable.

"The feasibility study concluded that the new distribution centre could be built within the approved budget."

"critical path"

The longest sequence of dependent tasks in a project that determines the earliest possible completion date.

"Any delay on the critical path will push back the entire project launch date."

"Gantt chart"

A horizontal bar chart that visually represents a project schedule, showing tasks, durations, and dependencies over time.

"The project manager shared a Gantt chart so every team member could see their task deadlines at a glance."

"float"

The amount of time a task can be delayed without affecting the project's overall deadline; also called slack.

"The testing phase had two weeks of float, giving the team flexibility to handle unexpected defects."

"fast-tracking"

A schedule compression technique where tasks normally done in sequence are performed in parallel to save time.

"To recover the lost two weeks, the manager approved fast-tracking the design and development phases."

"crashing"

A schedule compression method that reduces project duration by adding extra resources, usually at increased cost.

"Crashing the schedule by hiring two contractors allowed the team to meet the non-negotiable launch date."

"lead time"

The amount of time by which a successor task can start before its predecessor finishes.

"A three-day lead time allowed the QA team to begin preparing test environments before coding was complete."

"sprint"

A fixed, short time-box (typically one to four weeks) in which an Agile team completes a defined set of work.

"During the two-week sprint, the team focused exclusively on building the user authentication module."

"burn-down chart"

A graphical representation of work remaining versus time in a sprint or project, used to track progress against the plan.

"The burn-down chart showed the team was ahead of schedule after the first five days of the sprint."

"cost variance"

The difference between the budgeted cost of work performed and the actual cost — positive means under budget, negative means over.

"A negative cost variance of $15,000 in month three prompted a review of procurement spending."

"earned value"

The budgeted value of work actually completed at a point in time, used to measure project performance objectively.

"By calculating earned value, the sponsor could see that the team had completed 70% of the planned work."

"contingency reserve"

Budget set aside to cover identified risks and uncertainties that may affect project cost or schedule.

"The 10% contingency reserve was sufficient to cover the unexpected equipment replacement mid-project."

"cost-benefit analysis"

A systematic process of comparing the expected costs of a project against the benefits it will deliver to justify investment.

"The cost-benefit analysis showed a three-year payback period, which satisfied the finance committee."

"ROI"

Return on Investment — a ratio that measures the financial gain from a project relative to its cost.

"The digital transformation project delivered an ROI of 240% within 18 months of completion."

"budget at completion"

The total planned budget for a project, representing the entire authorised cost to complete all work; abbreviated BAC.

"With a budget at completion of $2 million, the team had to prioritise ruthlessly to avoid overruns."

"invoice"

A document sent by a vendor or contractor to a project requesting payment for goods or services delivered.

"The finance team processed all outstanding invoices before the end of the financial quarter."

"change order"

A formal document that authorises an addition, deletion, or revision to a project's scope, schedule, or cost.

"The client submitted a change order to add a new reporting module, which extended the timeline by two weeks."

"risk register"

A log documenting identified risks, their probability, potential impact, and the planned response strategy.

"The risk register was reviewed at every weekly meeting to update the status of each open risk."

"mitigation plan"

A documented strategy to reduce the likelihood or impact of a specific identified risk.

"The mitigation plan for the supplier delay included pre-qualifying two alternative vendors."

"risk appetite"

The amount and type of risk an organisation or project sponsor is willing to accept in pursuit of its objectives.

"With a low risk appetite, the board rejected any approach that could delay the product launch."

"issue log"

A document that tracks current problems affecting the project, their status, owner, and resolution progress.

"The project manager updated the issue log daily to ensure no open items were forgotten between meetings."

"escalation"

The process of raising an unresolved problem or decision to a higher level of authority within the project or organisation.

"After three failed attempts to resolve the conflict, the team lead escalated the matter to the steering committee."

"assumption"

A factor that is considered true or certain for planning purposes, but which could later prove incorrect and create risk.

"The schedule was built on the assumption that all regulatory approvals would be granted by March."

"workaround"

An unplanned response to a risk or issue that has already occurred, implemented because the original response was insufficient.

"When the main server failed, the team implemented a workaround using cloud backup to keep the project on track."

"trigger"

An event or condition that indicates a risk is about to occur, signalling that the response plan should be activated.

"A supplier's late delivery by more than three days was defined as the trigger to activate the contingency vendor contract."

"product backlog"

An ordered list of all work items — features, bug fixes, technical tasks — that need to be done to deliver a product.

"The product owner groomed the product backlog before the sprint planning session to ensure the top items were clearly defined."

"stand-up meeting"

A short daily team check-in, typically 15 minutes, where each member reports what they did, what they will do, and any blockers.

"The team held a virtual stand-up meeting every morning at 9 a.m. to stay aligned across different time zones."

"retrospective"

A regular Agile meeting held at the end of a sprint where the team reflects on what went well, what went wrong, and what to improve.

"The retrospective revealed that unclear acceptance criteria had caused most of the rework in the last sprint."

"velocity"

The amount of work a team completes in a sprint, measured in story points, used to forecast future delivery capacity.

"With an average velocity of 40 story points per sprint, the team could predict the release date with confidence."

"RACI matrix"

A responsibility assignment chart that defines who is Responsible, Accountable, Consulted, and Informed for each project task.

"The RACI matrix eliminated confusion by clearly assigning the accountable owner for each key decision."

"blockers"

Obstacles or impediments preventing a team member or the project from progressing, typically raised in stand-up meetings.

"The developer flagged a dependency on the DevOps team as a blocker during the morning stand-up."

"definition of done"

A shared team agreement that specifies all criteria a task or user story must meet before it is considered complete.

"According to the definition of done, every feature required code review, unit tests, and documentation before merging."

"user story"

A short, informal description of a feature written from the end user's perspective, following the format: As a [user], I want [goal] so that [reason].

"The product owner wrote a user story: 'As a customer, I want to reset my password so that I can regain access to my account.'"

"status report"

A regular document summarising a project's progress, budget, risks, and upcoming tasks for stakeholders.

"The project manager sent a weekly status report to all executives every Friday afternoon."

"lessons learned"

Knowledge and insights gained during a project that are documented to improve future project performance.

"The lessons learned session after go-live identified three process improvements for the next phase."

"project closure"

The final phase of a project in which all activities are formally completed, deliverables handed over, and the project officially ended.

"Project closure included archiving all documentation and releasing team members back to their departments."

"sign-off"

Formal approval by an authorised stakeholder confirming that a deliverable, phase, or the entire project is accepted as complete.

"The client's sign-off on the final report allowed the team to proceed to project closure."

"post-implementation review"

An evaluation conducted after a project goes live to assess whether it achieved its objectives and delivered expected benefits.

"The post-implementation review confirmed the new system had reduced processing time by 35%."

"KPI"

Key Performance Indicator — a measurable value used to evaluate how effectively a project or organisation is achieving its objectives.

"Customer satisfaction score was the primary KPI the steering committee tracked after the product launch."

"handover"

The formal transfer of project deliverables, documentation, and responsibilities from the project team to the operations or client team.

"A smooth handover required a two-week period of parallel running so the operations team could ask questions."

"acceptance criteria"

The specific conditions that a deliverable must satisfy for the client or product owner to formally accept it as complete.

"The acceptance criteria listed in the contract included zero critical bugs and full compliance with the data protection policy."