Full-Stack Development Communication & Stakeholder Relations 2 — Questions and Answers
Question 1: A client requests a feature mid-sprint that would take 3 days but the sprint ends in 2. What is the best response?
- Add it to the current sprint and drop a lower-priority task
- Acknowledge the request, add it to the backlog, and discuss prioritization with the product owner (Correct answer)
- Refuse the request and tell the client to wait for the next release cycle
- Implement it overnight without telling the team to meet expectations
Correct answer: Acknowledge the request, add it to the backlog, and discuss prioritization with the product owner
Mid-sprint scope changes should go through the backlog and product owner to protect sprint goals and maintain transparency.
Question 2: Which technique is most effective when presenting a technical architecture decision to non-technical executives?
- Use UML diagrams with full notation to demonstrate rigor
- Lead with business outcomes, risks, and cost before explaining technical details (Correct answer)
- Send a detailed written spec and ask them to review it before the meeting
- Defer all questions to the engineering lead to avoid miscommunication
Correct answer: Lead with business outcomes, risks, and cost before explaining technical details
Executives prioritize business impact, so framing technical choices around outcomes first ensures the conversation stays relevant to their concerns.
Question 3: A stakeholder complains that deployments always break something. What communication step should happen FIRST?
- Explain the complexity of the system to set realistic expectations
- Schedule a post-mortem and share incident data to identify the real failure pattern (Correct answer)
- Promise to add more testing without investigating the root cause
- Disable continuous deployment to reduce the frequency of changes
Correct answer: Schedule a post-mortem and share incident data to identify the real failure pattern
Data-driven post-mortems surface actual patterns rather than assumptions, enabling targeted fixes and rebuilding stakeholder trust.
Question 4: When writing a technical proposal for a new API, which section is most important for a business stakeholder audience?
- Endpoint schema and HTTP status codes
- Authentication implementation details
- Executive summary covering ROI, timeline, and risk (Correct answer)
- Database indexing strategy
Correct answer: Executive summary covering ROI, timeline, and risk
Business stakeholders evaluate proposals on value, cost, and risk rather than implementation specifics.
Question 5: A developer estimates 2 weeks for a feature but the sales team promises the client delivery in 5 days. What should the full-stack developer do?
- Work overtime to match the sales promise without escalating
- Immediately escalate the discrepancy to management with the accurate estimate and impact (Correct answer)
- Renegotiate scope with the client directly without involving sales
- Accept the deadline and skip code review to save time
Correct answer: Immediately escalate the discrepancy to management with the accurate estimate and impact
Escalating timeline conflicts with accurate data allows leadership to make informed decisions and realign client expectations before commitments harden.
Question 6: What is the primary purpose of a sprint review meeting from a stakeholder communication standpoint?
- To evaluate individual developer performance
- To allow stakeholders to inspect the increment and provide feedback that shapes the backlog (Correct answer)
- To plan the technical tasks for the next sprint
- To report bugs discovered during QA
Correct answer: To allow stakeholders to inspect the increment and provide feedback that shapes the backlog
The sprint review creates a feedback loop between the team and stakeholders to ensure the product evolves in alignment with business needs.
Question 7: A stakeholder insists on a specific technical solution (e.g., 'use MongoDB') without understanding the tradeoffs. How should a senior full-stack developer respond?
- Implement MongoDB as requested to avoid conflict
- Ignore the suggestion and implement the preferred solution without informing the stakeholder
- Present a comparison of options with tradeoffs tied to the project's requirements, then let the stakeholder make an informed decision (Correct answer)
- Escalate immediately to HR as stakeholder overreach
Correct answer: Present a comparison of options with tradeoffs tied to the project's requirements, then let the stakeholder make an informed decision
Presenting objective tradeoffs respects the stakeholder's authority while ensuring the decision is informed by technical realities.
Full-Stack Development Communication & Stakeholder Relations 2
A client requests a feature mid-sprint that would take 3 days but the sprint ends in 2.
What is the best response?