How to Talk to People and get Your Point Across

http://bit.ly/n5tJgV

As a business analyst, one has to be able to communicate effectively with people on the business end and developers. Today's post is about my experiences communicating with developers.

I work a lot with developers and it is easy for them to dive into the realm of database terms and disposition lines. Yes, I understand that the database works in this way and that the software was coded to work a certain way, but to meet the requirements bugs need to be fixed. Normally these conversations come up when I've found a bug in the system; I need to explain why it is a bug and how the software should work. Keep in mind that multiple developers may work on the same piece of code, sometimes without even knowing each other. Other times the functional team doesn't think of all the possible outcomes until they start to see the software coming together.

Either way, here are some things I learned for explaining requirements or bugs to developers.

• It is your job as representing the business to say what needs to be displayed. It is the developers job to figure out how. (Told to me by a developer)
• If you're trying to explain a requirement and get stuck get backup! Ask another functional team member who knows the requirements to clarify what you're saying.
• Don't let dev talk confuse you or bring you down.
• Be confident when explaining the defect. Having examples and being able to reproduce the problem will help.
• Put the bug in a "compliment sandwich". Showing that you appreciate the good things about the system can help the developer not become defensive about an issue.