PMI-ACP practice question 27 of 35

Project stakeholders are finding it difficult to know the real-time status of who has been assigned to various stories and the status of each work item. Which of the following should the agile project manager do?

Full set: 482 questions
Answer options
A: Use an information radiator to help increase the transparency of work for key stakeholders. Correct answer
B: Send status updates whenever the stakeholders request them.
C: Hold Scrum meetings more frequently to ensure stakeholders are well informed.
D: Instruct the team to focus on their own assignments rather than the work of others.
Correct Answer:
A. Use an information radiator to help increase the transparency of work for key stakeholders.
Explanation

The core issue is a lack of transparency regarding work status, which is a key agile principle. An information radiator is a large, highly visible display that provides real-time information to anyone who is interested, without requiring them to ask. Examples include physical or digital Kanban boards, task boards, or dashboards showing work in progress, assignments, and status. This "pull" system allows stakeholders to get updates passively, fostering transparency and trust while minimizing interruptions to the team.

Why Incorrect

B. Sending updates on request is a reactive, "push" system that creates administrative overhead and is less efficient than a centralized, visible radiator.
C. Scrum meetings, particularly the Daily Scrum, are for the development team to coordinate their work, not for stakeholder status reporting.
D. Instructing the team to focus only on their own work is counterproductive and reduces transparency, collaboration, and collective ownership, worsening the problem.

References

1. Project Management Institute. (2017). Agile Practice Guide. Section 5.3.1, Information Radiators, p. 60. ("To share information with the team and stakeholders, agile teams use information radiators... The purpose is to have a visible, significant display that provides information without the viewer having to ask.").

2. Cockburn, A. (2001). Agile Software Development. Chapter 1, "A Cooperative Game of Invention and Communication." (Cockburn coined the term "information radiator" and describes its importance for osmotic communication).

3. Stray, V., & Moe, N. B. (2020). Understanding coordination in global software engineering: A mixed-methods study on the use of meetings and information radiators. IET Software, 14(4), 351-359. https://doi.org/10.1049/iet-sen.2019.0151 (Provides academic research on the effectiveness of information radiators for team and stakeholder coordination).

Scroll to Top