Software systems are getting ever bigger and complicated while their Time to Market (TTM) is shrinking ever shorter. At the same time the cost of failure for the software implementations is getting higher. From the technology standpoint architecture is the blueprint for the system. Criticality of the architecture piece in the success of any IT system necessitates taking all the precautions getting it done right the first time. IT has established itself as a business enabler and serves as one of the prime drivers for the business growth. This changed business landscape, with its high dependency on IT, demands looking at the architecture development process from a fresh perspective. In this article we will discuss seven of the crucial practices that are important for developing architectures that survive and succeed.
THINKING THE BUSINESS, IMPLEMENTING THE TECHNOLOGY (1)
Independent research groups have identified lack of proper communication between the various stakeholders as one of the biggest failure factors for an IT project. The data shows that more than 50% of the projects that failed could have been saved if the folks in the team had taken keen interest in understanding each other. Why there is a lack of effective communication across the team, even when there is a lot of communication going on?
Communication is a vehicle to transfer our thinking among ourselves. We package our thoughts in the vocabulary and language we understand, often ignoring the fact that the receiver might be having her own set of vocabulary and language. The meaning of what has been communicated could change drastically after the receiver converts and translates it into her own terms. IT projects are team driven and creating a common vocabulary could be a daunting task. Given the heterogeneous nature of the IT teams, it is no wonder that the effective communication is a challenge.