> For the complete documentation index, see [llms.txt](https://docs.businessanalystcourses.com/business-analysis-101/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.businessanalystcourses.com/business-analysis-101/stakeholder-communication.md). # Stakeholder communication Going back to our project, you have identified all these stakeholders. | Role | Contact | | --------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | | Business Analyst | | | Project Sponsor | | | Customer | | | End user - Sample users of TechJobs who will use the App. | [accountmanagers@techjobs.com](mailto:usergroup@CloudKitchen.com) | | Subject Matter Expert- who handles the company relationships with the clients who needs candidates. | [accountmanagers@techjobs.com](mailto:usergroup@CloudKitchen.com) | | Project Manager | | | Testers | | | Developers | | | UI Designers | | How do you make sure all of them are aware of the project, its goals, expected deadlines, when it will go live, etc? You need to send constant communication to all the stakeholders periodically. It can be every week, every other week or every month or a quarter. The project management committee decides the frequency. As a business analyst, how do you make sure all of these people(stakeholders) with different backgrounds understand the project status and the next step? How do you communicate in a language that will be easy to understand for all? Here comes the project road map... --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.businessanalystcourses.com/business-analysis-101/stakeholder-communication.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.