BA community – Telegram
BA community
2.56K subscribers
610 photos
58 videos
6 files
394 links
Lead community of business and system analysts.

Follow us on LinkedIn: https://www.linkedin.com/groups/9800419.

Admin: @nadina_12.
Download Telegram
Hi analysts! ⭐️
There are some highly-complex domains, working in which requires an IT Business Analyst (BA) to intensively collaborate with various subject-matter experts (SMEs). What influences the quality of communication (and hence the comprehensiveness of requirements gathering) is the availability of the SME, their involvement in the project, and the project implementation phase. In this article, we will reveal the possible algorithms of interaction between a BA and an SME👉
👍4🔥32
Hi analysts! ⭐️
Let's continue discussing the possible algorithms of interaction between a BA and an SME👉
Hi analysts!⭐️
Here you can find an opinion why is so important to turn on camera during the online meeting.
Please, share from which team you are?
2
From which team you are?
Anonymous Poll
57%
Camera turn on
43%
Camera turn off
BA community
#BAmeme
It's a good result that most of us are in 'camera turn on' team😎
Do you agree that it helps to establish connection in the team and take part in funny moments like this?
👍3
Hi analysts!⭐️
In the last few posts we discuss the topic of communication on the project.
Today I propose to continue and discuss the topic "Use power-interest matrix for stakeholder prioritization"
Power-interest matrix visualizes the level of involvement and impact stakeholders have on the project.
It helps to group and prioritize stakeholders based on their power-interest level criteria.
As usual more information you will find more information on the slides👉
🔥5
Andersen invites you to a vibey meetup for Business and System Analysts!
🗓 8 June at 19:00
📍 Andersen Office Batumi
🎤 Speaker Siarhei Yehareichanka will bring up an important topic - "Know Your Customer (KYC): Play Legally Without Going Mad".
He will share with us his knowledge of and experience in KYC verification. Is it possible to build a universal multi-provider verification ecosystem without losing your mind?
Registration is required: the link
🔥2
​​Hi analysts!⭐️
How about dive a little bit deeper to Peculiarities of working with SMEs at different phases of the project?
Some posts ago we discussed BA and SME interaction (part 1, part 2).
Let's look at presale phase.

An in-house SME should participate in the project from the very beginning, if possible. Thus, the expert will have an opportunity to familiarize themselves with the customer's request together with the BA and immediately explain this request and the peculiarities of the customer’s business process to the analyst. The SME will suggest options for optimizing the current or planned system, taking into account its feasibility and their experience.

Depending on agreements, the SME will be able to ask questions to the customer during the meetings. In this case, special attention should be paid to the SME’s level of English or any other language used for the negotiations. If the level is low, the expert’s activity during the meetings reduces, hence they should be able to formulate their questions and ask them through the BA. Later, the SME can take part in the process of determining the planned product functionality in order to enhance the accuracy of assessing the features’ implementation.

Solution: draw up a list of questions for the customer and a specific list of functions for the planned system
👍2
Hi analysts!⭐️
Today we continue discussing Peculiarities of working with SMEs at different phases of the project.

At the start of the Discovery phase, the BA should introduce the SME to the team and give this specialist an opportunity to talk in simple words about the essence of the project and their vision of its implementation. In the course of Discovery, the BA can coordinate the prepared documentation with the SME and ensure their interaction with the designer to explain the features of the designed system and its convenience for users. The SME should also be involved in meetings with the customer or their expert for a more complete requirements elicitation based on domen specifics.

Solution: draw up a list of questions aimed at requirements elicitation, documents for the V&S/SRS approved by the SME, and designs.

#Discovery
👍1
​​Hi analysts!⭐️
Today we discuss Peculiarities of working with SMEs at delivery and support phases of the project.

Delivery. During the Delivery stage, the BA and the SME actively interact with the development team in the shadow support mode, answering their questions. It is considered good practice to explain to the team why the solution being developed is useful and essential for society and what the fundamental points of its use are.

In this phase, the SME’s activity is lower than in the previous ones. At the end of Delivery, this expert might be given the task of helping the BA in compiling various user guides.

Solution: tell the SME about the purpose and peculiarities of using the product, ensure support for the team, and create user guides.

Support
. During the Support stage, the work of the SME and the BA is mainly focused on handling requests and feedback from end-users. The expert will be able to explain tricky moments to workers and clearly convey the importance of a particular request to the team. The BA aligns requests with existing requirements, provides the customer with detailed estimates of changes, and manages possible changes of requirements.

Solution: document new product requirements approved by the SME after feedback is processed.