Full-Stack Development Communication & Stakeholder Relations 3

Question 1

Which of the following best describes 'active listening' in a stakeholder requirements meeting?

Accepted Answer

Paraphrasing the stakeholder's points and asking clarifying questions to confirm understanding

Answer

Active listening involves paraphrasing and clarifying to verify understanding, reducing the risk of building the wrong thing.

Question 2

A remote team member consistently misses async status updates in Slack. What is the most effective corrective approach?

Accepted Answer

Have a private conversation to understand their barriers and agree on a workable communication norm

Answer

Understanding the individual's constraints and co-creating a solution is more sustainable than punitive or team-wide overreactions.

Question 3

When should a developer send a written summary AFTER a stakeholder meeting?

Accepted Answer

Always, to document decisions made, open questions, and next steps

Answer

Written follow-ups create a shared record of decisions and accountability for action items, reducing ambiguity.

Question 4

A product manager keeps adding 'just small tweaks' to a completed feature without a formal change process. This is an example of what?

Accepted Answer

Scope creep

Answer

Informal, incremental additions to agreed scope without going through a change process is the definition of scope creep.

Question 5

What is the most effective way to communicate a critical production incident to business stakeholders?

Accepted Answer

Send regular brief status updates at defined intervals, even if there is no resolution yet

Answer

Regular cadenced updates manage anxiety and keep stakeholders informed without requiring developers to context-switch during an active incident.

Full-Stack Development Practice Test