Front End Development Communication & Stakeholder Relations 2 — Questions and Answers
Question 1: A stakeholder asks why a feature is taking longer than expected. What is the most professional response?
- Explain technical blockers with impact on timeline and propose a revised estimate (Correct answer)
- Tell them it's a complex problem they wouldn't understand
- Promise it will be done soon without committing to a date
- Redirect blame to another team member
Correct answer: Explain technical blockers with impact on timeline and propose a revised estimate
Transparent communication about blockers with a concrete revised estimate maintains trust and sets realistic expectations.
Question 2: Which artifact is most effective for aligning stakeholders on UI behavior before development begins?
- An interactive prototype (Correct answer)
- A finished codebase
- A verbal description in a meeting
- A post-launch retrospective report
Correct answer: An interactive prototype
Interactive prototypes let stakeholders experience proposed behavior and give concrete feedback before costly development starts.
Question 3: A client wants a feature that conflicts with established accessibility standards. What should a front-end developer do?
- Explain the legal and UX risks, propose an accessible alternative that meets the client's goal (Correct answer)
- Build it as requested since the client has final authority
- Refuse the request without explanation
- Log a bug ticket and move on
Correct answer: Explain the legal and UX risks, propose an accessible alternative that meets the client's goal
Educating clients about accessibility risks while offering alternatives fulfills both professional duty and client goals.
Question 4: What is the primary purpose of a 'Definition of Done' agreed upon with stakeholders?
- To create a shared understanding of when a feature is truly complete (Correct answer)
- To assign blame when features ship late
- To restrict developers from adding enhancements
- To replace design mockups
Correct answer: To create a shared understanding of when a feature is truly complete
A Definition of Done eliminates ambiguity by giving both developers and stakeholders identical criteria for feature completion.
Question 5: During a sprint review, a non-technical product manager asks what 'lazy loading' is. The best response is to:
- Explain it using a real-world analogy, then show the performance gain in the demo (Correct answer)
- Provide a detailed technical explanation with code examples
- Say it's too technical to explain quickly
- Skip the explanation and move to the next demo item
Correct answer: Explain it using a real-world analogy, then show the performance gain in the demo
Translating technical concepts into relatable analogies helps non-technical stakeholders understand value without overwhelming them.
Question 6: A designer and developer disagree on implementing a hover effect that may hurt performance. What is the best path forward?
- Run a quick performance test, share data, and collaboratively decide based on impact (Correct answer)
- The developer overrides the designer since performance is their domain
- The designer's vision always takes precedence
- Escalate immediately to a manager
Correct answer: Run a quick performance test, share data, and collaboratively decide based on impact
Data-driven discussion respects both roles and leads to solutions that balance aesthetics and performance.
Question 7: Which communication practice best reduces scope creep during a front-end project?
- Documenting and getting sign-off on requirements before starting development (Correct answer)
- Adding all requested features immediately to please stakeholders
- Avoiding meetings to focus on coding
- Keeping requirements informal and flexible
Correct answer: Documenting and getting sign-off on requirements before starting development
Formal requirement sign-off creates a clear baseline that makes additional requests visible as scope changes requiring negotiation.
Front End Development Communication & Stakeholder Relations 2
A stakeholder asks why a feature is taking longer than expected.
What is the most professional response?