Comments on: What To Do When a Developer Says “That’s Impossible” https://www.bridging-the-gap.com/what-to-do-when-a-developer-tells-you-thats-impossible/ We'll Help You Start Your Business Analyst Career Wed, 15 Jun 2022 19:41:20 +0000 hourly 1 https://wordpress.org/?v=6.6.2 By: Laura Brandenburg https://www.bridging-the-gap.com/what-to-do-when-a-developer-tells-you-thats-impossible/comment-page-1/#comment-429045 Fri, 10 Aug 2012 20:03:31 +0000 http://www.bridging-the-gap.com/?p=809#comment-429045 In reply to catalina.

Thanks Catalina!

]]> By: catalina https://www.bridging-the-gap.com/what-to-do-when-a-developer-tells-you-thats-impossible/comment-page-1/#comment-429044 Wed, 01 Aug 2012 20:00:56 +0000 http://www.bridging-the-gap.com/?p=809#comment-429044 Hi Laura, I subscribed to your lessons a few days ago and I just went through the 2nd lesson and this article. Amazing! I think your lessons contain useful, not only interesting information. I am happy I subscribed, I congratulate you and I am so looking forward to read all of your articles!

]]> By: EFFECTIVE COMMUNICATION –A MUST FOR A BUSINESS ANALYST | Anisan Technologies https://www.bridging-the-gap.com/what-to-do-when-a-developer-tells-you-thats-impossible/comment-page-1/#comment-429043 Thu, 12 Jan 2012 05:35:55 +0000 http://www.bridging-the-gap.com/?p=809#comment-429043 […] overcome this communication barrier between analysts and developers, one tactic is to use at a cross-roads between requirements and design is to take a couple of steps […]

]]> By: Laura Brandenburg https://www.bridging-the-gap.com/what-to-do-when-a-developer-tells-you-thats-impossible/comment-page-1/#comment-429042 Tue, 10 Aug 2010 15:01:25 +0000 http://www.bridging-the-gap.com/?p=809#comment-429042 Madalina,

I am definitely familiar with that situation but I don’t necessarily see it as a problem unless people who do not care about those details are in the meeting. When you say “over-complicate” are you speaking from your business expertise or technical expertise?

In my experience, developers and technical architects often need to have long discussions about possibilities and details to fully understand the technical scope of the problem. If you feel that you or your business stakeholders are being unnecessarily dragged through these discussions, one solution is to make someone from the IT side accountable for holding and leading the technical discussion, then coming back and collaborating with the larger group on the technical possibilities related to solving a specific business problem.

]]> By: Madalina https://www.bridging-the-gap.com/what-to-do-when-a-developer-tells-you-thats-impossible/comment-page-1/#comment-429041 Tue, 10 Aug 2010 14:45:15 +0000 http://www.bridging-the-gap.com/?p=809#comment-429041 I agree that should be collaborative discussions as early as possible.

But a challenge I’m facing when involving technical teams is that discussions suddenly get very detailed and technical.
Certain technical people tend to over-complicate things and the entire scope of the meeting is screwed: hours of talking about all the details. This is even worst when there is a cross-functional requirement when more teams need to be involved.

Anyone familiar with this type of situation? 🙂

Thanks for all the great posts!

]]>