Publication Date: 2/15/2010 8:38:17 AM
Whenever I’ve heard people talk about the importance of a single point of contact for communication between the developer and the “customer”, I’ve thought this was primarily to protect team members from unnecessary emails and meetings. But what I’ve come to realize is how important this is to project health generally, for a couple of reasons:
If only one person is giving the programmer feedback, they are less likely to get conflicting messages about how things should work.
Less communication about the communication
As a programmer on the outside of an organization, I often can’t tell who will have the answers to my questions. This means that when I have a question I have a few options:
Unfortunately, my hopes are not always realized.
I have found that what works best is for there to be a project manager or other person within the organization who coordinates communication with me. That way, I’m not sending email to 5 people, and hoping one of them will respond to my questions. It also works best if this person is a decision maker, because that can mean faster answers than if they have to run it by someone else.
Think like a geek
Mark W. Schumann
Your URL (optional):
Type the code shown
Top 5 Programmers to Avoid
What everyone should know about bugs
How to tell if an estimate sucks
The Secret to Building a Crappy User Interface
The Problem with Selecting the Lowest Bidder
5 Ways to Control Software Development Costs
Avonelle is an incredibly talented software developer. She works fast, is economical, and offers great insights into the project at hand. She is also not afraid to speak up when she has concerns about a decision or approach. We’ve utilized her talents on many of our software development projects over the years.
Carrie Rocha, Chief Operating Officer @ HousingLink
Copyright © 2013 Avonelle Lovhaug. All Rights Reserved.
Sitefinity ASP.NET CMS