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 1 Question 61 Discussion

Actual exam question for PMI's PMI-200 exam
Question #: 61
Topic #: 1
[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:

Mirta
6 months ago
This is like a game of Tetris, except the blocks are made of bureaucracy. Gotta find the right balance, am I right?
upvoted 0 times
Ernestine
5 months ago
B) Explain that interactions are valued over documentation, but documentation is not forbidden.
upvoted 0 times
...
Luisa
5 months ago
B) Explain that interactions are valued over documentation, but documentation is not forbidden.
upvoted 0 times
...
Helaine
5 months ago
A) Agree that documentation should be avoided, since it slows the progress of the team.
upvoted 0 times
...
...
Cherry
6 months ago
I'm with the other guy. Documentation is like that annoying relative - you'd rather not deal with it, but sometimes you gotta suck it up.
upvoted 0 times
Polly
5 months ago
B) Explain that interactions are valued over documentation, but documentation is not forbidden.
upvoted 0 times
...
Verona
6 months ago
A) Agree that documentation should be avoided, since it slows the progress of the team.
upvoted 0 times
...
Dalene
6 months ago
B) Explain that interactions are valued over documentation, but documentation is not forbidden.
upvoted 0 times
...
...
Gracia
6 months ago
Should we ask the ScrumMaster for guidance on this?
upvoted 0 times
...
Delbert
6 months ago
But in Agile, we prioritize interactions over documentation.
upvoted 0 times
...
Gracia
6 months ago
I think we should start a design document for this user story.
upvoted 0 times
...
Celeste
6 months ago
Seriously, no documentation? That's like building a house without a blueprint. Agile doesn't mean we should ditch common sense.
upvoted 0 times
Ozell
5 months ago
A) Agree that documentation should be avoided, since it slows the progress of the team.
upvoted 0 times
...
Alida
5 months ago
B) Explain that interactions are valued over documentation, but documentation is not forbidden.
upvoted 0 times
...
Sueann
5 months ago
A) Agree that documentation should be avoided, since it slows the progress of the team.
upvoted 0 times
...
Nada
6 months ago
B) Explain that interactions are valued over documentation, but documentation is not forbidden.
upvoted 0 times
...
Berry
6 months ago
A) Agree that documentation should be avoided, since it slows the progress of the team.
upvoted 0 times
...
Sabine
6 months ago
B) Explain that interactions are valued over documentation, but documentation is not forbidden.
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