All jobs / Project / delivery manager

Delivery Tracking interview questions

Delivery Tracking questions a Project / delivery manager can be asked, from first job to senior. Open one to see the strongest answer and why it works.

  1. What is the difference between lead time and cycle time?

    The strongest answer: Lead time is the clock the customer feels — from accepted request to delivery; cycle time runs from work actually starting to done — and the gap between them is queue time

    Why it works: Exactly — and the gap is the point: a fast cycle time with a long lead time means work waits in a queue, not on a desk.

    • Lead: request to delivery.
    • Cycle: start to done.
    • The gap is queue time.
    • State where your clock starts.

  2. People are working tickets that are not on the board. What is the problem?

    The strongest answer: The board is no longer the truth, so we cannot see WIP, blockers, or the forecast — we put the work up, we do not keep a shadow list

    Why it works: Exactly. A shadow list kills WIP limits and honesty. One board, the real work.

    • One board, the real work.
    • Shadow lists hide WIP.
    • Do not keep a leadership board.
    • Do not delete work to look clean.

  3. Cycle time looks fine but people mention night work and “quick favors.” What do you suspect?

    The strongest answer: Hidden WIP — work that is not on the board — and I make it visible before I praise the numbers

    Why it works: Exactly. Favors and nights are WIP. Visibility first; the number second.

    • Hunt hidden WIP.
    • Put favors on the board.
    • Do not praise a number that excludes nights.
    • Do not raise limits to match the shadow.

  4. The sprint burndown has been flat for four days, although the team says it has finished several stories.

    What is going on, and what would you look at instead?

    The strongest answer: Scope is being added as fast as work finishes, so the remaining line does not move; a burn-up plots done and total scope as two lines, so the growth is visible instead of hidden

    Why it works: Right — a burndown collapses scope change and progress into one line; a burn-up separates them, which is why you reach for it whenever scope moves.

    • Flat burndown: suspect scope growth.
    • Burndown hides added work.
    • Burn-up: done and scope lines.
    • Never edit the chart to slope.

  5. Half the sprint is carrying over again. Someone wants to split the leftovers so the report looks better. What do you do?

    The strongest answer: I leave the carry visible and I ask what we started too much of — I do not split cards to decorate a report

    Why it works: Exactly. Carry is information. Splitting to look finished is a lie.

    • Keep carry visible.
    • Ask what we started too much.
    • Do not split to decorate.
    • Do not fake-done leftovers.

  6. A three-month initiative arrives and the team asks how to structure it in Jira or Azure Boards.

    How do you structure it?

    The strongest answer: An epic (or feature) per outcome-sized chunk, stories under it that each deliver something a user can see, sub-tasks only for the team’s own steps — boards track stories, so anything that matters is a story

    Why it works: Exactly — the hierarchy exists so progress rolls up to something stakeholders recognise while the board shows units of value.

    • Epic, story, sub-task.
    • Epics: outcome-sized chunks.
    • Stories: visible user value.
    • Sub-tasks: team steps only.

  7. Remote people drop blockers in a side channel you do not see. The board looks healthy. What do you change?

    The strongest answer: I make one place for blockers that the board and the overlap both use, and I stop treating “quiet Slack” as “no impediments”

    Why it works: Exactly. One visible place. Quiet is not healthy. Hero-reading every channel does not scale.

    • One home for blockers.
    • Tie it to the board and the overlap.
    • Do not treat quiet as healthy.
    • Do not become the human inbox.

  8. On the team’s cumulative flow diagram, the “In review” band has been widening for three weeks while “Done” climbs slowly.

    What does it tell you, and what do you do?

    The strongest answer: Work enters review faster than it leaves — a queue is forming there; I make review the team’s bottleneck to fix: limit WIP upstream, pair on reviews, and watch whether the band narrows

    Why it works: Right — band width is WIP, slope is throughput; a widening band is the picture of a queue forming, and the fix is the system, not a person.

    • Widening band means a queue.
    • Width is WIP, slope is throughput.
    • Limit upstream, add review capacity.
    • Watch whether it narrows.

  9. Leadership wants a cycle-time target of “under five days.” What do you do with the metric?

    The strongest answer: I show the observed spread and what actually sits in the waits — I do not set a target that teaches people to close cards early

    Why it works: Exactly. Observed spread and waits. A target that rewards early close is how the board lies.

    • Show the observed spread.
    • Name the waits inside it.
    • Do not set a target that teaches fake-done.
    • Do not hide the misses.

  10. Delivery looks “green” because many tickets closed and the user problem did not move. How do you reset the bar?

    The strongest answer: I pair the range with the outcome we said we were after — I do not let closed tickets be the story

    Why it works: Exactly. The bar is the outcome plus an honest range. Ticket green is décor.

    • Tell the outcome and the range.
    • Do not let ticket-close be the story.
    • Do not raise output targets as the fix.
    • Do not declare a win on effort.