↑

English Vocabulary for Software Developers, Lesson 7: Managing the Backlog & Task Lifecycle

English Vocabulary for Software Developers, Lesson 7: Managing the Backlog & Task Lifecycle

Lesson Goals

  • Master the professional English vocabulary used in project management tools like Jira, Asana, or ClickUp.
  • Articulate issues regarding workload capacity, delivery speed, and changes in project scope.
  • Understand and apply the strict structural criteria required to move a task through its complete engineering lifecycle.

Target Vocabulary

  1. Ticket / Issue / Тикет / Задача в трекере
    • Definition: An individual record in a project management tool that describes a specific bug, task, or feature request to be worked on.
  2. Epic / Эпик (крупная задача)
    • Definition: A large body of work or a major feature category that can be broken down into several smaller user stories or tickets.
  3. Backlog / Бэклог (список запланированных задач)
    • Definition: A prioritized list of tasks, features, and bug fixes waiting to be developed or estimated by the engineering team.
  4. Blocker / Блокер (блокирующий фактор)
    • Definition: A critical issue or dependency that prevents a developer from making progress on a specific task or shipping code.
  5. Bandwidth / Пропускная способность (операционный ресурс / свободное время)
    • Definition: An individual’s or team’s mental, physical, or temporal capacity to take on new tasks or responsibilities.
  6. Velocity / Скорость разработки команды (велосити)
    • Definition: A metric calculated by measuring the average amount of story points a development team successfully delivers during a single sprint.
  7. Definition of Ready (DoR) / Критерии готовности задачи к работе (DoR)
    • Definition: A collaborative agreement defining the baseline information, design assets, and acceptance criteria a ticket must have before an engineer can pick it up.
  8. Definition of Done (DoD) / Критерии завершенности задачи (DoD)
    • Definition: A strict checklist of technical and quality benchmarks (e.g., code review completed, unit tests passed, deployed to staging) that a feature must satisfy before it is officially marked as complete.
  9. Scope Creep / Разрастание рамок проекта (добавление незапланированных требований)
    • Definition: The uncontrolled or gradual expansion of a project’s requirements mid-sprint or mid-project without adjustments to time, budget, or resources.

Reading Passage 1: Industry Overview

In many local software engineering teams, the lifecycle of a task can be highly informal. A manager might verbally request a quick change, and a developer might push that change directly to production without formalized review or testing. In the global tech workspace, however, every action revolves around the structured lifecycle of a Jira ticket. Individual tasks are organized under a high-level epic, and items waiting for attention reside in the product backlog. To protect efficiency, global teams rely on strict architectural boundaries. A developer will not pull a ticket into a sprint unless it meets the Definition of Ready (DoR). Similarly, a feature cannot be marked closed until it fulfills the absolute checklist of the Definition of Done (DoD). When unexpected features are pushed mid-sprint, it causes Scope Creep, which disrupts the team’s historical tracking metrics like velocity. Engineers are expected to protect their operational bandwidth and immediately flag any technical blocker in the tracker rather than quietly working overtime.


Reading Passage 2: Dialogue: Cleaning up the Sprint

Maria (Product Owner): Hey Arthur, I noticed that the payment gateway ticket is still sitting in the “In Progress” column even though the sprint ends tomorrow. Are you running into an infrastructure blocker?

Arthur (Backend Developer): Technically, the core logic is fully written. However, we’re dealing with severe scope creep. During yesterday’s sync, the design team asked me to add two unexpected webhooks for analytics tracking that weren’t in the original specification.

Maria: Oh, that shouldn’t happen mid-sprint. Those tracking metrics belong in a separate ticket inside the product backlog. We need to preserve our sprint velocity, or our quarterly forecasting will be completely off.

Arthur: Exactly. If I implement those webhooks now, I won’t have the bandwidth to finish writing the unit tests for the main transaction loop before the sprint cutoff.

Maria: Right, let’s pull those webhooks out. If you leave them out, does the core payment ticket meet our Definition of Done (DoD)?

Arthur: Yes. The code has passed peer review, the documentation is updated, and it passed our staging environment checks. Those are all the criteria on our DoD checklist.

Maria: Perfect. Go ahead and move that ticket to “Done.” Let’s create a new user story under the main integration epic for those analytics webhooks. We will refine it later to ensure it meets our Definition of Ready (DoR) before the next sprint planning.


Grammar & Usage Section: Discussing Workload & Scope Boundaries

When negotiating deadlines or defending your workload in global corporate cultures, it is vital to sound structured, collaborative, and metric-backed rather than defensive. Avoid saying: “I have too much work, I am busy.”

Instead, use standard engineering management frameworks:

  • Protecting your capacity: “Looking at my current sprint commitments, I don’t have the bandwidth to take on this additional task without dropping another priority.”
  • Highlighting unauthorized changes: “Adding these compliance requirements mid-sprint is introducing significant scope creep. Let’s document this in a new ticket for future refinement.”
  • Discussing task blockers: “I am currently blocked by the DevOps team’s environment deployment. I’ve updated the Jira status to reflect this dependency.”
  • Clarifying task criteria: “This user story doesn’t fully satisfy our Definition of Ready (DoR) because the design assets for the mobile view are missing.”

Practice Exercises

Part 1: Fill in the Blanks

Complete the sentences using the target vocabulary from this lesson.

  1. We cannot deploy this feature to production because it hasn’t passed code review, which is a mandatory requirement in our ________.
  2. The team’s sprint ________ dropped from 45 story points to 30 because three engineers were out sick last week.
  3. If the marketing team keeps adding secondary features to this MVP layout without extending the deadline, we will suffer from severe ________.
  4. I have noticed a major configuration issue that acts as a absolute ________ for my authentication service tasks.
  5. Please look through the product ________ and pull the highest-priority bug fixes into the next planning queue.

Part 2: Sentence Reconstruction (Word Order)

Rearrange the words to form grammatically correct sentences commonly used during sprint tracking.

  1. don’t / epic / I / think / belongs / this / user / to / story / this
  2. criteria / doesn’t / because / ticket / the / ready / meet / this / missing / are / acceptance
  3. points / sprint / allocated / many / story / this / how / to / are / ticket / ?
  4. manage / bandwidth / to / current / new / can’t / my / due / workload / I / this
  5. review / ready / update / let’s / the / status / to / code / ticket / for