I have been in meetings recently where some consultants, tasked with building an enterprise software solution based on a FileMaker solution I built, keep asking, “What are the fields and data types the system is tracking?”. Various people involved ask me over and over for lists of fields and tables, and I dutifully give them lists of fields and tables. They ask me for sample data, I give them sample data. Invariably they keep calling me back to meetings. “We looked at the lists of fields and tables. We looked at the sample data. We looked at the requirements documents. So, what are we supposed to be doing?” (I’m paraphrasing but you get the idea.)
Effective communication is arguably the most important aspect of a custom software development project. Good communication facilitates teamwork, while a lack thereof can stop a project dead in its tracks.
Getting information across and being understood in turn is key to a successful IT project implementation. The client communicates their needs to the developer, who must translate those needs into features that work with the chosen technology. Once underway, regular, two-way communication keeps a project moving along and allows you to discover issues earlier than you otherwise might.