Describe your BA experience

I have three and a half years of experience as a Business Analyst (BA). Before joining Andersen, I gained managerial experience in the wholesale and financial services industries. This background has provided me with the unique advantage of having worked on both sides of business analysis activities.

My experience spans

various domains, including corporate, fintech, and the B2B-B2C domain, as well as e-commerce. In terms of skills and activities (when it comes to my skill set), I'm pretty good at conducting interviews and organizing, as well as facilitating inception workshops for discovery phases. These workshops involve working closely with stakeholders to understand their needs and how these needs can be transformed into tangible features.

I gained significant experience working on discovery phases in my last two projects. I joined them from the very beginning, so I had to go through the entire process from start to finish. This meant that initially, I had to identify the stakeholders, find my stakeholders, organize meetings with them, understand their business objectives, their desires, and their requirements, document these, reflect on them in the documentation, analyze them, and so on. In essence, the entire spectrum of tasks that a business analyst is supposed to perform was completed.

And since I've touched on the topic of stakeholders, I would like to say that in my work managing stakeholders, I often lean on tools like the RACI matrix, but sometimes I find the Impact-Interest Matrix does a better job.

On top of that, requirement management is a big part of my job. This includes a range of activities, including identifying, documenting, analyzing, and tracking requirements throughout the project lifecycle. My approach ensures that stakeholder needs are accurately captured and addressed, contributing to the successful delivery of each project.

• Requirement Elicitation: This involves gathering requirements from stakeholders through various methods such as interviews, surveys, workshops, brainstorming sessions, and observation. The goal is to collect a comprehensive set of requirements that reflect the needs and constraints of the stakeholders.
• Requirement Documentation: Once requirements are gathered, they need to be clearly and concisely documented. This can be done using requirement specification documents, user stories, use cases, or product backlogs. Good documentation should be understandable, unambiguous, and comprehensive.
• Requirement Analysis: This step involves reviewing the requirements for feasibility, clarity, and potential conflicts. It may involve prioritizing requirements based on their importance, dependencies, and impact on the project.
• Requirement Validation: In this phase, stakeholders review the requirements to ensure they accurately reflect their needs and expectations. This often involves formal review sessions or approval processes.
• Requirement Verification: This is the process of ensuring that the developed system or product actually meets the documented requirements. It involves testing and other quality assurance practices.
• Requirement Change Management: Requirements can change for various reasons. Effective requirement management involves a controlled process for managing requirement changes, including assessing the impact of the change, getting necessary approvals, and updating documentation and plans.
• Traceability: Establishing a traceability matrix helps in tracking each requirement through the lifecycle of the project, ensuring that all requirements are addressed and tested. This is crucial for understanding the impact of changes and verifying the final product.
• Use of Requirement Management Tools: Various tools are available to help manage requirements. These tools can help in documenting, organizing, tracking, and reporting on requirements. They often provide functionalities for collaboration, version control, and integration with other project management tools.
• Communication and Collaboration: Regular communication with stakeholders is vital throughout the requirement management process. This ensures that everyone has a shared understanding of the requirements and any changes to them.
• Agile Requirement Management: In agile methodologies, requirements are managed differently. They are often captured as user stories in a product backlog and are continuously refined and prioritized throughout the project.
• Modeling Techniques: Sometimes, especially in complex projects, modeling techniques like UML (Unified Modeling Language), BPMN (Business Process Model and Notation), or ER diagrams (Entity-Relationship diagrams) are used to represent requirements in a visual format.
• I have experience of working with Microsoft Power BI (ETL), I know how to work with data and how to work with databases

UML and BPMN—and because it would look strange if, for example, I brought a classic sequence diagram to a stakeholder, they most likely won't understand it because, well, some knowledge about what UML is and what diagrams look like is needed. Therefore, I often take Figma and draw some diagrams, some flowcharts, so that the most important thing is achieved - clarity. My primary goal is to make the diagram understandable

• I also have experience with Microsoft Power BI and databases.
  I've worked with PostgreSQL and SQL Server applications, handling SQL queries for both PostgreSQL and Oracle. I am capable of working with SQL, creating queries, and extracting data in table formats. While I may not know absolutely everything, I have the necessary skills to gather the critical information needed for business analysis. From my perspective, this ability is valuable for the team, as I do not have to distract the developers every time when I need info from DB.

As to the applications I use in my work, the major of them are Confluence and Jira.

And I would like to say a word or two about my current project:
Our team  joined this project about a year ago. We were brought in to develop a music streaming app, kind of like Apple Music, YouTube Music, Spotify, and Soundcloud. It was for a big client, the largest mobile operator in Uzbekistan. Their business goal was  to boost profits by offering their existing mobile subscribers a music app subscription, especially focusing on Uzbek music. We had to develop application and backoffice application and had a lot of logic and the value of my work as a business analyst was in describing a huge amount of business logic that was present both in the app and in the backoffice, and in analyzing it. Plus, value of BA on this project was in ensuring that the development and execution align closely with both the business objectives and the end-users' needs.
Our team