Business Analyst
MEMAR
Total years of experience :2 years, 6 Months
In MEMAR, Currently working as a Scrum master for an ERP Implementation project which follows agile software development life cycle. Gained proficiency in agile software development tools such as JIRA and Confluence. JIRA help in end to end management of the project where as confluence is an efficient content management system.
Other activities include collaboration with the technical team for resolving the issues raised by them, scheduling and conducting the meeting as per the agile software development model, preparation of Test cases and active support for the UAT(User acceptance testing).
In EY, as a business analyst I have worked on various phases of the project starting from proposal preparation to the early life support after the product delivery. I had also developed my process analysis skills mainly using BPMN as a part of my stretch goal. Overall the areas which I have worked is described in brief bellow.
Dealing with requirements:
As a Business Analysts I have taken lead role in: • Assisting with the business case • Planning and monitoring • Eliciting requirements • Requirements organization • Translating and simplifying requirements • Requirements management and communication • Requirements analysis • Process modelling
I have also designed or review of test cases, process change requests, and had managed a project’s scope, acceptance.
Preparation of deliverable:
Business Analysis Plan This document contains the following key elements Background, Business Drivers, Problem Statement, Vision, Dependencies, Stakeholder Engagement Plan.
Business Requirements Specification The business requirements document will include Refined Business Drivers, Problem Statement, Stakeholder Model, Business Domain Model, Business Use Cases, Business Activity Diagrams, Business Requirements.
Business Case Business case is developed after writing the business requirements in order to capture all requirements. The key elements of a business case are Background, Current Situation / Problem Statement, Options Analysed, Recommendation, Costs and Benefits and Risks.
Functional & Non-Functional Specification The key elements of the functional specification are System Use Cases, User Requirements, System Activity Diagrams, Class Diagrams. Non-functional requirements must be associated with specific project functionality. The key elements of the non-functional requirements specification are Hardware Requirements, Software Requirements, Performance Requirements, Supportability Requirements etc.
Projects within various domains are being handled. Appreciations were received from the client for the Planning and Timely Submission of deliverable and Leadership and Coordination qualities expressed during the various projects.
Marketing Analysis of spare parts of Volvo heavy Vehicles
Key contributions: Analysed sales activities, marketing campaigns, organizations, customers, pricing, and competitors in detail, with charts, graphs and explanatory texts. Developed research projects for specific business issues - Integrated market research information into company system to develop new leads. Analysed metrics in order to identify effect-cause relationships between financial outcomes and marketed actions, thus raising profitability.
Areas of Impact: Analysed competition to evaluate market penetration. Effectively researched areas of the market regarding customer needs and brand perceptions. Worked in coordination with Product Management to identify possible opportunities. Designed focus groups as well as surveys to capture relevant market research data. Carried out customer-satisfaction surveys, compiling results into detailed reports. Built marketed dashboards, enabling visualization of indicators of fundamental performance. Conducted regular industry analysis: Social, political, technological, and economical.
I have done my project with Keltron.