Geeks With Blogs
Robert's Blog ideas about design and development
Sometimes as developers we get into disagreements (or perhaps blood feuds) with our internal customers or other teams we have dependencies on. We were talking to Jeff Yaskin the other day at work (he was kind enough to stop by and have a chat with us), and he put forth the idea that when two teams are in a disagreement on how to do something sometimes it is necessary for one team to swallow their pride and let the other team get work done. I was wondering: what two warring teams should do to come to an arrangement like this? My first answer would be to look at which team is going to be more greatly inconvenienced by doing things one way or another. Then I got to thinking, who is going to experience the greater pain changing their ways shouldn't always be the deciding factor. In some situations (probably most situations truthfully), it is important to see the bigger picture. What if a UI team desperately needs something from a service provider team to present a usable interface to their end user and the client? Shouldn't the real world business need of satisfying the customer trump the grumblings of the service provider team? But what if the service provider team doesn't see the big picture, or what if their big picture doesn't look the same as the UI team's or the Business Analyst's big picture? How do you go about showing each other "the light"? Posted on Saturday, May 31, 2008 8:06 AM | Back to top

Comments on this post: How do you respectfully disagree and still build software?

# re: How do you respectfully disagree and still build software?
Requesting Gravatar...
The only stuff that matters.

-- Who has more sway with the project-head.

Left by Cyril Gupta on Jun 02, 2008 5:51 AM

Your comment:
 (will show your gravatar)

Copyright © Robery Stackhouse | Powered by: