A guide to business analysis
Download as PPTX, PDF0 likes288 views
The presentation emphasizes improving the efficiency of business analysts (BAs) by following a structured approach that includes identifying stakeholders, capturing and categorizing client requirements, and developing mockups. It highlights the importance of understanding both functional and technical requirements, prioritizing them, and ensuring effective communication with clients for project alignment. Additionally, securing a signed agreement from the client is crucial to mitigate ambiguities later in the project.
A guide to business analysis
- 1. Seasia Consulting There has to be a better way (+1) 240-241-6897 Seasia InfoTech There has to be a better way (+1) 240-241-6897
- 2. • The main emphasis of this presentation is to increase the efficiency/output of the Business Analysts(BAs). • The following approaches will assist BA’s in achieving the desired output. In order to get the optimum results we should follow steps given below: – Identify Key Stakeholders – Capture Client’s Requirements – Categorize Requirements – Interpret and Record Requirements – Sign Off
- 4. • Identify the key people who will be affected by the project. • Identify end-users who will use the solution, product, or service. • Our project should intend to meet end-users needs, so we must consider their inputs.
- 5. • Ask the client, for their requirements for the new product or service. What do they want and expect from this project? We may use the following techniques: – Using the use case diagrams: E-R diagram helps us to know how the system is communicating with the users and vice-versa – Using group discussions: Discuss the requirements with the other BA. – Building prototypes (Initial Mockups): Based on the understanding design the initial mockups to get more clear picture of the application/product.
- 6. • The next step in the analysis phase is framing the work breakdown structure (WBS). The WBS should contain the following information: – Functional Requirements – These define how a product/service/solution should function from the end-user's perspective. These also describe the features and functions with which the end-user will interact directly.
- 7. – Technical Requirements – These define the technical issues that must be considered to successfully implement the process or create the product. – Transitional Requirements – These are the steps needed to implement the new product or process smoothly.
- 8. • Once we have gathered and categorized all of the requirements, we shall determine which requirements are achievable, and how the system or product can deliver them. We should always keep the following points in consideration while recording the requirements: – Define Requirements Neatly – Prioritize the requirements – Analyze Feasibility Once these steps are accomplished, document the key results and pass the documents to all the persons involved in the project directly or indirectly.
- 9. • Finally, make sure you get the signed agreement of client or an individual who is outsourcing the project/application i.e. get the DoU approved from the client. This formal commitment will play an important part in ensuring that the project does not suffer from any ambiguity in the later stages.