Comments on: Beyond gathering, eliciting and trawling for requirements http://www.bridging-the-gap.com/beyond-gathering-eliciting-and-trawling-for-requirements/ Advance Your Business Analysis Career Thu, 09 Feb 2012 00:08:14 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Adriana http://www.bridging-the-gap.com/beyond-gathering-eliciting-and-trawling-for-requirements/comment-page-1/#comment-9978 Adriana Thu, 28 Jul 2011 21:49:41 +0000 http://www.bridging-the-gap.com/?p=1952#comment-9978 @David: indeed, "emerge" does sound like waiting for something to happen, rather than being proactive and going through the necessary discovery process to ensure that the problem has been correctly identified and the team has developed a comprehensive understanding of the needed capabilities. @David: indeed, “emerge” does sound like waiting for something to happen, rather than being proactive and going through the necessary discovery process to ensure that the problem has been correctly identified and the team has developed a comprehensive understanding of the needed capabilities.

]]> By: David Wright http://www.bridging-the-gap.com/beyond-gathering-eliciting-and-trawling-for-requirements/comment-page-1/#comment-9977 David Wright Thu, 28 Jul 2011 21:12:53 +0000 http://www.bridging-the-gap.com/?p=1952#comment-9977 yeah, "emerge", that's a good one, like how the iceberg emerged out of the night right in front of the Titanic. Not looking at all the posts from 2009, I would say that Requirements need to be Discovered, "emerge" sounds like waiting for something to happen. yeah, “emerge”, that’s a good one, like how the iceberg emerged out of the night right in front of the Titanic.

Not looking at all the posts from 2009, I would say that Requirements need to be Discovered, “emerge” sounds like waiting for something to happen.

]]> By: Adriana http://www.bridging-the-gap.com/beyond-gathering-eliciting-and-trawling-for-requirements/comment-page-1/#comment-9975 Adriana Thu, 28 Jul 2011 19:38:34 +0000 http://www.bridging-the-gap.com/?p=1952#comment-9975 Ignacio -- in the software projects I have experience with, if you waited for requirements to "emerge", you would probably never get to a final product :-). Ignacio — in the software projects I have experience with, if you waited for requirements to “emerge”, you would probably never get to a final product :-) .

]]> By: Ignacio http://www.bridging-the-gap.com/beyond-gathering-eliciting-and-trawling-for-requirements/comment-page-1/#comment-9973 Ignacio Thu, 28 Jul 2011 19:06:12 +0000 http://www.bridging-the-gap.com/?p=1952#comment-9973 I think requirements must not be captured, we have to let them "emerge" I think requirements must not be captured, we have to let them “emerge”

]]> By: 2wtx Mastering Business Analysis » Blog Archive » Tips on how to deal with software development challenges http://www.bridging-the-gap.com/beyond-gathering-eliciting-and-trawling-for-requirements/comment-page-1/#comment-4676 2wtx Mastering Business Analysis » Blog Archive » Tips on how to deal with software development challenges Fri, 12 Feb 2010 15:16:24 +0000 http://www.bridging-the-gap.com/?p=1952#comment-4676 [...] “requirements discovery” with a different meaning from the one some of us adopt (see this article at Bridging the Gap), his points are valid and his advice will be particularly helpful for professionals with little [...] [...] “requirements discovery” with a different meaning from the one some of us adopt (see this article at Bridging the Gap), his points are valid and his advice will be particularly helpful for professionals with little [...]

]]>