Full-Stack Development Communication & Stakeholder Relations 4 — Questions and Answers
Question 1: A client's highest-priority feature conflicts with a technical constraint the team discovered. What is the correct order of actions?
- Implement a workaround without telling the client to avoid alarm
- Ignore the constraint and build what was requested
- Explain the constraint, quantify the risk of ignoring it, and propose two or three alternative approaches (Correct answer)
- Cancel the feature entirely and refund the client
Correct answer: Explain the constraint, quantify the risk of ignoring it, and propose two or three alternative approaches
Presenting options with trade-offs respects the client's decision-making authority while ensuring they understand the technical reality.
Question 2: Which asynchronous communication format is best suited for explaining a complex API integration decision to a distributed team?
- A quick Slack message with a link to the PR
- A structured written document with context, decision, alternatives considered, and consequences (ADR format) (Correct answer)
- A voice memo recorded on a phone
- An impromptu Zoom call at a convenient time for the sender only
Correct answer: A structured written document with context, decision, alternatives considered, and consequences (ADR format)
Architecture Decision Records (ADRs) capture the reasoning behind decisions in a format that remains useful long after the decision is made.
Question 3: What does 'managing up' mean in a full-stack development context?
- Reporting bugs to senior engineers
- Proactively communicating risks, progress, and needs to managers and stakeholders before they ask (Correct answer)
- Asking for a promotion during performance reviews
- Escalating every decision to leadership to avoid responsibility
Correct answer: Proactively communicating risks, progress, and needs to managers and stakeholders before they ask
Managing up means keeping leadership informed proactively so they can support the team and make timely decisions.
Question 4: A stakeholder approves a design in a wireframe review, but later says 'this isn't what I meant.' How should the team respond?
- Rebuild the feature at no additional cost since it's the team's communication failure
- Review the wireframe approval record, identify the gap between expectation and output, and negotiate a change order if scope expanded (Correct answer)
- Blame the stakeholder for approving incorrect wireframes
- Restart the project from scratch to rebuild trust
Correct answer: Review the wireframe approval record, identify the gap between expectation and output, and negotiate a change order if scope expanded
Documented approvals protect the team, while honest gap analysis and change-order negotiation address evolving requirements fairly.
Question 5: In a RACI matrix for a software project, what does the 'C' (Consulted) role mean?
- The person responsible for completing the task
- Someone whose input is sought before decisions are made but who does not do the work (Correct answer)
- The person who signs off on deliverables
- Someone who receives updates after decisions are made
Correct answer: Someone whose input is sought before decisions are made but who does not do the work
Consulted parties provide expertise or feedback during a task but are not accountable for its outcome.
Question 6: A developer disagrees with a product decision but the decision has been finalized. What is the professional course of action?
- Implement the decision as requested while documenting the concern in a brief written note for the record (Correct answer)
- Refuse to implement until the decision is revisited
- Implement it incorrectly to demonstrate why it was a bad idea
- Announce the disagreement publicly to the broader team
Correct answer: Implement the decision as requested while documenting the concern in a brief written note for the record
Implementing finalized decisions while creating a paper trail of concerns is professional and keeps the project moving without suppressing legitimate feedback.
Question 7: What is the main benefit of maintaining a public-facing project status page during a long-running outage?
- It reduces the number of inbound support tickets and individual stakeholder inquiries (Correct answer)
- It improves the SEO of the company website
- It satisfies legal requirements for uptime SLAs
- It allows the engineering team to avoid holding a post-mortem
Correct answer: It reduces the number of inbound support tickets and individual stakeholder inquiries
A status page centralizes information, reducing the volume of direct inquiries that would otherwise interrupt the team trying to resolve the outage.
Full-Stack Development Communication & Stakeholder Relations 4
A client's highest-priority feature conflicts with a technical constraint the team discovered.
What is the correct order of actions?