New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Scrum PSD Exam - Topic 4 Question 82 Discussion

Actual exam question for Scrum's PSD exam
Question #: 82
Topic #: 4
[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.


by Ashlyn at Nov 22, 2025, 10:04 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Chaya
12 hours ago
Wait, are we really saying one bug per report is bad?
upvoted 0 times
...
Joesph
6 days ago
Totally agree, blaming others doesn't help!
upvoted 0 times
...
Annalee
11 days ago
Ah, the joys of debugging code based on a bug report that reads like a Shakespearean sonnet.
upvoted 0 times
...
Keva
16 days ago
D and E? Psh, those are for amateurs. Real pros make their bug reports as cryptic as possible.
upvoted 0 times
...
Trevor
21 days ago
I'd add "Lack of coffee stains" as a fourth attribute. How else will the devs know it's a real bug report?
upvoted 0 times
...
Beckie
26 days ago
Vague statements, assigning blame, and generic titles - the holy trinity of bad bug reports!
upvoted 0 times
...
Clorinda
1 month ago
A, B, and C are the correct attributes of a bad bug report.
upvoted 0 times
...
Kati
1 month ago
I feel like one bug per report is a good practice, but I’m not entirely confident about the other options.
upvoted 0 times
...
Stevie
1 month ago
Generic titles seem like a big issue too, but I can't recall if they were always listed as a top three in our practice tests.
upvoted 0 times
...
Hollis
2 months ago
I remember practicing a question like this, and I think assigning blame is definitely a bad attribute.
upvoted 0 times
...
Tyra
2 months ago
Hmm, I'm a little confused on this one. I know simple and repeatable reproduction steps are good, but I'm not sure if the other options are all bad. I'll have to review my notes and make sure I understand the key differences.
upvoted 0 times
...
Alesia
2 months ago
Easy peasy! Vague statements, assigning blame, and generic titles are the three bad attributes. I've seen enough bad bug reports to know those are the classic no-nos. Time to put that knowledge to use.
upvoted 0 times
...
Corrinne
2 months ago
A) and C) are definitely bad attributes.
upvoted 0 times
...
Kendra
2 months ago
I think vague statements are a big issue.
upvoted 0 times
...
Herschel
3 months ago
I think vague statements definitely make a bug report bad, but I'm not sure about the others.
upvoted 0 times
...
Mozell
3 months ago
Okay, let's see. Vague statements and generic titles make sense as bad attributes. But I'm not sure about the other one - is assigning blame really a bad thing? I'll have to double-check that.
upvoted 0 times
...
Eden
3 months ago
Hmm, this is a tricky one. I'm not sure if I should pick the opposite of the good attributes, or if there are other specific bad attributes I'm missing. I'll have to think this through carefully.
upvoted 0 times
...
Shayne
3 months ago
I think I know this one - vague statements, assigning blame, and generic titles seem like the clear bad attributes. I'll make sure to avoid those in my bug reports.
upvoted 0 times
Antione
2 months ago
I agree! Vague statements really confuse things.
upvoted 0 times
...
...

Save Cancel