State and describe six principles of communication practices.

 Solution:-

Communication Practices Effective communication among the technical peers, customers and other stakeholders, project managers etc. is among the most challenging activities that confront software engineers. Before customers‘ requirements can be analysed, modeled are specified they must be gathered through a communication. Effective communication is among the most challenging activities that you will confront.

Communication Principles are

1. Listen: Try to focus on the speaker‘s words, rather than formulating your response to those words. Ask for clarification if something is unclear, but avoid constant interruptions.

2. Prepare before you communicate: Speed the time to understand the problem before you meet with others. If necessary, do some research to understand business domain jargon.

3. Someone should facilitate the activity: Every communication meeting should have a leader to keep the conversation moving in a productive direction, to mediate any conflict that does occur and to ensure than other principles are followed.

4. Face-to Face communication is best: It usually works better when some other representation of the relevant information is present. For e.g. A participant may create a drawing or a ―straw man‖ document that serves as a focus for discussion.

5. Take notes and document decisions: Things have a way of falling into cracks. Someone participating in the communication should serve as a ―recorder‖ and write down all important points and decisions.

6. Strive for collaboration: Collaboration and consensus occur when the collective knowledge of members of the team is used to describe product or system functions or features. Each small collaboration serves to build trust among team members and creates a common goal for the team.

7. Stay focused; modularize your discussion: The more likely involved in any communication, the more likely that discussion will bounce from one topic to next. The facilitator should keep the conversation modular; leaving one topic only after it has been resolved.

8. If something is unclear, draw a picture: Verbal communication goes only so far. A sketchor drawing can often provide clarity when words fail to do the job.

9. A) Once you agree to something, move on. B) If you can’t agree to something, move on C) If a feature or function is unclear and cannot be clarified at the moment, move on. : Communication, like any software engineering activity, takes time. Rather than iterating endlessly the people who participates should recognize that many topics require discussion and that ―moving on‖ is sometimes the best the best way to achieve communication agility.

10. Negotiation is not a contest or a game. It works best when both parties win: There are many instances in which you and other stakeholders must negotiate functions and features, priorities, and delivery dates. If the team has collaborated well, all parties have a common goal. Still, negotiation will demand compromise from all parties

Comments

Popular posts from this blog

State the functions of Hub, Repeater, Bridge and Router.

Describe the OSI model with neat diagram.

Explain Database languages.