Should client's comment be considered offensive?

By pmpteam07 ·
My team is working towards building a sofware product for xyz company. All the features in the product are built as specified in the SRS. However, an additional condition that was required was not included in the SRS. This was not caught during the multiple number of reviews that was done by the client.

During testing, the client who reviewed the document N number of times has spotted that this feature is missing and his comment is "The feature is not there in the SRS. This is a stupid way of writing the SRS"..thus indirectly blaming and calling the author of the SRS a stupid.

Should the clients comments be considered offensive? What is the right way to convey to the client that such comments are not acceptable because the requirements are provided by them and reviews are also done by them.

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Let it go............

by ThumbsUp2 In reply to Should client's comment b ...

Personally, I would let it go. If you must say something, tell them thank you for their observations and that you will strive to improve the SRS format in the future. You might even ask for their input on how to improve it.

Let's face it. Stuff happens during developement. Things get overlooked a number of times during the process. But, when something IS found, you don't want to "turn them off" by commenting back that their comments are not acceptable. Just swallow it, strive to improve it, and move on with life.

Collapse -

client comment

by ladytech2010 In reply to Should client's comment b ...

Clients say things all the time. It's not your place to tell them they are being offensive, short of swearing, breaking the law, refusing to pay, or doing harm. It's your place to let certain things slide, and try to find a way to make it work. If you or your team heard about it during requirements analysis, then it was both your responsibilities to include it. Perhaps suggest a future release with that included at a lesser cost. It would have cost them anyway, had it been included in the first place.

We have a sign in our office that says "Pull up your big girl panties and deal with it." Crude, but an effective reminder that we sometimes have to do just that.

Collapse -

SOP: The Four Agreements #2

by longtex In reply to Should client's comment b ...

The second of the Four Agreements is "Never take anything personally".

You can't control what other people think, say, or do, so it is totally and completely a waste of your precious time and energy to worry about or work at changing anything anyone else says or does.

It says something about them, not something about you, so **** it off... better yet, don't even let it alight on you in the first place.

If you insist on thinking about it at all, think about it from the other side - probably the poor f*cker has an internal demon poking him in a soft spot and telling him he screwed up because he reviewed it N times and didn't notice it wasn't there... but that says something about him, not about you.

If it becomes an issue about getting paid, you have the hammer anyway, so get up, wipe the blood off your face, spit, smile a big one, and get your *ss back in the game.

Back to Software Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums