AAC Stakeholder Engagement & Collaboration Flashcards
6 cards from real AAC practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 AAC Stakeholder Engagement & Collaboration flashcards as text
In agile analysis, what is the primary purpose of a stakeholder map?
Answer: To identify, categorize, and prioritize stakeholders by influence and interest
A stakeholder map helps agile analysts identify and categorize stakeholders by their level of influence and interest so engagement efforts can be prioritized appropriately.
Which technique is most effective for eliciting requirements from a large, geographically dispersed stakeholder group in an agile project?
Answer: Collaborative online workshops using digital facilitation tools
Collaborative online workshops using digital facilitation tools (e.g., Miro, MURAL) enable real-time participation and consensus-building across distributed stakeholders.
What does the term 'product champion' refer to in agile stakeholder collaboration?
Answer: A stakeholder who advocates for the product and helps remove organizational obstacles
A product champion is a stakeholder who actively supports the product, promotes its value, and helps overcome internal resistance or obstacles.
When a key stakeholder consistently misses sprint reviews, what is the recommended agile analysis approach?
Answer: Engage the stakeholder to understand their constraints and adjust communication channels
Agile analysts should proactively engage absent stakeholders to understand barriers and adapt communication methods to ensure continued collaboration.
Which agile artifact is most useful for communicating the product's progress and upcoming priorities to stakeholders?
Answer: Product roadmap
The product roadmap provides stakeholders with a high-level, time-oriented view of the product's strategic direction and upcoming priorities.
In the AAC body of knowledge, 'shared understanding' between analysts and stakeholders is best achieved through:
Answer: Frequent, collaborative conversations and visual modeling
Shared understanding in agile analysis is built through ongoing, collaborative conversations and visual tools like wireframes and process maps rather than static documents.