COMMUNICATION

Communication takes many forms for the business analyst. You communicate verbally, in pictures, and
in written documentation. The business analyst is often responsible first, for helping the stakeholders
communicate among themselves about the business problems and opportunities.

The business analyst is also responsible for communicating requirements to the implementation team.
The end-to-end requirements process involves many individuals, from subject matter experts within the
business to implementation engineers (developers, database administrators, IT, QA, user interface
designers, etc.). For each deliverable there might be a different set of stakeholders across business and
IT involved in creating, reviewing, and approving it. The BA is in the center of all of these groups
ensuring that communication about the requirements and the solution is seamless.
Throughout the implementation process, the business analyst will also keep communicating back to the
business team. Oftentimes alternatives or constraints surface during implementation and the business
analyst needs to bring some possibilities back to the business for a decision.

Written communication
Requirements Specifications

The most prominent form of written communication are the requirements and specification documents
youll create to solidify the requirements. The types of documents are discussed in detail above. When it
comes to writing these documents, a business analyst needs to focus on the clarity of their language.
Ambiguous writing or writing that lacks clarity in general will lead to an inefficient requirements process.

Another aspect of written communication is its usability. Usable documents tend to be well-organized,
logical, and consistent. Formatting is one aspect of a usable document, but much more important is how
you leverage the format to make the document easy to comprehend.

Email

Visual communication

Verbal Communication Skills