Mobile App Design Communication & Stakeholder Relations 3 — Questions and Answers
Question 1: A stakeholder keeps changing requirements mid-sprint. What process improvement would most reduce this disruption?
- Lock the sprint backlog and enforce a change-request process (Correct answer)
- Let all changes through to keep the stakeholder happy
- Cancel the sprint whenever a change is requested
- Ignore the stakeholder until the sprint ends
Correct answer: Lock the sprint backlog and enforce a change-request process
A formal change-request process protects sprint commitments while giving stakeholders a legitimate path for changes.
Question 2: What is the primary purpose of a design review meeting in a mobile app project?
- To assign blame for missed deadlines
- To gather cross-functional feedback and align on design decisions before development (Correct answer)
- To show finished code to the client
- To replace user research
Correct answer: To gather cross-functional feedback and align on design decisions before development
Design reviews surface cross-functional concerns early, reducing costly rework during development.
Question 3: A QA tester finds a usability issue that the designer considers out of scope. Who should resolve this disagreement?
- The developer, by deleting the feature
- The product owner, using the agreed definition of done (Correct answer)
- The marketing team
- The end user via a public vote
Correct answer: The product owner, using the agreed definition of done
The product owner uses the definition of done and project scope to arbitrate disputes between team members.
Question 4: What is an effective way to keep executive stakeholders informed without overwhelming them with detail?
- Send them every Jira ticket update
- Provide a concise weekly status dashboard with key metrics and blockers (Correct answer)
- Schedule daily three-hour meetings
- Copy them on every team Slack message
Correct answer: Provide a concise weekly status dashboard with key metrics and blockers
Executives need high-level summaries of progress, risks, and blockers, not granular task details.
Question 5: During a user-testing session, a stakeholder wants to interrupt and coach the participant. What should the facilitator do?
- Allow it to make the stakeholder feel involved
- Politely ask the stakeholder to observe silently and note questions for debrief (Correct answer)
- End the session immediately
- Remove the stakeholder from the building
Correct answer: Politely ask the stakeholder to observe silently and note questions for debrief
Coaching participants biases results; observers should remain silent and debrief after the session.
Question 6: Which type of documentation is most useful for onboarding a new developer to an ongoing mobile app project?
- A collection of old meeting recordings with no index
- A structured README with architecture overview, setup steps, and design links (Correct answer)
- A stack of printed wireframes
- The CEO's original pitch deck
Correct answer: A structured README with architecture overview, setup steps, and design links
A structured README with setup instructions and context helps new team members become productive quickly.
Question 7: A client sends conflicting feedback in separate email threads. What is the best way to resolve this?
- Implement the most recent email and ignore the rest
- Consolidate all feedback into one document and schedule a call to confirm priorities (Correct answer)
- Delete all emails and start over
- Implement all feedback simultaneously regardless of conflicts
Correct answer: Consolidate all feedback into one document and schedule a call to confirm priorities
Consolidating feedback and confirming priorities with the client prevents wasted effort on conflicting directions.
Mobile App Design Communication & Stakeholder Relations 3
A stakeholder keeps changing requirements mid-sprint.
What process improvement would most reduce this disruption?