Introduction to Business Analysis
- 1. Page 1Classification: Restricted Business Analysis Training Introduction to Business Analysis
- 2. Page 2Classification: Restricted Agenda Introduction to Business Analysis • What is a Project? • Business Process – What and Why? • Who is a Project Manager? • Who is a Business Analyst? • What is Business Analysis and why is it important? • Roles, Responsibilities and necessary Skills for a Business Analyst
- 3. Page 3Classification: Restricted Trainer’s Introduction About me • Name – • Education – • Work Experience -
- 4. Page 4Classification: Restricted What is a Business Process? • It is a set of related tasks, performed to accomplish a specific organizational goal. It can also be defined as a series of logically structured activities that produce a specific service or product for customers.
- 5. Page 5Classification: Restricted Why do we need a Business Process? • To become and remain successful and competitive, businesses must continuously improve their processes. • Failure to do so is likely to result in higher costs, lower revenues, less motivated employees and fewer satisfied customers.
- 6. Page 6Classification: Restricted Need for Automating the Business Processes? • Automation is moving the needle of business efficiency and simplifying human lives in general. • Businesses that have automated their processes cut price, save time, and employ their manual workforce to solve more intelligent problems. • They let machines do the rote tasks, while eliminating the chances of human errors.
- 7. Page 7Classification: Restricted Benefits of Automation Streamline Communication Enforce Accountability
- 8. Page 8Classification: Restricted Benefits of Automation Minimize Costs and Manual Errors Keep a Tab on your Business Processes
- 9. Page 9Classification: Restricted How do you Automate Business Processes?
- 10. Page 10Classification: Restricted Industry Based on Function • Product Based Company – Building their own product and selling it in market • Service Based Company – Building product, application or part of them, for other companies and their clients
- 11. Page 11Classification: Restricted What is a “Project”? What is a “Project” ?
- 12. Page 12Classification: Restricted Project • A Project is a temporary endeavor undertaken to create unique product, service, or result. • The temporary nature of project indicates a definite beginning and end. Project Types: • Fixed Bid Projects • Billing Projects
- 13. Page 13Classification: Restricted IT Project Structure Business Stakeholders Subject Matter Experts (SMEs) Technology Head Technical Architect Project Manager QA Manager Production Support Junior Technical Architects/ Assistants Technical Lead Developer QA Leads QA Analysis
- 14. Page 14Classification: Restricted Pre-Project Activity • Client realizes his need for a software application. • He will do an initial analysis on the required features of the Software Application and will prepare Requirements Document. Request for Proposal (RFP) RFP is a document in which Business need appear. Request for Information (RFI) is a form that is attached to RFP Request for Quotation (RFQ) A request for quotation (RFQ) is a standard business process whose purpose is to invite suppliers into a bidding process to bid on specific products or services Statement of Work (SOW) A document that defines project-specific activities, deliverables, and timelines for a vendor providing services to the client.
- 15. Page 15Classification: Restricted Reason for Project Initiation • Projects plays essential role in Growth and Survival of Organization in today’s rapidly changing competitive business environment and also in managing the change and achieving the strategies of the enterprise. • All projects are aimed to help the project sponsor in one way or the other to reduce cost, increase revenue or increase efficiency or ensure transparency etc. • Projects may be initiated in response to a business strategy in order to, • Cater market demand • Tackle competition • Increase market share • Comply with regulation • Create a competitive edge • Exploit emerging opportunity and many other
- 16. Page 16Classification: Restricted What is Business Analysis? • Business Analysis is the set of tasks, knowledge, and techniques required to identify business needs and determine solutions to business problems. Solutions often includes : • Systems development component • Process improvement • Organizational change
- 17. Page 17Classification: Restricted Why is Business Analysis important? • Business analysis helps stakeholders achieve a shared understanding of the organization’s needs. • This shared understanding puts the team in a position to make legitimate recommendations for those needs, and ultimately puts the organization in a position to move forward with the set of recommendations that best meets those needs.
- 18. Page 18Classification: Restricted Who is a Business Analyst? Business Stakeholders Subject Matter Experts (SMEs) Technology Head Project Manager QA Manager Production Support Junior Technical Architects/ Assistants Technical Lead Developer QA Leads QA Analysis Business Analyst Technical Architect
- 19. Page 19Classification: Restricted Role of a Business Analyst • A Business Analyst works as a liaison among stakeholders in order to elicit, analyze, communicate and validate requirements for changes to business processes, policies and information systems. • The Business Analyst understands business problems and opportunities in the context of the requirements and recommends solutions that enable the organization to achieve its goals. • A Business Analyst is responsible for ensuring the project’s outputs meet the requirements of the business and that they are fit for purpose.
- 20. Page 20Classification: Restricted What are the Responsibilities of a Business Analyst?
- 21. Page 21Classification: Restricted Essential Skills of a Business Analyst
- 22. Page 22Classification: Restricted Knowledge areas of BA
- 23. Page 23Classification: Restricted Project Life Cycle Methodology Technical Architect 1 Project Initiation 1.Define Scope 2.HireTeam 3.Develop Business Case 2 Project Planning 1.Defineand record requirements,constraints, and assumptions 2.Identify project team and define rolesand responsibilities 3.CreatetheWork Breakdown Schedule (WBS) 4.Develop change management plan 5.Identify risksand define risk strategies 6.Obtain plan approval 3 Project Execution 1. Execute tasksdefinesin the project plan 2. Implement the procurement of project resources 3. Manage resource allocation 4. Implement approved changes 5. Measure project performance 6.Verify and manage change to the project 7. Ensure project deliverable conform to quality standards 8. Monitor all risks 4 Project Closure 1.Obtain final acceptance for theproject 2.Obtain financial,legal, and administrative closure 3.Releaseproject resources 4.Document and communicatelessons learned 5.Createand distribute final project report 6.Archiveand retain project records 7.Measurecustomer satisfaction Montoring andControl
- 24. Page 24Classification: Restricted Role of a BA & PM PM: A Project Manager is ultimately responsible for ensuring the objectives of a project are met and that the outputs are delivered on time, to cost and to quality. BA: A Business Analyst is responsible for ensuring the project’s outputs meet the requirements of the business and that they are fit for purpose.
- 25. Page 25Classification: Restricted Knowledge Areas BA PM • Enterprise Analysis Integration • Planning & Management Scope Management • Requirements Elicitation Time Management • Requirements Analysis & Documentation Cost Management • Requirements Communication Human Resource Management • Requirements Implementation Communication Management Quality Management Risk Management Procurement
- 26. Page 26Classification: Restricted How do a PM and BA work together? Initiation Requirements Design & Implementation Planning Construction QA Implementation Closure The Execution of a Project PM • Scope • Budget • Team • PIR• Planning • Execution & Control • Document Requirements • System Checkout • Scope • Design • Testing & Training Strategies • Test Case Creation • Test • UAT • Train • PIR BA
- 27. Page 27Classification: Restricted Topics to be covered in next session • SDLC (Software Development Life Cycle) • Types of SDLC Methodologies • Waterfall Approach • Incremental Approach • Iterative Approach • Difference between Incremental and Iterative • Prototype Approach • Spiral Approach • Rational Unified Process • Inception • Elaboration • Construction • Agile Methodology • Scrum Lifecycle