|
The requirements process at its best is a negotiation - we make a point of trying to clarify what a sumbitter is asking for. And if we, at the first vetting, think a request should be rejected as already provided or probably won't be done, we still ask if the submitter wants to press the issue.
That continues throughout the process - again, at its best. This can take more time, as well.
On 5/12/2015 6:48 AM, rob@xxxxxxxxx wrote:
I often submit them through both. Hey, I love COMMON. They do great work. That being said, I once had a requirement totally reworded to something not even close to what I asked. Confusion? Or part of someone else's desire to get work done on their pet requirement, I don't know. Granted, that was a couple of decades back. I'm just not a big fan of middlemen. Or let's say that some requirements committee says that DB2 parity is not quite as high a priority as numerous other items and puts your requirement way down on the bottom. I may agree with them but you may not. I guess the value of COMMON helps if they put your requirement at the top. :-) Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
