Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

PMI Exam PMI-200 Topic 9 Question 50 Discussion

Actual exam question for PMI's PMI-200 exam
Question #: 50
Topic #: 9
[All PMI-200 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Louann
8 months ago
Exactly, it's all about finding the right balance. I'd be wary of just agreeing to avoid documentation, that could cause issues down the line. But I also don't think we need a huge, comprehensive design doc for every user story. Maybe a quick whiteboard sketch would be enough in this case.
upvoted 0 times
...
Serina
8 months ago
Haha, 'Agile, no documentation?' That's a classic misconception. I'd go with option B - explain that documentation is not forbidden, it's just not the primary focus. As long as it's adding value and not slowing the team down, a little documentation can be useful.
upvoted 0 times
...
Mindy
8 months ago
I agree, it's a tough one. I think the ScrumMaster should try to find a middle ground. Maybe they could suggest starting with a lightweight design document, just to capture the key aspects, and then focus on the actual implementation.
upvoted 0 times
Tish
8 months ago
B) Explain that interactions are valued over documentation, but documentation is not forbidden.
upvoted 0 times
...
Ahmed
8 months ago
A) Agree that documentation should be avoided, since it slows the progress of the team.
upvoted 0 times
...
Miles
8 months ago
B) Explain that interactions are valued over documentation, but documentation is not forbidden.
upvoted 0 times
...
Galen
8 months ago
A) Agree that documentation should be avoided, since it slows the progress of the team.
upvoted 0 times
...
Allene
8 months ago
B) Explain that interactions are valued over documentation, but documentation is not forbidden.
upvoted 0 times
...
...
Maia
8 months ago
This is a tricky question. I can see both sides of the argument. On one hand, Agile does emphasize interactions over documentation. But on the other hand, some level of documentation can be helpful, especially for complex systems.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77