Choose the most professional phrasing for reporting what you did, how far along you are, and when you'll finish — in 5 real standup scenarios.
Progress reporting — 5 key phrases
"I completed the [specific feature/task] — it's merged / deployed / tested."
"I'm about [X]% through the [task]. I expect to finish by [time]."
"I'm still working on [task] — [specific remaining piece] left."
"My revised estimate is [date/time] — here's why it changed: [reason]."
"I have capacity for more — are there any backlog items I can pick up?"
0 / 5 completed
1 / 5
During standup, you finished implementing OAuth login yesterday. Which phrase sounds most professional?
I completed the [specific feature] and it's [status] is the ideal standup phrase. Use past simple + specific technical detail + outcome. "I did the login feature" is too vague — which feature? "Login thing is done" sounds casual and unprofessional. "I was working on login" uses past continuous which implies the work is still ongoing, not finished.
2 / 5
You're 70% through a refactoring task. Which progress update gives your team the most useful information?
Quantified progress + specific remaining work + timeline is the gold standard. "70% through the database refactoring" gives a mental model. "Remaining service-layer changes by EOD" tells the team exactly what's left and when. "Almost done" and "still working on it" give no useful data. The team needs to know: how far along, what remains, when it will be done.
3 / 5
You completed two tasks yesterday: fixed a bug and wrote unit tests. How do you report this most effectively?
Specific task + specific outcome for each item is the pattern. "Resolved the null pointer exception in the cart service" names the exact bug and where it was. "12 tests, all passing" gives a concrete measure of output. Generic phrases like "a bunch of things" or "some tests" waste the team's time because they must follow up to understand what you actually did. Be specific, be brief.
4 / 5
Your feature is 90% done but you're waiting on a design decision before you can finish. Which update is most accurate?
State what's done, name the specific dependency, identify who you're waiting on. This update tells three things: (1) most work is done, (2) the exact remaining piece is the notification UI, (3) it's blocked by UX, not by your own capacity. This is how the team lead knows to chase the UX team, not you. Vague answers like "almost there" create uncertainty — is it a 1-hour task or a 2-day task?
5 / 5
You worked on the same task for 3 days and it's still not complete. A teammate asks for an honest update. What do you say?
Acknowledge the miss, explain the cause, give a revised estimate, state your action. This is not making excuses — it's giving the team the information they need. Key elements: (1) original estimate was 2 days, (2) specific cause: data transformation complexity, (3) revised deadline: end of tomorrow, (4) follow-up action: update the ticket. Saying "should be done soon" three days in a row destroys trust. Specific revised estimates rebuild it.