🚨 Managers vs. Burned-Out Employees!
Want to know what managers do? Support, pressure, or pretend everything’s fine?
👇 See the poll in Typical Manager and Vote – the truth must be heard! 💥
🔗 Link to the poll
Want to know what managers do? Support, pressure, or pretend everything’s fine?
👇 See the poll in Typical Manager and Vote – the truth must be heard! 💥
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥1👏1
How does MoSCoW help Business Analysts❓
Did you know that 80% of IT projects fail, according to a Gartner survey? And one of the leading causes is poor prioritization, which can result in functionality issues, substantial delays, and runaway costs [source].
The MoSCoW Method provides a clear framework to identify and prioritize requirements based on their importance and impact, enabling business analysts to focus on what truly matters.
How Does the MoSCoW Method Help Business Analysts?
The MoSCoW Method categorizes requirements into 4 distinct groups:
✅ Must-Have: These are essential for project success. Without them, the project would fail.
✅ Should-Have: These are important but not critical; they enhance the project but can be deferred if necessary.
✅ Could-Have: These are desirable features that add value but are not necessary.
✅ Won’t-Have: These are non-essential and won’t be included in the current scope.
We always can use MoSCoW when:
- Deadlines are tight and prioritization is critical.
- Resources are limited, requiring efficient allocation.
- Stakeholder alignment is needed to avoid conflicts and ensure clarity.
- We simply need to prioritize the requirements.
Have you used the MoSCoW Method in your projects?
#MoSCoWMethod #Prioritization #BusinessAnalysis #BACommunity
Did you know that 80% of IT projects fail, according to a Gartner survey? And one of the leading causes is poor prioritization, which can result in functionality issues, substantial delays, and runaway costs [source].
The MoSCoW Method provides a clear framework to identify and prioritize requirements based on their importance and impact, enabling business analysts to focus on what truly matters.
How Does the MoSCoW Method Help Business Analysts?
The MoSCoW Method categorizes requirements into 4 distinct groups:
✅ Must-Have: These are essential for project success. Without them, the project would fail.
Example: Core functionalities like payment processing in an e-commerce platform.✅ Should-Have: These are important but not critical; they enhance the project but can be deferred if necessary.
Example: A search filter in an app that could be added post-launch.✅ Could-Have: These are desirable features that add value but are not necessary.
Example: Custom themes or advanced analytics for users.✅ Won’t-Have: These are non-essential and won’t be included in the current scope.
Example: Experimental features or ideas that require additional resources.We always can use MoSCoW when:
- Deadlines are tight and prioritization is critical.
- Resources are limited, requiring efficient allocation.
- Stakeholder alignment is needed to avoid conflicts and ensure clarity.
- We simply need to prioritize the requirements.
Have you used the MoSCoW Method in your projects?
#MoSCoWMethod #Prioritization #BusinessAnalysis #BACommunity
Please open Telegram to view this post
VIEW IN TELEGRAM
❤5🔥1
This media is not supported in your browser
VIEW IN TELEGRAM
Classic documentation: a Vision and Scope Document 📑
Analysts, imagine that you have started a project with an IT outsourcing company. How can you make sure that your software partner has understood your wishes correctly and will implement them exactly the way you want? The answer is: create a vision and scope document. In this article, we'll show you how this document can save your project and give you a structure on how to create it.
A Vision and Scope Document — the product from a business perspective
Ideally, the work on a project begins with a document that answers the questions of what kind of program is being developed and why. Together with the customer, a Business Analyst forms the product image and describes what goals the business will achieve with the help of this software. In other words, a Vision and Scope Document - an artifact that is obtained as a result of the work of a Business Analyst with a customer (or customer representatives) at the stage of the discovery phase - is being created.
The Vision and Scope Document contains a set of business requirements (or business needs), high-level denoscriptions of system functionality, project priorities, a list of stakeholders, and other information. The Business Analyst develops the Vision and Scope Document so that all project participants have a high-level understanding of what the product is being built for.
Along with that, the Vision and Scope Document contains information about the “pains” of the business and its abilities to create a product. If we had described the problems of passengers in this document before the creation of Uber, for instance, we could have indicated that there was a lack of vehicles and people wanted to order cheaper cars faster. These are the problems that were solved with the corresponding application.
What is the benefit of a Vision and Scope Document for a customer? It helps in formulating clear criteria for the project's success and effectiveness. Thanks to this 10-page document, specialists have a quick understanding of what they will be developing and why. The Vision and Scope Document makes it easier for managers to convince investors of the product value.
Here's how a basic structure of a Vision and Scope Document looks like (see the attached picture). 🙂
#VisionAndScope #BusinessAnalysis #RequirementsGathering #StakeholderAlignment #BABestPractices
Analysts, imagine that you have started a project with an IT outsourcing company. How can you make sure that your software partner has understood your wishes correctly and will implement them exactly the way you want? The answer is: create a vision and scope document. In this article, we'll show you how this document can save your project and give you a structure on how to create it.
A Vision and Scope Document — the product from a business perspective
Ideally, the work on a project begins with a document that answers the questions of what kind of program is being developed and why. Together with the customer, a Business Analyst forms the product image and describes what goals the business will achieve with the help of this software. In other words, a Vision and Scope Document - an artifact that is obtained as a result of the work of a Business Analyst with a customer (or customer representatives) at the stage of the discovery phase - is being created.
The Vision and Scope Document contains a set of business requirements (or business needs), high-level denoscriptions of system functionality, project priorities, a list of stakeholders, and other information. The Business Analyst develops the Vision and Scope Document so that all project participants have a high-level understanding of what the product is being built for.
Along with that, the Vision and Scope Document contains information about the “pains” of the business and its abilities to create a product. If we had described the problems of passengers in this document before the creation of Uber, for instance, we could have indicated that there was a lack of vehicles and people wanted to order cheaper cars faster. These are the problems that were solved with the corresponding application.
What is the benefit of a Vision and Scope Document for a customer? It helps in formulating clear criteria for the project's success and effectiveness. Thanks to this 10-page document, specialists have a quick understanding of what they will be developing and why. The Vision and Scope Document makes it easier for managers to convince investors of the product value.
Here's how a basic structure of a Vision and Scope Document looks like (see the attached picture). 🙂
#VisionAndScope #BusinessAnalysis #RequirementsGathering #StakeholderAlignment #BABestPractices
🔥7👏1
Dear business analysts, don't miss the chance! ☀️
We invite you to upcoming meetup where we will talk on AI for #businessanalysts
08.05.2025, Warsaw 🗓
In partnership with IIBA Poland Chapter
For more information and registration - go to our LinkedIn channel - Analyst Hub📱
See you!
#community #AI #network #requirements #software
We invite you to upcoming meetup where we will talk on AI for #businessanalysts
08.05.2025, Warsaw 🗓
In partnership with IIBA Poland Chapter
For more information and registration - go to our LinkedIn channel - Analyst Hub
See you!
#community #AI #network #requirements #software
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥5❤4👍1
"Not seeing the BIG PICTURE" - analyst's expert opinion
Obviously, it's not easy to see the big picture. I've experienced this problem as well. At the same time, it's very common issue that I notice in BAs who are in the early stages of their career, plus my students and even very experienced senior specialists. And I've seen it many times in different projects and circumstances.
"You have a specific task, specific requirement and it serves some purpose. You know what this requirement is about. But you don't know the end goal. You can't see the value in it. You don't know how this requirement adds up to the big picture. You can write good user stories, but you don't see the epic. It's like you make a tire, but you don't know what car is being made".
To avoid this issue, the BA should always prioritize the big picture and focus on it. It's very important to see the small details as well, but if you have no clearance on what the end goal is, it means you haven't analyzed the requirement in a correct way.
How?
In requirement elicitation, try to build the habit of asking yourself "what is the end goal here?" & "Do I see the Big Picture?". Zoom out, have the bird view and view the overall scope from that point. In my experience this is one of the most effective ways to see the big picture.
Obviously, it's not easy to see the big picture. I've experienced this problem as well. At the same time, it's very common issue that I notice in BAs who are in the early stages of their career, plus my students and even very experienced senior specialists. And I've seen it many times in different projects and circumstances.
"You have a specific task, specific requirement and it serves some purpose. You know what this requirement is about. But you don't know the end goal. You can't see the value in it. You don't know how this requirement adds up to the big picture. You can write good user stories, but you don't see the epic. It's like you make a tire, but you don't know what car is being made".
To avoid this issue, the BA should always prioritize the big picture and focus on it. It's very important to see the small details as well, but if you have no clearance on what the end goal is, it means you haven't analyzed the requirement in a correct way.
How?
In requirement elicitation, try to build the habit of asking yourself "what is the end goal here?" & "Do I see the Big Picture?". Zoom out, have the bird view and view the overall scope from that point. In my experience this is one of the most effective ways to see the big picture.
❤8🔥3
Effective Note-taking methods during meetings 📌
Taking notes during meetings is important, but can be tricky to not miss anything important. Here are some easy methods to stay organized:
1) The Quadrant method: Divide your page into two columns (or four sections). One column is for main ideas, and the other is for more detailed notes. You can then divide your page into categories like general notes, action items for yourself, tasks for others, and any questions. This structure helps keep everything organized as the conversation goes on.
2)Symbols: Use a set of symbols to help you quickly capture information. For example, you might use a star (*) for something that stands out, an exclamation mark (!) for urgent stuff, or a question mark (?) for follow-up items.
Handwritten Notes vs Digital Notes: Studies suggest that handwriting notes can help you remember information better than typing! If you’re trying to stay focused and improve your memory, choose writing your notes by hand
3) Timestamp your notes: If the meeting is pretty long, add timestamps next to the points in your notes. So, you can find specific parts of the discussion when you look back much more easily!
4)Use abbreviations: Come up with your own shorthand for frequently used terms. For example, “AP” - action point, “FYI” - for your information, “US” - user profile, etc.
5)Voice notes: In digital meetings, consider using a voice recording app for important points. You can always go back and listen to them if you missed something!
6)"Parking lot": If a topic goes off track (or isn’t relevant), “put” it down in a “parking lot” section to come back to it later. This will help you stay focused on the current agenda while ensuring you don’t forget important things.
7) Summarize: At the end of the meeting, take a couple of minutes to quickly summarize the key points, action items, and deadlines in your notes. This reinforces the information while it’s still fresh in your mind.
8) The "Who, What, When": As the meeting progresses, note down the key points in three simple categories: Who is responsible, What needs to be done, and When it needs to be completed.
9)Collaborate on notes: If you’re working within a team, share your notes with colleagues. They may have additional points or clarifications that you have missed!
#NoteTakingTips #MeetingProductivity #BACommunity #EffectiveCommunication
Taking notes during meetings is important, but can be tricky to not miss anything important. Here are some easy methods to stay organized:
1) The Quadrant method: Divide your page into two columns (or four sections). One column is for main ideas, and the other is for more detailed notes. You can then divide your page into categories like general notes, action items for yourself, tasks for others, and any questions. This structure helps keep everything organized as the conversation goes on.
2)Symbols: Use a set of symbols to help you quickly capture information. For example, you might use a star (*) for something that stands out, an exclamation mark (!) for urgent stuff, or a question mark (?) for follow-up items.
Handwritten Notes vs Digital Notes: Studies suggest that handwriting notes can help you remember information better than typing! If you’re trying to stay focused and improve your memory, choose writing your notes by hand
3) Timestamp your notes: If the meeting is pretty long, add timestamps next to the points in your notes. So, you can find specific parts of the discussion when you look back much more easily!
4)Use abbreviations: Come up with your own shorthand for frequently used terms. For example, “AP” - action point, “FYI” - for your information, “US” - user profile, etc.
5)Voice notes: In digital meetings, consider using a voice recording app for important points. You can always go back and listen to them if you missed something!
6)"Parking lot": If a topic goes off track (or isn’t relevant), “put” it down in a “parking lot” section to come back to it later. This will help you stay focused on the current agenda while ensuring you don’t forget important things.
7) Summarize: At the end of the meeting, take a couple of minutes to quickly summarize the key points, action items, and deadlines in your notes. This reinforces the information while it’s still fresh in your mind.
8) The "Who, What, When": As the meeting progresses, note down the key points in three simple categories: Who is responsible, What needs to be done, and When it needs to be completed.
9)Collaborate on notes: If you’re working within a team, share your notes with colleagues. They may have additional points or clarifications that you have missed!
#NoteTakingTips #MeetingProductivity #BACommunity #EffectiveCommunication
❤5🔥3👍1
The baton of April meetups is passed to “Product Approach in Software Development” 🥇
In 2025, the winners are those who focus not on outputs but on outcomes. The product approach helps teams adapt faster, validate hypotheses, and achieve significant business results.
At the meetup on April 28, Vadim Rutkevich will explain how the product approach differs from the project approach, how to implement it, what pitfalls you might encounter, and what tools will streamline this transition.
🎟 Register here
Meetup details:
⏰ Time: 18:00 CET
⏳ Duration: 45 minutes – 1 hour
🗣 Language: English
💻 Online: The link to the stream will be sent to your email specified in the registration form
Join our IT Community:
📱 Dev Telegram: https://news.1rj.ru/str/d3v_community
📱 Dev LinkedIn: https://www.linkedin.com/groups/9877436/
📱 BA/SA LinkedIn: https://www.linkedin.com/groups/9800419/
In 2025, the winners are those who focus not on outputs but on outcomes. The product approach helps teams adapt faster, validate hypotheses, and achieve significant business results.
At the meetup on April 28, Vadim Rutkevich will explain how the product approach differs from the project approach, how to implement it, what pitfalls you might encounter, and what tools will streamline this transition.
🎟 Register here
Meetup details:
⏰ Time: 18:00 CET
⏳ Duration: 45 minutes – 1 hour
🗣 Language: English
💻 Online: The link to the stream will be sent to your email specified in the registration form
Join our IT Community:
📱 Dev Telegram: https://news.1rj.ru/str/d3v_community
📱 Dev LinkedIn: https://www.linkedin.com/groups/9877436/
📱 BA/SA LinkedIn: https://www.linkedin.com/groups/9800419/
❤3🤩2
🔥 We’re back together! On May 8, Andersen, in collaboration with IIBA Poland Chapter, will hold a meetup
The world of business analysis is rapidly changing under the influence of AI, so now it’s high time to adapt to the new reality. How exactly? Learn from our speakers 👇
📌 Sviatlana Varabyova (Senior Business Analyst) – "The Evolving Role of the IT Business Analyst in the Age of AI"
We’ll discuss what essential skills IT business analysts need, what challenges they face, and how they can adapt to thrive in an AI-powered landscape.
📌 Tomasz Plebanski (Business Analysis Manager) – "AI for Smarter Business Analysis: Practical Use Cases and Insights"
We'll delve into practical use cases of AI in business analysis, including requirements gathering and analysis, stakeholder collaboration, document analysis, artefact creation, and more.
➡️ Register here
Twice as many speakers – twice as much value, and hence seats are filling up twice as fast. Don’t wait to register 😉
⏰ Time: 18:00 (CET)
⏳ Duration: 1-1.5 hours
🗣 Language: English
📍 Offline: Andersen’s office in Warsaw
See you!
#MeetUp #BusinessAnalysis #IIBA #AI
The world of business analysis is rapidly changing under the influence of AI, so now it’s high time to adapt to the new reality. How exactly? Learn from our speakers 👇
📌 Sviatlana Varabyova (Senior Business Analyst) – "The Evolving Role of the IT Business Analyst in the Age of AI"
We’ll discuss what essential skills IT business analysts need, what challenges they face, and how they can adapt to thrive in an AI-powered landscape.
📌 Tomasz Plebanski (Business Analysis Manager) – "AI for Smarter Business Analysis: Practical Use Cases and Insights"
We'll delve into practical use cases of AI in business analysis, including requirements gathering and analysis, stakeholder collaboration, document analysis, artefact creation, and more.
➡️ Register here
Twice as many speakers – twice as much value, and hence seats are filling up twice as fast. Don’t wait to register 😉
⏰ Time: 18:00 (CET)
⏳ Duration: 1-1.5 hours
🗣 Language: English
📍 Offline: Andersen’s office in Warsaw
See you!
#MeetUp #BusinessAnalysis #IIBA #AI
❤4🔥4👏1
We’ve Reached 500 Members on LinkedIn! Thank You, BA Community! 💛
Heartfelt thank you to each member! Your engagement, curiosity, and willingness to help one another are what make this community truly special.
To celebrate, we’re excited to spotlight our 500th member, Artem Stelmakhov, who has shared with us the story How did he come to business analysis, and what inspired him to join our community?
"Thank you for the opportunity to share my story. It's a pleasure to become the 500th member of the BA Community - a significant milestone for the group.
My journey into business analysis began at a manufacturing enterprise, where I witnessed the inefficiency of manual processes firsthand. For example:
- The workshop spent over three hours daily compiling raw material inventory reports in Excel, leading to outdated data.
- Logistics processes between warehouses followed obsolete protocols, causing downtime.
This experience highlighted the importance of automation and a systematic approach to optimization. I began exploring how digital solutions (such as ERP systems and RPA) could address operational inefficiencies, which gradually evolved into a professional interest in business analysis.
I was drawn to the BA Community for several reasons:
1. Practical focus: Discussions here revolve around real-world cases, not just theory.
2. Knowledge sharing: The chance to learn how other specialists tackle similar challenges.
3. Industry trends: Topics like IIoT or low-code applications in manufacturing processes.
If community members are interested, I’d be happy to elaborate on my experience implementing changes and the results achieved".
Let’s keep the momentum going—share in the comments what this community means to you or your own journey into business analysis.
Thank you for being the heart of our community!
📱 Analyst Hub on LinkedIn
#BusinessAnalysis #CommunityMilestone #MemberSpotlight
Heartfelt thank you to each member! Your engagement, curiosity, and willingness to help one another are what make this community truly special.
To celebrate, we’re excited to spotlight our 500th member, Artem Stelmakhov, who has shared with us the story How did he come to business analysis, and what inspired him to join our community?
"Thank you for the opportunity to share my story. It's a pleasure to become the 500th member of the BA Community - a significant milestone for the group.
My journey into business analysis began at a manufacturing enterprise, where I witnessed the inefficiency of manual processes firsthand. For example:
- The workshop spent over three hours daily compiling raw material inventory reports in Excel, leading to outdated data.
- Logistics processes between warehouses followed obsolete protocols, causing downtime.
This experience highlighted the importance of automation and a systematic approach to optimization. I began exploring how digital solutions (such as ERP systems and RPA) could address operational inefficiencies, which gradually evolved into a professional interest in business analysis.
I was drawn to the BA Community for several reasons:
1. Practical focus: Discussions here revolve around real-world cases, not just theory.
2. Knowledge sharing: The chance to learn how other specialists tackle similar challenges.
3. Industry trends: Topics like IIoT or low-code applications in manufacturing processes.
If community members are interested, I’d be happy to elaborate on my experience implementing changes and the results achieved".
Let’s keep the momentum going—share in the comments what this community means to you or your own journey into business analysis.
Thank you for being the heart of our community!
#BusinessAnalysis #CommunityMilestone #MemberSpotlight
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥9❤1🥰1
How to Handle Direct Criticism Across Cultures (Without Losing Your Cool or Your Team)
Do you work in international IT projects where feedback is part of everyday life?
Ever felt a teammate’s message was too blunt — or, on the flip side, annoyingly vague?
💡 It might not be about personality. It might be about cultural expectations of giving negative feedback.
📖 In The Culture Map, Erin Meyer describes how different cultures evaluate and express criticism. This is crucial for business/system analysts, who often act as bridges between stakeholders, developers, and end users.
Two cultural quadrants you should know:
🔹 Quadrant A: Low-Context + Direct Negative Feedback
Examples: 🇳🇱 Netherlands, 🇩🇪 Germany, 🇺🇸 USA
These cultures value clarity, honesty, and professionalism.
👉 If a Dutch or German colleague gives you direct criticism, it’s probably not personal. It’s a sign of respect for your competence.
📌 Do: Take their feedback seriously, not emotionally.
📌 Don’t: Try to “be just as direct” unless you deeply understand their style. You might overshoot and come off as rude.
🔸 Quadrant B: High-Context + Direct Negative Feedback
Examples: 🇷🇺 Russia, 🇮🇱 Israel
These cultures may be indirect in general conversation but very frank when giving negative feedback, especially toward strangers or subordinates.
📌 Do: Recognize that direct criticism doesn’t mean they dislike you — it’s how they operate in hierarchical or transactional settings.
📌 Don’t: Expect a polite sandwich of compliments — you might only get the meat.
Why does this matter in IT analytics?
Whether you’re facilitating a retrospective, analyzing stakeholder feedback, or conducting user interviews — understanding how criticism is meant to be delivered and received helps prevent:
- Unnecessary offense
- Silence instead of questions
- Misinterpretation of feedback loops
✅ Takeaways for analysts:
🔹 Accept that direct does not equal hostile.
🔹 When working with more direct cultures, take feedback at face value.
🔹 When working with less direct cultures, soften your message or use “downgraders” (“maybe,” “a bit,” “could be improved”).
🔹 Don’t mimic directness unless you truly understand where the line is.
Feedback is a tool — learn to read the instruction manual before using it.
#ITCommunication #BusinessAnalysis #SystemAnalysis #CrossCultural #FeedbackCulture #SoftSkills
Do you work in international IT projects where feedback is part of everyday life?
Ever felt a teammate’s message was too blunt — or, on the flip side, annoyingly vague?
💡 It might not be about personality. It might be about cultural expectations of giving negative feedback.
📖 In The Culture Map, Erin Meyer describes how different cultures evaluate and express criticism. This is crucial for business/system analysts, who often act as bridges between stakeholders, developers, and end users.
Two cultural quadrants you should know:
🔹 Quadrant A: Low-Context + Direct Negative Feedback
Examples: 🇳🇱 Netherlands, 🇩🇪 Germany, 🇺🇸 USA
These cultures value clarity, honesty, and professionalism.
👉 If a Dutch or German colleague gives you direct criticism, it’s probably not personal. It’s a sign of respect for your competence.
📌 Do: Take their feedback seriously, not emotionally.
📌 Don’t: Try to “be just as direct” unless you deeply understand their style. You might overshoot and come off as rude.
🔸 Quadrant B: High-Context + Direct Negative Feedback
Examples: 🇷🇺 Russia, 🇮🇱 Israel
These cultures may be indirect in general conversation but very frank when giving negative feedback, especially toward strangers or subordinates.
📌 Do: Recognize that direct criticism doesn’t mean they dislike you — it’s how they operate in hierarchical or transactional settings.
📌 Don’t: Expect a polite sandwich of compliments — you might only get the meat.
Why does this matter in IT analytics?
Whether you’re facilitating a retrospective, analyzing stakeholder feedback, or conducting user interviews — understanding how criticism is meant to be delivered and received helps prevent:
- Unnecessary offense
- Silence instead of questions
- Misinterpretation of feedback loops
✅ Takeaways for analysts:
🔹 Accept that direct does not equal hostile.
🔹 When working with more direct cultures, take feedback at face value.
🔹 When working with less direct cultures, soften your message or use “downgraders” (“maybe,” “a bit,” “could be improved”).
🔹 Don’t mimic directness unless you truly understand where the line is.
Feedback is a tool — learn to read the instruction manual before using it.
#ITCommunication #BusinessAnalysis #SystemAnalysis #CrossCultural #FeedbackCulture #SoftSkills
🔥6👏1
Anonymous Poll
28%
🗣 IT events & meetups
47%
69%
36%
0%
🤔2
🔍 Software (System) Requirements Specification (SRS)
Let’s talk about one of the most essential artefacts in a Business Analyst’s toolkit: the System Requirements Specification (SRS).
An SRS is much more than just a document-it’s the “set of laws” for your software project. It describes, in detail, what your system should do and the capabilities it must provide to users. This guide becomes the foundation for everyone involved:
✅ Project Managers use it to plan and track progress.
✅Developers rely on it to write the right code.
✅ QA specialists use it to test and validate the product.
Starting a project without an SRS is like setting off on a journey without a map. Without clear requirements, the team can easily lose direction, leading to confusion and costly mistakes.
Why is the SRS so valuable for customers?
Without a specification, requests can be misunderstood, and the final product may not meet expectations-resulting in wasted time and budget. A well-prepared SRS helps both sides stay aligned, reduces the risk of surprises, and makes it easier to compare project costs across different IT service providers.
It also saves money: instead of developers spending time clarifying requirements, the Business Analyst translates customer needs into clear, technical instructions-saving both time and resources.
Curious what an SRS actually looks like? Check out the example below! 👇
#BusinessAnalysis #SRS #SystemRequirementsSpecification #ProjectManagement
Let’s talk about one of the most essential artefacts in a Business Analyst’s toolkit: the System Requirements Specification (SRS).
An SRS is much more than just a document-it’s the “set of laws” for your software project. It describes, in detail, what your system should do and the capabilities it must provide to users. This guide becomes the foundation for everyone involved:
✅ Project Managers use it to plan and track progress.
✅Developers rely on it to write the right code.
✅ QA specialists use it to test and validate the product.
Starting a project without an SRS is like setting off on a journey without a map. Without clear requirements, the team can easily lose direction, leading to confusion and costly mistakes.
Why is the SRS so valuable for customers?
Without a specification, requests can be misunderstood, and the final product may not meet expectations-resulting in wasted time and budget. A well-prepared SRS helps both sides stay aligned, reduces the risk of surprises, and makes it easier to compare project costs across different IT service providers.
It also saves money: instead of developers spending time clarifying requirements, the Business Analyst translates customer needs into clear, technical instructions-saving both time and resources.
Curious what an SRS actually looks like? Check out the example below! 👇
#BusinessAnalysis #SRS #SystemRequirementsSpecification #ProjectManagement
❤8🔥3👏1
Writing User Stories - Vertical Slicing ✍️
Splitting large user stories into smaller user stories appropriately is one action that a team can do to improve their scrum workflow.
Not only are smaller stories easier to understand and therefore easier to estimate, but their smaller size makes them inherently less risky!
When attempting to split a user story, it is more desirable to split a user story into a slice vertically rather than horizontally.
A Vertical vs Horizontal Slice🍰
If a user story is broken down vertically, they are broken down in such a way that smaller items still result in working, demonstrable, software, or a specific working feature useful for the user.
✅ “User stories should be small enough to complete in one iteration”,
✅ “Each separate user story should have measurable business value.”
A vertical slice means it contains a bit of every layer of the system / ‘Cake’.
Our system, has basic 3 layers to the ‘Cake’:
1) UI/UX;
2) Domain (i.e. logic);
3) Data (e.g. file storage, blob, database…).
If a user story is broken down horizontally, it decomposes problems into technical layers. This may seem to match well with the technical skills of team members, i.e. they’re split amongst a database specialist, a UI specialist etc… but each user story can’t deliver the value to the end customer! At least not without interaction or integration with other layers, components, or other building blocks of the software system i.e. other user stories.
It is like slicing a cake horizontally, which does not allow for users to have the perfect bite :)
Click for detailed study
#UserStories #Agile #BusinessAnalysis #UserExperience
Splitting large user stories into smaller user stories appropriately is one action that a team can do to improve their scrum workflow.
Not only are smaller stories easier to understand and therefore easier to estimate, but their smaller size makes them inherently less risky!
When attempting to split a user story, it is more desirable to split a user story into a slice vertically rather than horizontally.
A Vertical vs Horizontal Slice
If a user story is broken down vertically, they are broken down in such a way that smaller items still result in working, demonstrable, software, or a specific working feature useful for the user.
✅ “User stories should be small enough to complete in one iteration”,
✅ “Each separate user story should have measurable business value.”
A vertical slice means it contains a bit of every layer of the system / ‘Cake’.
Our system, has basic 3 layers to the ‘Cake’:
1) UI/UX;
2) Domain (i.e. logic);
3) Data (e.g. file storage, blob, database…).
If a user story is broken down horizontally, it decomposes problems into technical layers. This may seem to match well with the technical skills of team members, i.e. they’re split amongst a database specialist, a UI specialist etc… but each user story can’t deliver the value to the end customer! At least not without interaction or integration with other layers, components, or other building blocks of the software system i.e. other user stories.
It is like slicing a cake horizontally, which does not allow for users to have the perfect bite :)
Click for detailed study
#UserStories #Agile #BusinessAnalysis #UserExperience
Please open Telegram to view this post
VIEW IN TELEGRAM
❤8🤩2👏1
How a Business Analyst Can Help a Project Manager 🙌🏻
At a meetup on May 14, Olga Kletskina will share a few scenarios of how a business analyst can help in establishing processes related to backlog management and communication within and beyond the team.
We stand for a practice-based approach – the speech is based on the speaker’s first-hand experience 🤩
🎟 Register here
⏰ Time: 19:00 (Minsk time)/18:00 (CET)
🕒 Duration: 1 hour
🗣 Language: Russian
📍 Offline: Andersen’s office in Minsk
💻 Online: The link to the stream will be sent to your email specified in the registration form
Join Andersen IT Community:
📱 BA/SA LinkedIn
At a meetup on May 14, Olga Kletskina will share a few scenarios of how a business analyst can help in establishing processes related to backlog management and communication within and beyond the team.
We stand for a practice-based approach – the speech is based on the speaker’s first-hand experience 🤩
🎟 Register here
⏰ Time: 19:00 (Minsk time)/18:00 (CET)
🕒 Duration: 1 hour
🗣 Language: Russian
📍 Offline: Andersen’s office in Minsk
💻 Online: The link to the stream will be sent to your email specified in the registration form
Join Andersen IT Community:
📱 BA/SA LinkedIn
👍4🔥3👏1
Media is too big
VIEW IN TELEGRAM
Hi everyone! Last week we had the pleasure to participate in a fantastic Business Analysis Meet Up in collaboration with IIBA Poland Chapter at vibrant Andersen Lab space 🙌
Together, we explored the evolving role of Business Analysts and the real impact of AI on business analysis. The discussions were thought-provoking.
A special thank to Tomasz Plebański and Sviatlana Varabyova for contributed their expertise and perspectives.
If you couldn’t attend or want to revisit the highlights - please, here is a full event recording here:
▶️ https://lnkd.in/dSVWkqep
Thank you once again to all attendees, partners, and the IIBA team for making this event a success. Let’s move beyond the buzzwords and focus on meaningful change together! 🙂
#AI #Innovation #IIBA #BusinessAnalysis #ProfessionalGrowth
Together, we explored the evolving role of Business Analysts and the real impact of AI on business analysis. The discussions were thought-provoking.
A special thank to Tomasz Plebański and Sviatlana Varabyova for contributed their expertise and perspectives.
If you couldn’t attend or want to revisit the highlights - please, here is a full event recording here:
▶️ https://lnkd.in/dSVWkqep
Thank you once again to all attendees, partners, and the IIBA team for making this event a success. Let’s move beyond the buzzwords and focus on meaningful change together! 🙂
#AI #Innovation #IIBA #BusinessAnalysis #ProfessionalGrowth
❤5🔥2🤩1
Hi Analysts,
Today We'd like to share some DOs and DON'Ts for BAs from experience.
"DO"s and "DON'T"s for Business Analysts:
1. DO
your research all the time. Technology and technical solutions are always evolving and you can find answers to your questions by researching.
2. DON'T
work as a call-center operator. Don't repeat the customer's words and do what they say without analyzing and verifying that it's really valuable. If you can't translate requirements into actionable items, you should improve it first.
3. DO
communicate with team often while you are still working on your output. Before presenting the solution to the team, always have their opinion, especially, tech team. Some solutions may not fit your project.
4. DON'T
set up meeting with stakeholders until you clearly set objectives from the meeting and know what questions to ask. Otherwise, you will have a chaotic picture of requirements.
5. DO
take notes. Because it's not only helpful to understand better, but also memorize the topics afterwards.
Note: Handwriting helps to memorize things much better.
6. DON'T
make extremely complicated diagrams just to use cool elements. Simpler the better for understanding.
#BATips #BusinessAnalyst #BACommunity #AnalystHub
Today We'd like to share some DOs and DON'Ts for BAs from experience.
"DO"s and "DON'T"s for Business Analysts:
1. DO
your research all the time. Technology and technical solutions are always evolving and you can find answers to your questions by researching.
2. DON'T
work as a call-center operator. Don't repeat the customer's words and do what they say without analyzing and verifying that it's really valuable. If you can't translate requirements into actionable items, you should improve it first.
3. DO
communicate with team often while you are still working on your output. Before presenting the solution to the team, always have their opinion, especially, tech team. Some solutions may not fit your project.
4. DON'T
set up meeting with stakeholders until you clearly set objectives from the meeting and know what questions to ask. Otherwise, you will have a chaotic picture of requirements.
5. DO
take notes. Because it's not only helpful to understand better, but also memorize the topics afterwards.
Note: Handwriting helps to memorize things much better.
6. DON'T
make extremely complicated diagrams just to use cool elements. Simpler the better for understanding.
#BATips #BusinessAnalyst #BACommunity #AnalystHub
❤13🔥5👍2👏1
🤝 MeetUp Recap: How Can a Business Analyst Help a Project Manager?
Yesterday, we had the pleasure of conducting a fantastic Meet up with our speaker Olga Kletskina on the topic “How Can a Business Analyst Help a Project Manager?”
💡 Here are the key takeaways from our discussion to point out:
✅Business Analysts (BAs) and Project Managers (PMs) have many overlapping areas within a project, which means constant collaboration is essential.
✅Both BAs and PMs regularly rely on each other’s support and expertise to achieve project goals.
✅Effective interaction between BAs and PMs directly influences project processes, the planning and delivery of functionality, and the quality of the final product.
✅The most important aspect of BA–PM collaboration is mutual respect, clear communication of requests with explanations, and alignment of expectations and deadlines.
A huge thank to you Olga for the engaging performance, sharing your expertise with our community, and to everyone who joined the discussion as well! Let’s continue fostering strong collaboration between BAs and PMs to drive our projects to success.
If you still have questions after the meetup, this is the best time and place to ask - drop them in the comments below!
#BusinessAnalysis #ProjectManagement #Teamwork #Collaboration #MeetUp #BACommunity #ProfessionalGrowth
Yesterday, we had the pleasure of conducting a fantastic Meet up with our speaker Olga Kletskina on the topic “How Can a Business Analyst Help a Project Manager?”
💡 Here are the key takeaways from our discussion to point out:
✅Business Analysts (BAs) and Project Managers (PMs) have many overlapping areas within a project, which means constant collaboration is essential.
✅Both BAs and PMs regularly rely on each other’s support and expertise to achieve project goals.
✅Effective interaction between BAs and PMs directly influences project processes, the planning and delivery of functionality, and the quality of the final product.
✅The most important aspect of BA–PM collaboration is mutual respect, clear communication of requests with explanations, and alignment of expectations and deadlines.
A huge thank to you Olga for the engaging performance, sharing your expertise with our community, and to everyone who joined the discussion as well! Let’s continue fostering strong collaboration between BAs and PMs to drive our projects to success.
If you still have questions after the meetup, this is the best time and place to ask - drop them in the comments below!
#BusinessAnalysis #ProjectManagement #Teamwork #Collaboration #MeetUp #BACommunity #ProfessionalGrowth
👍5🔥5❤2👏1
🤝 Understanding the Role of a Project Manager and Their Collaboration with Business Analysts
In our recent Meetup, we explored the vital collaboration between Project Managers (PMs) and Business Analysts (BAs). To deepen our understanding, let’s take a closer look at who a Project Manager is, their core responsibilities, and how they work together with BAs to ensure project success.
Who is a Project Manager?
According to PMBOK®, a Project Manager is the person appointed to lead the project team and is responsible for achieving the project’s objectives. The PM manages the project team to meet goals and stakeholder expectations while balancing competing project constraints with available resources.
Key Knowledge Areas of a Project Manager (PMBOK®):
🔹Project Integration Management
🔹Project Scope Management
🔹Project Schedule Management
🔹Project Cost Management
🔹Project Quality Management
🔹Project Resource Management
🔹Project Communications Management
🔹Project Risk Management
🔹Project Procurement Management
🔹Project Stakeholder Management
Core Responsibilities of a Project Manager:
🔸Planning and defining the project scope, schedule, and budget
🔸Leading and managing the project team
🔸Executing the project plan and monitoring progress
🔸Managing communications and stakeholder expectations
🔸Identifying and mitigating risks
🔸Overseeing quality and procurement processes
🔸Reporting on project status and ensuring timely delivery
How Do Project Managers and Business Analysts Collaborate?
✅ PMs and BAs have overlapping areas in projects, requiring constant interaction and mutual support.
✅ BAs help define clear requirements and translate business needs into actionable items, supporting PMs in scope and stakeholder management.
✅ Their collaboration directly impacts process optimization, functional delivery planning, and product quality assurance.
✅ Effective communication, mutual respect, clear requests with reasoning, and aligned expectations and deadlines are the foundation of their partnership.
Together, PMs and BAs form a powerful tandem that drives project success by combining strategic planning with detailed analysis and communication.
#ProjectManagement #BusinessAnalysis #PMBOK #Teamwork #Collaboration #ITProjects #BACommunity #ProjectSuccess #Leadership #StakeholderManagement
In our recent Meetup, we explored the vital collaboration between Project Managers (PMs) and Business Analysts (BAs). To deepen our understanding, let’s take a closer look at who a Project Manager is, their core responsibilities, and how they work together with BAs to ensure project success.
Who is a Project Manager?
According to PMBOK®, a Project Manager is the person appointed to lead the project team and is responsible for achieving the project’s objectives. The PM manages the project team to meet goals and stakeholder expectations while balancing competing project constraints with available resources.
Key Knowledge Areas of a Project Manager (PMBOK®):
🔹Project Integration Management
🔹Project Scope Management
🔹Project Schedule Management
🔹Project Cost Management
🔹Project Quality Management
🔹Project Resource Management
🔹Project Communications Management
🔹Project Risk Management
🔹Project Procurement Management
🔹Project Stakeholder Management
Core Responsibilities of a Project Manager:
🔸Planning and defining the project scope, schedule, and budget
🔸Leading and managing the project team
🔸Executing the project plan and monitoring progress
🔸Managing communications and stakeholder expectations
🔸Identifying and mitigating risks
🔸Overseeing quality and procurement processes
🔸Reporting on project status and ensuring timely delivery
How Do Project Managers and Business Analysts Collaborate?
✅ PMs and BAs have overlapping areas in projects, requiring constant interaction and mutual support.
✅ BAs help define clear requirements and translate business needs into actionable items, supporting PMs in scope and stakeholder management.
✅ Their collaboration directly impacts process optimization, functional delivery planning, and product quality assurance.
✅ Effective communication, mutual respect, clear requests with reasoning, and aligned expectations and deadlines are the foundation of their partnership.
Together, PMs and BAs form a powerful tandem that drives project success by combining strategic planning with detailed analysis and communication.
#ProjectManagement #BusinessAnalysis #PMBOK #Teamwork #Collaboration #ITProjects #BACommunity #ProjectSuccess #Leadership #StakeholderManagement
🔥7👍3❤2
How to create Web3 products with $100M+ ARR? 💡
On May 20 at 18:00 (CET), Andersen is hosting an online meetup with Maxim Krasnov, Founder of Coinstruct.tech and a blockchain economist.
We will discuss:
— Web3 trends and prospects: which products generate $100M+ per year;
— How to choose blockchain infrastructure: Ethereum, Solana, TON, L1 vs L2;
— Smart contract frameworks: ERC-20, ERC-721, ERC-1155, ERC-4626 and their optimization;
— Assets in Web3 (FT and NFT);
— Business models & Go-to-market for a blockchain-based startup.
The meetup will be useful for: startup founders, CTOs, product managers, Web3 developers, investors, and everyone building blockchain projects.
🎟 Register here
⏰ Time: 18:00 (CET)
🕒 Duration: 1 hour
🗣 Language: English
💻 Online: We'll send the streaming link to the email provided during registration
See you!
On May 20 at 18:00 (CET), Andersen is hosting an online meetup with Maxim Krasnov, Founder of Coinstruct.tech and a blockchain economist.
We will discuss:
— Web3 trends and prospects: which products generate $100M+ per year;
— How to choose blockchain infrastructure: Ethereum, Solana, TON, L1 vs L2;
— Smart contract frameworks: ERC-20, ERC-721, ERC-1155, ERC-4626 and their optimization;
— Assets in Web3 (FT and NFT);
— Business models & Go-to-market for a blockchain-based startup.
The meetup will be useful for: startup founders, CTOs, product managers, Web3 developers, investors, and everyone building blockchain projects.
🎟 Register here
⏰ Time: 18:00 (CET)
🕒 Duration: 1 hour
🗣 Language: English
💻 Online: We'll send the streaming link to the email provided during registration
See you!
👍2🔥2❤1👏1
✅ The AI Supply Chain: What Every Business Analyst Should Know
A recent paper from the Bank for International Settlements (BIS, No. 154) outlines a five-layered supply chain behind modern artificial intelligence systems. Understanding this structure is essential for anyone working with AI integration, risk management, or strategic tech procurement.
5️⃣ The five layers include:
1. Hardware – This is the computing foundation: GPUs, TPUs, and other specialized chips required for AI training. The market is highly concentrated, with Nvidia holding over 90% of the data center GPU market.
2. Cloud Infrastructure – Providers like AWS, Microsoft Azure, and Google Cloud dominate global access to AI-scale computing power. Switching between platforms is costly, reinforcing vendor lock-in and limiting competition.
3. Training Data – The “raw materials” of AI. With high-quality public data becoming scarce, large firms increasingly rely on proprietary data ecosystems. This gives big tech companies with extensive user data a structural advantage.
4. Foundation Models – These are the general-purpose large language models (LLMs) that underpin most AI applications. While over 300 models exist, just a few players (OpenAI, Google, Anthropic, Meta) control the majority of market share due to high entry costs and strong first-mover advantages.
5. Applications – End-user tools like ChatGPT or Copilot represent the final stage. Even here, the market exhibits “winner-takes-most” dynamics, raising long-term questions about user choice and innovation paths.
The report warns that this concentration—especially in the hardware and cloud layers—poses systemic risks: reduced competition, heightened cybersecurity exposure, and dependencies that could affect financial and operational stability globally.
For organizations building AI strategies, these dynamics should be considered carefully. Who controls your inputs, infrastructure, and tools increasingly shapes not just performance and cost, but also resilience and strategic independence.
🔥 BIS concludes that addressing these risks will require both stronger regulation and greater international cooperation. But for now, the business community must navigate an ecosystem increasingly shaped by a small number of dominant players.
#ArtificialIntelligence #BusinessAnalysis
#AIInfrastructure
A recent paper from the Bank for International Settlements (BIS, No. 154) outlines a five-layered supply chain behind modern artificial intelligence systems. Understanding this structure is essential for anyone working with AI integration, risk management, or strategic tech procurement.
5️⃣ The five layers include:
1. Hardware – This is the computing foundation: GPUs, TPUs, and other specialized chips required for AI training. The market is highly concentrated, with Nvidia holding over 90% of the data center GPU market.
2. Cloud Infrastructure – Providers like AWS, Microsoft Azure, and Google Cloud dominate global access to AI-scale computing power. Switching between platforms is costly, reinforcing vendor lock-in and limiting competition.
3. Training Data – The “raw materials” of AI. With high-quality public data becoming scarce, large firms increasingly rely on proprietary data ecosystems. This gives big tech companies with extensive user data a structural advantage.
4. Foundation Models – These are the general-purpose large language models (LLMs) that underpin most AI applications. While over 300 models exist, just a few players (OpenAI, Google, Anthropic, Meta) control the majority of market share due to high entry costs and strong first-mover advantages.
5. Applications – End-user tools like ChatGPT or Copilot represent the final stage. Even here, the market exhibits “winner-takes-most” dynamics, raising long-term questions about user choice and innovation paths.
The report warns that this concentration—especially in the hardware and cloud layers—poses systemic risks: reduced competition, heightened cybersecurity exposure, and dependencies that could affect financial and operational stability globally.
For organizations building AI strategies, these dynamics should be considered carefully. Who controls your inputs, infrastructure, and tools increasingly shapes not just performance and cost, but also resilience and strategic independence.
🔥 BIS concludes that addressing these risks will require both stronger regulation and greater international cooperation. But for now, the business community must navigate an ecosystem increasingly shaped by a small number of dominant players.
#ArtificialIntelligence #BusinessAnalysis
#AIInfrastructure
❤3🔥2👏1
🎯 Giveaway of 3-month Telegram Premium!
Do you want to upgrade your Telegram and use all its premium features for free? We’ve got a chance for you! 🎉
📌 How to participate?
Just subscribe to the community’s channels on Telegram, and you’ll automatically become part of the giveaway!
🎁 On June 6, Telegram will randomly select three lucky winners who will receive a 3-month Premium subnoscription! 😎
🚀 Take part and enjoy all Premium benefits!
🔗 Details and the link to participate are here: link
Don’t miss your chance – join the giveaway now! 💥
Do you want to upgrade your Telegram and use all its premium features for free? We’ve got a chance for you! 🎉
📌 How to participate?
Just subscribe to the community’s channels on Telegram, and you’ll automatically become part of the giveaway!
🎁 On June 6, Telegram will randomly select three lucky winners who will receive a 3-month Premium subnoscription! 😎
🚀 Take part and enjoy all Premium benefits!
🔗 Details and the link to participate are here: link
Don’t miss your chance – join the giveaway now! 💥
👍4🔥3❤1