Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Scrum Exam PSD Topic 2 Question 67 Discussion

Actual exam question for Scrum's PSD exam
Question #: 67
Topic #: 2
[All PSD Questions]

Which are three attributes of a bad bug report?

Show Suggested Answer Hide Answer
Suggested Answer: A, B, C

you don't want to blame anyone, have vague titles of make vague statements. It needs to be clear and constructive, and focussed on one specific problem. It should als not contain feature requests.


Contribute your Thoughts:

Lindsey
9 months ago
A, B, and C are definitely no-nos. A bug report should be clear, blame-free, and specific. Anything less is just a waste of time.
upvoted 0 times
...
Maricela
9 months ago
E is a tricky one. I can see the argument for keeping one bug per report, but sometimes related issues can be better addressed together.
upvoted 0 times
Jerry
8 months ago
E is a tricky one. I can see the argument for keeping one bug per report, but sometimes related issues can be better addressed together.
upvoted 0 times
...
Leonora
8 months ago
C) Generic titles
upvoted 0 times
...
Kara
9 months ago
B) Assigning blame
upvoted 0 times
...
Van
9 months ago
A) Vague statements or untested assumptions
upvoted 0 times
...
...
Jesus
9 months ago
I think D is actually a good thing for a bug report. Simple and repeatable steps make it easier to reproduce and fix the issue.
upvoted 0 times
...
Lezlie
9 months ago
Hmm, I'd say A, B, and C are definitely attributes of a bad bug report. Vague statements, blaming others, and generic titles? No thanks!
upvoted 0 times
Alaine
9 months ago
C) Generic titles
upvoted 0 times
...
Tegan
9 months ago
B) Assigning blame
upvoted 0 times
...
Marti
9 months ago
A) Vague statements or untested assumptions
upvoted 0 times
...
...
Lauran
10 months ago
Generic titles can make it hard to understand the issue, so that's another attribute of a bad bug report.
upvoted 0 times
...
Jordan
10 months ago
I agree with Annice, assigning blame is also not helpful in a bug report.
upvoted 0 times
...
Annice
10 months ago
I think vague statements or untested assumptions are definitely a sign of a bad bug report.
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