quanonline - Group Communication

GROUP COMMUNICATION

Communicating effectively at all levels across departments is truly an art form. The day to day tasks of performing one's job is hard enough and then you have to pass the information down to the appropriate players in the other departments.
There are several things that must be taken under consideration in order to have effective communication lines. For the purpose of this page the interaction between the development and test groups was chosen. Keep in mind that while not all the information discussed here applies to the relation between other departments, alot of the basic concepts due apply because they are universal.

How well does your development group communicate with the testing group?
The relationship between the development and test groups is naturally adversary; one group creates code while the other tries to shoot holes in it and find everything that is wrong with it. While sometimes that may not be a bad thing it can quickly turn into problem if it goes out of control and remains unchecked.
The reason is very simple; human nature. We don't like our work criticized. Both testers and developers understand that the product must be tested but sometimes personalities and ego can get in the way. If poor communication and lack of processes are added to the equation, the relationship will turn counter-productive very quickly. However, when processes and communication are handled properly, the development and testing cycle is not a problem but rather a very productive exercise.

The relationship between the development and test departments sometimes is too adversary and turns counterproductive.

A set of tools and methodologies must be put in place to help smooth out the relationship between the two departments while enhancing performance and adding more value to the whole process. Some of the key points that must be considered include:

VISIBILITY	What is the status of the test cases and procedures? When is testing going to be completed? These are some of the most common questions asked during the test cycle and the ones that go un-answered more frequestly than desired. Obtaining this information is not aleays the easiest thing due to the dynamic nature of the test effort. The test department must have the ability to track the status of each test procedure and test case in a real time fashion. In addition, information must be distributed in a prompt and comprehensive manner to all concern parties throughout the organization.

ACCOUNTABILITY	Why are things being returned to the test group when they are not yet fixed? Why are modules sent to the developers when they are working as intended? These types of circumstances seem to arise in every testing cycle. There are many problems that arise from having this set of events occur. For one, friction among the groups begins to form, energy and time are wasted in a series of fruitless exercises. The best way to avoid this problem is to have a methodology that provides all team members a clear picture of the task at hand.

CORRECTIVE MEASURES	After an entire test/development lifecycle many problems have been encountered. Some have been solved while other linger open to be addressed during the next release. The main question at this junction is: What will be done different in the next release to avoid the problems encountered? The answer to this question is extremelly important because it will show whether or not anything has been learned from the current experience. It is acceptable to make mistakes as long as something is learned from them so they are not committed again. The organization must have a mechanism to capture critical information. This mechanism must also present information in a clear and concise manner so it can be analyzed. Lessons learned must then be documented and made readily available to key personnel for review prior to engaging in another project. Click here for a free communication improvement suggestions form.

Secutity Statement | Privacy Statement