PMI Exam PMI-200 Topic 8 Question 54 Discussion

Actual exam question for PMI's PMI-200 exam

Question #: 54
Topic #: 8

During iteration planning, the team is discussing the design for a user story. A team member states that a design document should be started since the system is complex in nature. Another team member responds that in Agile there is no documentation. How should the ScrumMaster respond?

AAgree that documentation should be avoided, since it slows the progress of the team.

BExplain that interactions are valued over documentation, but documentation is not forbidden.

CAsk the manager if the technical processes mandate that designs be documented.

DAsk the Product Owner if it is acceptable for the resources to spend time on documentation.

Show Suggested Answer

Suggested Answer: B

by Justine at Mar 10, 2024, 03:08 PM

Limited Time Offer

25%

Off

Get Premium PMI-200 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Refugia

12 days ago

You know, this reminds me of that classic Dilbert comic where the pointy-haired boss says 'No more documents! They slow us down!' And then Dilbert's like, 'But how will we know what to do?' Haha, classic.

upvoted 0 times

...

Denise

13 days ago

Hmm, I don't know. I can see both sides of this. On one hand, the Agile manifesto does say 'working software over comprehensive documentation.' But on the other hand, some documentation can actually help us work more efficiently, especially for a complex system. This is a tricky one.

upvoted 0 times

Louisa

10 hours ago

B) Explain that interactions are valued over documentation, but documentation is not forbidden.

upvoted 0 times

...

Yen

14 days ago

Hah, yeah, that's totally relevant here! Look, the ScrumMaster needs to find a way to balance the need for documentation with the Agile principles. Maybe they can compromise and say we'll do just enough documentation to keep us on track, but not get carried away with it.

upvoted 0 times

...

Scot

15 days ago

Whoa, hold on a second! This is a classic Agile vs. documentation debate. I mean, we all know that Agile values working software over comprehensive documentation, but that doesn't mean we can totally ignore it, right? This is a complex system, after all.

upvoted 0 times

...