Agile project management: giving status updates
1
Think about these questions before reading. Share your ideas with a partner.
- Think about a team project you've worked on, either at work or in your studies. What were the biggest challenges in keeping everyone coordinated and informed?
- In your opinion, what is the difference between a productive team meeting and one that feels like a waste of time? Can you give an example from your own experience?
- Imagine you are managing a project and an unexpected problem arises that completely changes your original plan. How would you handle this situation to get the project back on track?
2
Daily scrum update practice
Listen to the dialogue. Notice how the vocabulary and grammar from the lesson are used.
3
Key vocabulary for project updates
Vocabulary
These expressions will help you discuss progress and challenges more effectively in a professional setting.
Examples
To touch base — to make contact with someone briefly to get an update or share information.
Usage note: This is a common, semi-formal phrase used in business communication, especially in emails or at the start of a meeting. You can say 'Let's touch base tomorrow morning.'
A bottleneck — a point in a process where progress is slowed down or stopped completely because of a problem or overload of work.
Usage note: This noun is often used with verbs like 'identify', 'create', or 'remove'. For example: 'The review stage has become a bottleneck in our workflow.'
To get bogged down in (something) — to become stuck on a particular aspect of a task, often preventing you from making progress on the main objective.
Usage note: This phrasal verb is often followed by 'the details'. It has a negative meaning, suggesting inefficiency. Example: 'Let's focus on the main goals and try not to get bogged down in the minor details.'
To be on the same page — to have a shared understanding or agreement about a situation or plan.
Usage note: This is a very common idiom in team settings. It's a great way to check for alignment. You can ask, 'Before we continue, I just want to make sure we're all on the same page.'
Actionable feedback — specific, clear, and practical advice that someone can easily use to make improvements.
Usage note: This is a key concept in professional development and Agile retrospectives. It's the opposite of vague criticism. For example: 'Instead of saying 'do better', give actionable feedback like 'try adding more specific examples to your report'.'
4
Project management phrases
Complete the sentences with the correct ending.
Match each item on the left with the correct item on the right.
Drag or click to match
Definitions
5
Grammar: using the passive voice for updates
Grammar
The passive voice is often used in professional settings like scrum meetings to focus on the action or result, not the person who performed it. We use it to describe what has been done, what is being done, or what needs to be done in a project. This makes your updates sound more objective and team-focused.
Examples
The user authentication feature was completed yesterday.
Use the passive (be + past participle) to emphasize the task itself. This is common in status reports.
Currently, the final code review is being conducted by the senior developers.
The passive can be used in various tenses. Here, the present continuous passive shows an ongoing action.
All known blockers have been resolved, so the sprint can proceed as planned.
The present perfect passive is perfect for reporting recent achievements that are relevant to the current situation.
Key points
- Form the passive with the verb 'to be' + the past participle (e.g., is developed, was fixed, has been tested).
- Use the passive to focus on the action or the result, not the person doing the action (the 'agent').
- Common mistake: Avoid overusing the passive. The active voice ('I fixed the bug') is often better for showing personal responsibility.
6
Find the mistake
Read the sentences below. They are all related to giving updates in a project management context.
Each sentence contains one error. Find and correct it.
01I have finished the user authentication feature yesterday, so I'm moving on to the next task.
Corrected version
I have finished the user authentication feature yesterday, so I'm moving on to the next task.
02The list of impediments for this sprint are growing longer each day.
Corrected version
The list of impediments for this sprint are is growing longer each day.
03We need to make sure the whole team is alignment before we start the next sprint.
Corrected version
We need to make sure the whole team is alignment aligned before we start the next sprint.
04I'm getting bogged down with the details of the bug report and can't see the bigger picture.
Corrected version
I'm getting bogged down with in the details of the bug report and can't see the bigger picture.
05Let's touch the base later this afternoon to discuss the client's feedback.
Corrected version
Let's touch the base later this afternoon to discuss the client's feedback.
06The final report has been send to the stakeholders for their review.
Corrected version
The final report has been send sent to the stakeholders for their review.
07The approval from the legal team has become main bottleneck in our workflow.
Corrected version
The approval from the legal team has become the main bottleneck in our workflow.
7
Useful phrases: giving updates in a daily stand-up
Vocabulary
In a daily stand-up or scrum meeting, your update needs to be quick and clear. These phrases will help you sound natural and professional when sharing what you've done, what you're doing next, and if you need any help.
Examples
Just a quick update from my side... — a simple and professional way to start your turn.
Register: neutral. Use this to signal that you're about to begin your update. It sets a concise, efficient tone.
Yesterday, I managed to wrap up the... — to talk about a task you successfully completed.
Register: neutral. 'To wrap up' is a common phrasal verb for 'to finish'. Using 'managed to' subtly suggests you overcame a small challenge to complete it.
My main focus today will be on... — to state your primary goal for the day.
Register: neutral to formal. This is a great way to show you are organised and have prioritised your work. You can follow it with '...getting the first draft of the report finished.'
I'm running into a bit of an issue with... — a soft way to introduce a problem or blocker.
Register: neutral. This is less direct than saying 'I have a problem'. It sounds more collaborative and opens the door for others to offer help. For example: '...the API connection.'
I could use a second pair of eyes on... — a polite and collaborative way to ask for help or a review.
Register: neutral to informal. This is perfect when you're not completely blocked but would like someone to quickly check your work or give their opinion. It's less demanding than asking for 'help'.
No blockers on my end at the moment. — to clearly state that nothing is preventing you from making progress.
Register: neutral. 'On my end' is a very common phrase meaning 'from my perspective' or 'in my area of work'. It's a standard and efficient way to close your update if everything is fine.
8
Complete the sentences with words or phrases from the box. One is extra.
Word bank
01The code review process has become a major , slowing down our deployment schedule significantly.
02Let's try not to get in the small details and instead focus on completing the main tasks for this sprint.
03Could we quickly after the stand-up meeting? I have a quick question about the latest client request.
04The retrospective was very productive; we received a lot of that we can use to improve our process next week.
05Before we commit to the plan, let's confirm that the product owner and the development team are about the project goals.
9
Making stand-ups work
Read the passage below, then answer the comprehension questions.
For weeks, our team’s daily stand-up had become the biggest bottleneck in our workflow. What was intended to be a quick, 15-minute sync-up regularly stretched into an hour-long debate. Team members would get bogged down in highly specific technical problems, losing sight of the meeting's purpose. It was clear we were no longer on the same page about how to use this time effectively. A decision was made by the team lead: updates would be strictly limited to progress, plans, and impediments. Any issue requiring a deep dive was to be 'parked' for a separate follow-up meeting with only the relevant people. Since this new structure has been implemented, the change has been remarkable. We touch base efficiently, actionable feedback is shared when necessary, and the team feels far more aligned on our sprint goals.
01What was the main problem with the team's original daily stand-up meetings?
Sample answerThey were too long and unfocused because team members would get stuck discussing specific technical details.
02According to the new rule, what should happen to a complex issue raised during the stand-up?
Sample answerIt should be 'parked' and discussed later in a separate meeting involving only the relevant people.
03The passage says the team was not 'on the same page'. What does this imply about their meetings?
Sample answerIt implies that team members had different understandings or expectations for the purpose of the meeting, which caused inefficiency.
04What has been the most significant positive outcome since the new meeting structure was introduced?
Sample answerThe team has become more efficient and aligned on their goals because the meetings are now short and focused.
10
Discuss these questions with a partner. Try to use vocabulary from the lesson.
- Some critics argue that daily stand-up meetings can become a routine chore rather than a productive way to identify impediments. To what extent do you agree? What strategies can a team use to ensure everyone stays on the same page without getting bogged down in repetitive updates?
- The Agile approach requires team members to give and receive actionable feedback very frequently. Thinking about the professional or academic culture in your country, how common is this style of direct and constant feedback? What might be some cultural challenges in implementing it effectively?
- Imagine a project where one person's work is consistently creating a bottleneck for the rest of the team. Do you think the public transparency of an Agile system is the most effective way to handle this, or could it be demotivating for the individual? What's the best way for a manager to touch base with that person about the issue?