Full-Stack Development Communication & Stakeholder Relations 3 — Questions and Answers
Question 1: Which of the following best describes 'active listening' in a stakeholder requirements meeting?
- Taking notes verbatim and reading them back at the end
- Paraphrasing the stakeholder's points and asking clarifying questions to confirm understanding (Correct answer)
- Staying silent and only speaking when directly asked
- Recording the meeting and transcribing it afterward
Correct answer: Paraphrasing the stakeholder's points and asking clarifying questions to confirm understanding
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?
- Remove them from the project
- Have a private conversation to understand their barriers and agree on a workable communication norm (Correct answer)
- Add their manager to every thread to apply pressure
- Switch the entire team to synchronous daily standups to enforce participation
Correct answer: Have a private conversation to understand their barriers and agree on a workable communication norm
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?
- Only when something went wrong
- Always, to document decisions made, open questions, and next steps (Correct answer)
- Only for meetings longer than one hour
- Only when the stakeholder explicitly requests it
Correct answer: Always, to document decisions made, open questions, and next steps
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?
- Agile flexibility
- Scope creep (Correct answer)
- Continuous improvement
- Backlog grooming
Correct answer: Scope creep
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?
- Wait until the issue is fully resolved before communicating anything
- Send regular brief status updates at defined intervals, even if there is no resolution yet (Correct answer)
- Communicate only technical details to demonstrate the team's competence
- Assign a developer to answer individual stakeholder calls throughout the incident
Correct answer: Send regular brief status updates at defined intervals, even if there is no resolution yet
Regular cadenced updates manage anxiety and keep stakeholders informed without requiring developers to context-switch during an active incident.
Question 6: A stakeholder asks for a status update on a delayed feature. Which response is most professional?
- 'It'll be done when it's done.'
- 'We hit a blocker with the third-party API integration; we expect to resolve it by Friday and the feature ships Monday.' (Correct answer)
- 'The engineering team is working on it.'
- 'Ask the project manager.'
Correct answer: 'We hit a blocker with the third-party API integration; we expect to resolve it by Friday and the feature ships Monday.'
Specific blocker identification plus a concrete revised timeline demonstrates accountability and gives the stakeholder actionable information.
Question 7: What is the risk of using technical jargon (e.g., 'N+1 query', 'race condition') when communicating with non-technical stakeholders?
- It makes the developer appear knowledgeable and builds credibility
- It creates misunderstanding and may cause the stakeholder to make poorly-informed decisions (Correct answer)
- Non-technical stakeholders generally learn the terminology quickly
- It is required for formal documentation purposes
Correct answer: It creates misunderstanding and may cause the stakeholder to make poorly-informed decisions
Jargon excludes non-technical stakeholders from the conversation and can lead to misaligned expectations or decisions.
Full-Stack Development Communication & Stakeholder Relations 3
Which of the following best describes 'active listening' in a stakeholder requirements meeting?