MENU
User documentation is part of your Definition of Done. However, there are not enough technical writers for all teams. Your Scrum Team does not have a technical writer. What needs to be done?
(choose the best answer)
Suggested Answer: E
Get Premium PSM-II Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
The Development Team owns the Definition of ''Done'' and is accountable for the quality of the Product Backlog items.
34 comments · newest first
SH
Shawnta
11 months ago
Wait, a separate team for docs? That seems like overkill.
FL
Florinda
11 months ago
Totally agree with A, we can't leave it undone!
SE
Serina
11 months ago
C sounds interesting, but is it really feasible?
RO
Roxane
11 months ago
I disagree, B just delays the problem.
RO
Rosenda
11 months ago
A is the way to go! Developers should handle it.
YV
Yvonne
12 months ago
I think the Developers should definitely be involved in writing documentation, but I'm not sure if they have the time. Option A seems like the best choice, though.
ER
Erick
12 months ago
Forming a separate team sounds tempting, but I wonder if that would really align with Scrum principles. It feels like it could complicate things.
CE
Cecily
12 months ago
I'm not entirely sure, but I feel like letting documentation pile up until the end could lead to issues. I think we practiced a question similar to this.
GI
Gilberto
1 year ago
I remember we discussed how the Scrum Team is responsible for all aspects of the product, including documentation. So, I think option A makes sense.
LU
Lura
1 year ago
I'm leaning towards option A. The Developers should be able to handle the user documentation, even if it's not their main focus. It's part of the Definition of Done, so they need to make it happen.
LE
Leslie
1 year ago
Forming a separate team of technical writers sounds like a good idea, but I'm not sure how that would work in practice. Would the writers just be on-call for whenever the teams need them? Seems like it could get complicated.
LA
Lajuana
1 year ago
I think the best approach is to have the Developers write the user documentation. They know the product the best, and it's part of the Definition of Done, so they need to take ownership of it.
HY
Hyman
1 year ago
This is a tricky one. I'm not sure if the Developers should be responsible for the user documentation, since that's not their primary role. But letting it accumulate until the end doesn't seem like a great solution either.
TA
Tamar
1 year ago
This looks straightforward. I'll just need to create the install.yml file with the required URLs and role names, then run the ansible-galaxy command to install the roles.
EV
Eva
1 year ago
Hmm, I'm a bit confused. Creating a copy of the table with a different data type seems like a lot of work. I wonder if there's a simpler solution that doesn't require duplicating the data.
LO
Lorrine
1 year ago
Why not just get the Developers to write the documentation and then have the technical writers proofread and edit it? That way, they can focus on quality while the Developers do the heavy lifting.
ID
Idella
1 year ago
I'm just imagining the Developers trying to write user documentation. It's going to be like a bunch of toddlers trying to assemble IKEA furniture - hilarious, but not very useful for the users!
RE
Refugia
1 year ago
A) Your Scrum Team is still accountable for creating user documentation. In this case, the Developers will write it.
SH
Sheldon
1 year ago
B) Let the user documentation remain undone and accumulate until after the last development Sprint. It will then be done by any available technical writers.
TR
Trina
1 year ago
A) Your Scrum Team is still accountable for creating user documentation. In this case, the Developers will write it.
GL
Glory
1 year ago
A separate team of technical writers sounds like a good idea, but the 'first in, first out' approach could lead to imbalanced workloads and delays. There must be a better way to manage the demand.
PE
Peggie
1 year ago
A separate team of technical writers could help balance the workload and prevent delays.
RE
Refugia
1 year ago
C) Form a separate team of technical writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.
JO
Joesph
1 year ago
A) Your Scrum Team is still accountable for creating user documentation. In this case, the Developers will write it.
AN
Antonio
1 year ago
Letting the user documentation accumulate until the end is a recipe for disaster. That's just kicking the can down the road and will create a huge backlog of work.
AN
Annamae
1 year ago
C) Form a separate team of technical writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.
AN
Annamae
1 year ago
A) Your Scrum Team is still accountable for creating user documentation. In this case, the Developers will write it.
MI
Mila
2 years ago
In that case, the team can collaborate with the Product Owner to ensure the documentation meets the required standards.
EU
Eulah
2 years ago
I agree that the Scrum Team is accountable for user documentation, even without a dedicated technical writer. The Developers should step up and take ownership of this task.
HE
Herman
1 year ago
A) Your Scrum Team is still accountable for creating user documentation. In this case, the Developers will write it.
NE
Nenita
1 year ago
C) Form a separate team of technical writers that will work on an on-demand basis for the various Product Owners. Work order will be first in, first out.
BR
Brice
1 year ago
A) Your Scrum Team is still accountable for creating user documentation. In this case, the Developers will write it.
EL
Eloisa
2 years ago
But what if the Developers don't have the necessary skills to write user documentation?
MI
Mila
2 years ago
A) Your Scrum Team is still accountable for creating user documentation. In this case, the Developers will write it.