What is Communication Practice in Software engineering ?

Before customer requirement can be taken into considerations, studied or analyzed, it must be gathering through commutation called Requirement gathering activity. A customer has a problem that may be amenable to a computer- based solution. A developer responds to the customer’s request for help. Communication has begun. But the road from communication to understanding is often full of potholes. Effective communication among technical peers, with the customer and other stakeholders, and with project managers is the most challenging activities that confront software engineer. Some principles are following :-

1. Listen carefully : – To understand customers requirement perfectly and listen carefully to speaker which ensure proper data collection. Ask for classification of something is under , but avoid constant interceptions. Concentrate on speakers’ word so there should be any chance of misinterpretation.

2. Prepare before you communicate :- Spend the time to understand the problem before you meet with others. If necessary, do some research to understand business domain jargon. If you have responsibility for conducting a meeting, prepare an agenda in advance of the meeting.

3. Someone should facilitate the activity :- Every communication meeting should have a leader to keep conversation moving in productive direction. To solve any conflict that does occur.

4. Face–to-face communication is best :- Face-to-face communication is better but even if some document related to that particular subject or discuss is given. The drawing and documents speaks better.

5. Take notes and document decision : – Note down all important points and issue raised in the meeting maintain record. One participant of meeting may act as a recorder for the notes and document decision.

6. Stay focused, modularize your discussion :-  The more people involved in any communication the more chances to bounce topic form one to other. The facilitator should keep conversation in one direction and important topic will be focused. so stay be focused modularize with your discussion.

7. Strive for collaboration : – Collaboration in team members is essential for better team work. Collaboration is achieved when collective knowledge of member of the team is united to illustrate product of system function or system feature. It helps to build faith among team member and create generic goal for team. So the collaboration is very important in the team members.

8. If something is unclear, draw a picture :- Though verbal communication is important a sketch or drawing can be often provide clarity when words fails to do job so that’s why draw the clear drawing or picture for particular stage.

9. Negotiation is successful when both parties win :- There are many instances in which the software engineer and the customer must negotiate functions and features, priorities, and delivery dates. If the team has collaborated well, all parties have a common goal. Therefore, negotiation will demand compromise from all parties.


The Generic task set for Communication practice is given below :

1. Identify primary customer and other stakeholders.

2. Meet with primary customer to address “context free questions” that define.
  • Business need and business values.
  • End-users’ characteristics / needs.
  • Required user- visible outputs.
  • Business constraints.

3. Develop a one- page written statement of project scope that is subject to revision.

4. Review statement of scope with stakeholders and amend as required.

5. Collaborate with customer/end- users to define:
  • Resulting outputs and inputs.
  • Important software features, functions, and behavior.
  • Customer-defined business risks.

6. Develop a brief written description (e.g., a set of lists) of scenarios, output/ inputs, features/ functions and risks.

7. Iterate with customer- defined priorities to each user scenario, feature, function, and behavior.

8. Assign customer- defined priorities to each user scenario, feature, function, and behavior.

9. Review all information gathered during the communication activity with the customer and other stakeholder and armed as required.

10. Prepare for planning activity.



Next Topic :

No comments:

Post a Comment