Practice status reporting vocabulary: RAG status, Amber risk communication, weekly steering committee updates, dependency risks, and executive status formats.
0 / 16 completed
1 / 16
What does 'RAG status' mean in project reporting?
RAG stands for Red/Amber/Green — a traffic light status system. Green means on track, Amber means at risk but manageable, Red means seriously off track and requiring immediate action. It gives executives an instant visual summary of project health.
2 / 16
A PM reports 'the project is Amber — risk of missing Q3 target'. What action does Amber typically trigger?
Amber status means the project is at risk but not yet in crisis. It triggers proactive action: the PM should document the specific risk, present mitigation options, update the steering committee, and increase the monitoring frequency. Amber is a warning to act before it turns Red.
3 / 16
'The weekly status email to the steering committee.' What should this typically contain?
A steering committee status email should be concise and executive-focused: current RAG status, what was accomplished, what risks or issues exist, what decisions are needed from the committee, and what happens next. Steering committees don't want implementation details — they want to know if they need to act.
4 / 16
A PM says 'we're on track but have a dependency risk'. What does this mean?
A dependency risk means the project's progress relies on something outside the team's direct control — another team delivering an API, a vendor completing integration, or a third party approving access. Even if the project is currently on track, this external dependency could delay it.
5 / 16
What is the purpose of 'executive status vocabulary' in project reporting?
Executive status vocabulary translates technical and operational details into business impact language. Instead of 'the CI pipeline failed 3 times', say 'we have a reliability risk in our delivery process that we're mitigating'. Executives need to understand risks, decisions, and impact — not implementation details.
6 / 16
Sarah, the lead developer on Project Phoenix, is writing a comment on a code review for John. John has flagged a potential performance bottleneck in the database query. Sarah replies: 'This needs investigation. Let's add a status ticket to track this.' What does 'adding a status ticket' primarily signify within this context?
Adding a status ticket isn't simply about raising an issue; it's about establishing a structured process. It creates a task with assigned ownership (to Sarah) and allows for tracking progress – key aspects of managing technical risk in a development environment. Option A is too broad, C is premature escalation, and D assumes John's skills are sufficient.
7 / 16
Mark, a project manager, sends a Slack message to the development team: 'Just updating – API v2.0 is now deployed and stable. We're seeing some intermittent latency spikes, but monitoring is in place.' What does 'monitoring is in place' MOST likely imply regarding the ongoing situation?
'Monitoring is in place' signifies proactive observation. It means a system (likely monitoring tools) is actively tracking the latency spikes to gather data and identify patterns. This allows for informed decision-making – ignoring the issue would be negligent, and refactoring without understanding the root cause is inefficient.
8 / 16
David, a senior engineer, is explaining the current status of Feature X to the team during a daily standup. He says, 'The build is green, but we've hit a minor roadblock with integration testing – some tests are failing intermittently.' What does 'hitting a roadblock' most likely indicate in this context?
'Hitting a roadblock' signifies an unexpected obstacle preventing progress. It doesn't necessarily mean the code is broken or that the team failed; it indicates a problem requiring attention and a revised approach to overcome it. The phrase implies a need for troubleshooting before continuing development.
9 / 16
Maria, the product owner, sends a message in Slack: 'Okay team, status update on Task Y. The API endpoint is returning 500 errors intermittently – we're seeing a correlation with high CPU usage on the database server. Rolling back to v1.2 for now.' What does 'rolling back' suggest about Maria's immediate action?
'Rolling back' is a standard practice in software development when an update introduces problems. It represents reverting to a known-good version of the system before attempting further changes or investigations. This minimizes disruption and allows for recovery from the error.
10 / 16
David, a senior engineer, is presenting the project status to stakeholders. He states: 'The system is currently in 'Yellow' – indicating potential delays impacting our sprint goal. What does a 'Yellow' status typically signify within Agile reporting?
'Yellow' status in Agile reporting represents a moderate level of risk—a potential issue that isn't critical but needs attention. It signifies that the team is aware of a problem and actively monitoring it to prevent escalation to 'Red'. A 'Yellow' doesn't necessarily mean immediate action, but signals proactive management.
11 / 16
Sarah, a developer, receives a Slack message from Mark: 'Just noting – the microservice deployment failed with a 503 error. We're investigating.' What is Mark most likely communicating regarding the system status?
A '503 – Service Unavailable' error indicates a significant issue preventing the microservice from functioning correctly. This message clearly signals a failure requiring immediate investigation and resolution to restore service availability. It's crucial to understand that 503 errors are not routine issues.
12 / 16
During a sprint review, the Scrum Master asks the development team to provide a concise status update. Which of the following best describes what 'Green' typically signifies in this context?
'Green' in Agile status reporting usually indicates a healthy sprint. It signifies that all tasks are proceeding as planned, deadlines are being met, and there aren't significant roadblocks hindering the team's progress. The misconception is often equating 'green' with simply 'progress,' which isn't the core meaning within a Scrum context.
13 / 16
John, a developer, is writing a comment on a code review for Emily. Emily has just submitted a pull request to update the user authentication module. John writes: 'Looks good, but can you add more logging around the password hashing step? We need to ensure compliance with security best practices.' What does this comment primarily indicate about the status of the pull request?
The comment indicates that while the code appears functional, it's not yet considered 'complete'. John is requesting further investigation (logging) to address potential security concerns – a common practice when reviewing critical functionality. The use of 'needs' suggests the PR isn't ready for final approval and requires more work.
14 / 16
Maria, a product owner, sends a Slack message to her team: 'The microservice is currently displaying a 502 Bad Gateway error. We're seeing this primarily during peak usage times and suspect it might be related to resource contention.' What does Maria's message suggest about the system's status?
The message describes an error (502) occurring under specific conditions (peak usage). This aligns with 'Yellow' status, signifying a potential issue requiring investigation. 'Red' would indicate a full outage; 'Green' and 'Blue' are incorrect because the system is clearly not operating as expected.
15 / 16
David, a senior engineer, is updating his team during a daily standup. He says: 'The build is passing, but we're seeing intermittent failures in our integration tests – specifically around the new payment gateway integration. We've identified a race condition.' What does David's statement primarily communicate about the project's status?
David's description of 'intermittent failures' and a specific technical problem (race condition) strongly suggests a 'Yellow' status. This indicates a potential impediment to the sprint goal that needs immediate investigation and resolution. 'Green' implies everything is working perfectly; 'Orange' is too optimistic given the test failures.
16 / 16
Sarah, a developer, receives an API response from a third-party service. The response includes this JSON: `{"status": "error", "code": 403, "message": "Forbidden - Insufficient Permissions"}`. What does this API response likely indicate about the system's status?
The response includes an 'error' status and a specific error code (403). The message clearly states 'Insufficient Permissions,' indicating that the system or user lacked the necessary authorization to access the requested resource. This is a common API error, signifying a problem with the request itself.
What will I learn from the "Status Reporting Vocabulary" exercise?
Practice status reporting vocabulary: RAG status, Amber risk communication, weekly steering committee updates, dependency risks, and executive status formats.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 16 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Stakeholder Management exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss stakeholder management topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 16 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Stakeholder Management exercises?
See the full Stakeholder Management exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.