In Agile and user-centered design, creating user personas is a valuable way to represent the different types of users who will interact with the application. By identifying these personas, the project manager can ensure that the development team better understands the varying needs, behaviors, and goals of different user groups.
This approach helps create a more effective and tailored user experience for the application. It also provides clear guidance to the team on how to prioritize features and functionality for diverse user groups.

When issues recur across multiple iterations, it's a strong indication that the root cause has not been addressed. The PMI Agile Practice Guide (Section 5.6 Retrospectives) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement) recommend performing root cause analysis techniques (e.g.,
5 Whys, Fishbone diagram) to ensure that the true source of recurring problems is uncovered and resolved.
* Option B is correct: identifying root causes is essential to sustainable improvements.
* Option A may help but doesn't address the underlying team-level process.
* Option C is useful after a solution is implemented but not the priority when the cause is unknown.
* Option D is helpful for tracking, but again, ineffective if the root cause is unidentified.

Transparency is key in agile. ThePMI Agile Practice Guide (Section 7.1 Communications)emphasizes the use ofinformation radiators-visual displays such as task boards, burndown charts, or Kanban boards that immediately communicate project status. These tools make progress visible to all stakeholders without needing detailed documentation.
Mike Griffiths in thePMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement)reinforces that collocated displays or shared online boardsreduce misunderstandings and keep stakeholders aligned.
* Option Dis correct: a public project board offersreal-time visibilityand promotes transparency.
* Option Acontradicts agile by emphasizing documentation over working software.
* Option Blimits visibility to a subset of stakeholders and is passive.
* Option Cdisrupts the team's daily focus-stand-ups are not intended for stakeholder participation.

In this situation, the scrum master has already escalated the issue to upper management without resolution, so it's important to collect empirical data to further demonstrate the impact of the external dependency. This data can be used to show the consequences of the dependency on the project's progress, helping upper management understand the severity of the issue. By influencing management and making them accountable for ensuring the external team delivers, the scrum master helps ensure the problem is addressed at a higher level, which is critical for long-term resolution.

Iteration reviews (or sprint reviews) are designed to demonstrate completed, potentially shippable product increments. According to the PMI Agile Practice Guide (Section 5.3 Sprint Review and Acceptance), the purpose of the iteration review is to showcase work that meets the Definition of Done (DoD) and to receive stakeholder feedback. Demonstrating incomplete or in-progress stories can mislead stakeholders about progress and reduce trust in the team.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) emphasizes the importance of showing only completed work to maintain transparency and clarity in stakeholder communication.
* Option A is correct: only completed stories should be demoed to ensure expectations are managed effectively.
* Option B and C are not part of the typical iteration review agenda unless explicitly required.
* Option D is incorrect, as it blurs the line between done and in-progress work.