Sample contracted-work translation

The update asks you to decide one thing: whether to postpone the switch to the new version until a package from another company is released.

This is a progress update from the company building your software, covering a two-week block of work they call sprint 14. It lists what they say they finished, what moved to the next block, and one decision they are putting to you.

The words it uses

• "Refactored the auth service" means the part of the system that signs people in was rebuilt without changing what it does for a user.
• A "JWT" is a signed pass the system issues after you log in. The update says these are now short-lived, meaning they expire quickly and have to be replaced.
• "Refresh token rotation" means the separate pass used to get a new one is replaced every time it is used, instead of being kept and reused.
• "P1" is the team's own label for their highest priority category. The update does not say what puts an item in it.
• An "SDK" is a package of code supplied by another company that your system is built on top of.
• "Staging" is a copy of the system used for testing, separate from the one your customers use.
• The "production cutover" is the moment the new version replaces the one currently running for customers.

What it says was done

• The sign-in rebuild, described above.
• Seven items in the team's P1 category, which the update says clears that list.
• The update says staging is passing its checks.

What moved to the next block

• The reporting module migration.
• The update gives the reason as a version of the vendor SDK that has not been released yet by the company that makes it.

The numbers in it

• "Velocity 34 points against a 40 point commitment." Points are the team's own internal unit for the size of a piece of work. They are not hours and not money, and the update does not say how the team converts one to the other.
• The team planned 40 and recorded 34. Both figures are their own measure of their own work.

What it asks of you

• One decision: whether to hold the production cutover until the vendor's package is released.
• The update states its own preference for holding. It does not give a date by which you need to answer.

Deep-dive questions for the people doing the work

1. 1

   What puts an item in the P1 category, and what were the seven that were closed?

   What this is asking: You are asking what their highest priority label actually means and what work it covered here.

   A clear answer covers: A description of the seven items and the rule the team uses to assign that label.

   Why it matters: The update reports the seven as a count without saying what they were, so the count is the only thing you currently have.

2. 2

   Has the vendor given a date for the SDK version the reporting module needs?

   What this is asking: You are asking whether the thing this piece of work is waiting on has a known release date.

   A clear answer covers: Either a date the vendor has published, or a clear statement that the vendor has not given one.

   Why it matters: The update names this as the reason the work moved to the next block but does not say when it is expected to clear.

3. 3

   If the production cutover is held, what else moves with it?

   What this is asking: You are asking what the knock-on effects of postponing the switch would be.

   A clear answer covers: A list of the work or dates that depend on the cutover, or a statement that nothing else depends on it.

   Why it matters: This is the decision the update is asking you to make, and it sets out the choice without saying what follows from either answer.