business analyst online training
DESCRIPTION
UGS provides Business Analyst Online Training in India, usa, canada,australia, UK, australia, ireland, hyderabad,canada,business analyst online training courses,Saudi Arabia,Center .TRANSCRIPT
Business analyst
Business Analysis Training Brochure
Business Analyst
Duration Normal course25 hours /one month/daily one hour
Fast track course25hours/15days/daily two hours/DURATION
Tools
Ms visio --- UML DIAGRAMS/DFDRATIONAL ROSE---UML DIAGRAMS/DFDMS WORDBRD/SRS/DRD/FRD document preparationsERD/TEST CASE PREPARATION
TEMPLATESBRD TEMPLATEFRD TEMPLATEDRD TEMPLATESRS TEMPALTETEST CASE TEMPLATEUSE CASE DOCUMENT TEMPLATEALL UML DIAGRAMS TRAINING/TEMPALTESBA COURSERESUMESRESUME TIPSRESUME DEVELOPMENTSPROJECTS FOR RESUMES TO INCLUDEINTERVIEW QUESTIONSINTERVIEW TIPSCASE STUDIESLIVE PROJECTS IN ALL DOMAINSTIPS TO WORK AS BA IN IT COMPANY
BUSINESS ANALYST OPENINGBusiness Analyst Training IntroPresented byChandra, Sr.Business Analyst 9AgendaBusiness Analysis Definition
Business Analyst Skills and Roles & Responsibilities.
Fundamentals of Requirements Elicitation
BA Training Course Structure and Placement Assistance
Questions10Business Analysis Definition IIBA defines Business analysis as the set of tasks, knowledge, and techniques required to identify business needs and determine solutions to business problems. IIBA ( International Institute of Business Analysis) Solutions often include a systems development component, but may also consist of process improvement or organizational change.Thus, business analysts are often the liaisons between business and solution development (oftentimes IT), can-vassing the enterprise to understand business needs, issues and opportunities in order to recommend solutions that address those needs most effectively and efficiently. 11
Business Analyst Skills
who follow a chain of reasoning that leads from problem definition to implemented solutions and maintaining the integrity and coherence of the chain is the work of the Business Analyst. Owners defines measures of success and targets Money! Business Analysts confirm & document Strategists determine the strategy to hit the targets Business Analysts do market research, create strategy, challenge & document Sponsors establish a Programme that delivers the strategy Business Analysts document Programme TOR and build the Business Case (TOR : Terms of Reference)Programme Managers Institute Projectsthat implement the programme Business Analysts document the Project TOR Business analysts specify requirements for Projects in the Business Model Systems Analysts IT design solutionthat satisfies the requirements Business Analysts protect requirements & document compromises build solution Business Analysts protect requirements & document compromises IT and the Business test solution Business Analysts ensure tested against requirements Project managers Implement solution Users Accept solution Business Analysts help with -MEASURING BENEFITS REALISATION Business Analysts help with -Process and data migration -Cutover planning -Rollout POST-IMPLEMENTATION Business Analysts feed back to the Owner how well their measure of success has been achieved Scope Of The Business Analyst Role Vs SDLC 14Fundamentals of Requirements ElicitationAnswer Following Question When ? : Analysis
What ? : BRS
Why ? : Tools & Tech..
Who? : SMEs,Rteam,TSMEs
How? : Process 3D MethodRequirements Discovery ProcessFinally Business Analysis is Not
In Conclusion Business Analysis its not rocket science it is science (not a [dark] art) science has the scientific method Business Analysis has many structured methods All structured methods must be fundamentally the same as they must all analyze problems analyze the scope of the solution analyze functional and non-functional requirements manage requirements in to design & delivery What is Business AnalystIIBA Definition of a Business Analyst:
Business Analysts are responsible for identifying business needs.The Business Analyst is responsible for requirements development and requirements management. Specifically, the Business Analyst elicits, analyzes, validates and documents business, organizational and/or operational requirements. Solutions are not predetermined by the Business Analyst, but are driven solely by the requirements of the business. Solutions often include a systems development component, but may also consist of process improvement or organizational change. The Business Analyst is a key facilitator within an organization, acting as a bridge between the client, stakeholders and the solution team.Business Analysis is distinct from financial analysis, project management, quality assurance, organizational development, testing, training and documentation development. International Institute for Business Analysis http://www.iiba.com
Usually assigned to the project after it has startedResponsible for bridging the gap between the Business and ITLearn the business inside and outEssentially the architect of effective business systemsJob title, definition and responsibilities viewed inconsistently across the industry
BusinessTechnologyBusiness Analyst Working Domains Banking & financial InsuranceHealth careHRMTelecomAirline Marketing or manufacturing
BA is going to work on different domains depends upon company projects
insurancetelecombankinghealthcareHRMEXAMPLECEAT Company is a client
Business Analyst clientIt companyIBMCEAT GATHERING REQUIREMENTSDesign developersTesting engineers BUSINESS ANALYSTBA/BRDPROJECT MANAGERPRODUCT MANAGER/INTERNAL REQUIREMENTSEXTERNAL CLIENTSPRODUCT BASED COMPANYCLIENTS EXTERNAL REQUIREMENTSCLIENTS MEETINGBDM SALESCLIENTSGOESSALES DICUSSION ON PROJECT ,TECHNOLOGIES,ABOUT OUR COMPANY STRUCTURE AND WORK OUTLETS WITH CLIENTSFINALLY CLIENTS WANTS TO MAKE KICK-OFF MEETING WITH OUR COMPANY LEADS TO DICUSS ABOUT PROJECTHOW THE PROJECTS ARE COMING TO ITCOMPANY
BDM AFTER FINISHING THE COMMUNICATION WITH CLIENTS REGARDING THE PROJECTS WHEN THE CLIENT LOOKING FOR PROJECT DEVELOPMENT
NOW BEFORE STARTING OF DEVELOPMENT OF SYSTEM THE CLENT WANT TO MAKE KICK OFF MEETING WITH OUR COMPANYKICK OFF MEETINGThe Kickoff Meeting is the first meeting with the project team and the client of the project. This meeting would follow definition of the base elements for the project and other project planning activities. This meeting introduces the members of the project team and the client and provides the opportunity to discuss the role of each team member. Other base elements in the project that involve the client may also be discussed at this meeting (Schedule, Status Reporting, etc.).
The basic format of a kickoff meeting includes the roles of and contributions from the stakeholders. It also mentions the risks and issues involved, particularly those that may affect project schedules and lead to decreased customer satisfaction. This is the point at which help needed from stakeholders is explicitly mentioned.
If there are any new team members, the process to be followed is explained so as to maintain quality standards of the organization. Clarity is given by the project lead if there exists any ambiguity in the process implementations....
There is a special discussion on the legalities involved in the project. For example, the design team interacting with the testing team may want a car to be tested on city roads. If the legal permissions are not mentioned by the concerned stakeholder during kickoff, the test may get modified later to comply with local traffic laws (this causes unplanned delay in project implementation). So, it was best to have a discussion about it in the kickoff meeting and follow it up separately, than to assume stuff and later be forced to replan test procedures.
The kickoff meeting is an enthusiasm-generator for the customer and displays a full summary of the project so far. By displaying a thorough knowledge of the goal and steps on how to reach it, confidence is put in the customer
WHO IS GOING INVOLVE IN KICK OFF MEETING
Project managerPresentation regarding the project development in means of1.cost2.duration3.quality4.risk 5.development processProject plan/scope/charterANALYSISBA1-15 DAYS60,000DESIGNDESIGNERS1535 DAYS1LAKHSCODINGPROGRAMMERS35---50DAYSXXXXTESTINGTEST ENGINERS5065 DAYSXXXXDEPLOYMENTDEPLOY65---90DAYSXXXXXXKICK OFF MEETING
BA INVOLVES IN KICK OFFBA INVOLVES IN KICK OFF MEETINGDEPENDS UPON THE COMPANY
ACTION EVENTSWHAT EVER WE DICUSSED IN KICK OFF MEETING REGARDING THE PROJECT ISSUESACTION EVENTS ARE THE WHAT EVER RESPONSE IS COMING FROM THE CLIENTS REAGRDING THE QUERY IN PROJECT SCOPEEXAMPLEIN COST OF PROJECT DEVELOPMENT OF PROJECTACTION COMING FROM THE STAKE HOLDERSACTION REQUIREMENTS ARE WHAT EVER WE HAVE DICUSSED REGARDING THE DEVELOPMENT OF CLINETS PROJECT SCOPE.WE ARE GATHERING ALL THE REQUIREMENTSSUCCESS COMPLIATION OF KICK OFF MEETINGKICK OFF MEETING FINISHED SUCESSFULLY.CLIENT PREPARES THEIR BUSINESS PROPOSAL AND SEND TO IT COMPANY PMPM PREPARES THE BUSINESS PROPSALS FOR CLIENTS PROJECT DEVELOPMET
PROJECT MANAGER/LEAD BA PREPARES
BUSINESS PROPOSALBA HAS TO GO THROUGH WITH BUSINESS PROPSALGATHER INTERNAL REQUIREMENTSBEFORE STARTING REQUIREMENT GATHERING FROM CLIENTS OR INTERACTION WITH CLIENTSBA HAS DO SURVEYS REGARDING THE CLIENTS COMPANYSURVEYSPRIMARY DATA COLLECTION 1.ONLINE MARKET RESARCH 2.FACE TO FACE INTERACTION WITH CLIENTSSECONDARY DATA COLLECTION 1.HISTORICAL DATA 2.PREVIOUS DOCUMENTSTHESE SURVEYS FOR INTERNAL REQUIREMEMNTS FEEDBACK ONLY.
AS-IS AND TO-BEAs-Is study means studying the business process of theclient. The BUSINESS ANALYST goes to the client's place and gets this document. Once the As is document is ready theconsultant based on the client's requirement prepares theTo-Be document which means how the business of the clientmust be. This whole process takes place in the Second phaseof ASAP which is the Blueprint Phase.
Business analyst topicsRoles of BASDLC METHODSANALYSISDESIGNCODINGTESTING IMPLEMENTATION
BABA ROLECLENTSIT COMANYCLIENTS WANT TO MAKE AN INTRANET ON SHAREPOINTDESIGNERSDEVELOPERSREQUIREMENTSBABA Role - The PastElicitationAnalysisElicitationSpecificationValidation andDocumentationRequirements PhaseBA Role The Future A Critical Role Throughout the Project Life CycleEnterpriseAnalysisStrategic PlanningRequirementsDesignConstructionTestDeliverOperationsandMaintenanceDeactivateStudy PeriodImplementation PeriodImplementation Period (continued)Operations PeriodBusiness Analyst Role - Study PeriodThe executive team cannot affect the transition to a strategy-focused organization alone
Information, process, tools and facilitation are provided by the Business Analyst to enable the organization to shift focus and activities to be strategy driven\
Conduct analysis to inform the portfolio planning team
Create and maintain the business architecture Conduct feasibility studies to determine optimal solutionPrepare the business case
Planning Business Analysis activitiesRequirements elicitation Requirements analysisRequirements specification
Requirements validation & verificationRequirements allocation and tracingRequirements change managementOrganizational change managementBusiness Analyst Role - Implementation Period
SDLC METHODSANALYSISDESIGNPROGRAMCONSTRUCTIONTESTINGIMPLEMENTATIONWHY DOES A PROJECT NEED BA AND PM
MOSCOW TECHNIQUEMOSCOW
MUST SHOULD COULD WOULD
HOW TO MAP REQUIREMENTS FROM CLIENTS AND PRIORTY FOR EACH REQUIREMENTS
MoSCoW is a prioritization technique used in business analysis and software development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement - also known as Moscow prioritization or Moscow analysis.According to A Guide to the Business Analysis Body of Knowledge, version 2.0[1], section 6.1.5.2, the Moscow categories are as follows:M - MUST: Describes a requirement that must be satisfied in the final solution for the solution to be considered a success.S - SHOULD: Represents a high-priority item that should be included in the solution if it is possible. This is often a critical requirement but one which can be satisfied in other ways if strictly necessary.C - COULD: Describes a requirement which is considered desirable but not necessary. This will be included if time and resources permit.W - WON'T: Represents a requirement that stakeholders have agreed will not be implemented in a given release, but may be considered for the future.
ZACHMAN METHOD5W+1HWHYWHENWHERE HOW WHATWHO
3D FRAME WORK FOR REQUIREMENT GATHERING 3DDISCOVERDISCRIEBINGDOCUMENT
3D MODEL FOR REQUIREMENTSBRDFRDDRD
BRDBRD- BUSINESS REQUIREMENT DOCUMENTFRD- FUNCTIONAL REQUIREMENTDOCUMENTSRS -SYSTEM REQUIREMENT DOCUMENTDRD -DATA REQUIREMENT DOCUMENT
BRD SHOULD BE COVERTED INTO FRD/DRDBRD/FRD/DRDCAPTURING CUSTOMER DETAILSBRDHOW YOU WANT SEARCHCAPTURING CUSTOMER DETAILS USING REGISTRATIONSTORE CUSTOMER DETAILSAVAILABLE TO CUSTOMERFRDWHAT KIND OF REQUIREMENTSNAMEAGESEXPROFILEDRDBRD STRUCTURE HOW TO PREPAREEVERY COMPANY HAS OWN STANDARDED TEMPLATEBRD1.INTRODUCTIONOVERVIEWPROJECT BACKGROUNDKEY STACKHOLDERS2.SCOPEINSCOPEOUTSCOPE3.FUNCTIONAL REQUIREMENTSUSE CASES DIAGRAMSUSE CASE DOCUMENTFUNCTIONAL REQUIREMENTS4.NON FUNCTIONAL REQUIREMENTSQUALITYPERFORMANCEAASURANCEHARDWARESOFTWARE5.DRD6.RTM
REVERSE ENGINEERING FOR REQUIRMENTSREQUIREMENTSVALIDATIONELICITATIONDOCUMENTMANAGE
SDLC MODELSWATER FALL MODELSPIRAL MODELRAD MODEL(RAPID APPLICATION DEVELOPMENT)RUP MODEL RATIONAL UNIFIED PROCESSV- SHAPED MODELINCREMENTAL MODELAGILE WITH SCRUMAGILE WITH XPRTMREUIREMENT TRACIBLITY MATRIX
REQ.NOFEATURECOMPONENTCATEGORYTESTCASEREQUIREMENT ELICITRATION PROCESSINTERVIEWING & QUESTIONAIREJAD/WORKSHOPS/FOCUSGROUPBRAINSTROMINGPROTOTYPE/STORY BOARD/MARKUP/WIREFRAMEUSE CASE MODELSURVEYSREVERSE ENGINEERINGVIEWPOINTUSE CASE DIAGRAMEXAMPLE-- ATM CASH WITH DRAWNVISIT ATMUSER SELECTSINSERT CARDSYSTEM VALIDATES CARDENTER VALID PINSYSTEM VALIDATESSYSTEM OPENS LIST OPTIONSANALYSISSTRUCTRAL ANALYSIS OOADDFD UML DIAGRAMSSFCHIPOSTC
ANALYSISUMLCLASS OBJECTPACKAGECOMPOSITECOMPONENTDEPLOYMENTSTRUCTRAL DIAGRAMSUML DIAGRAMSBEHAVIOURAL DIAGRAMSUSECASE DIAGRAMSACTIVITY DIAGRAMSSTATE MACHINE CHARTS
INTERACTION DIAGRAMSCOMMUNICATIONSEQUENCE DIAGRAMSTIMING DIAGRAMSINTERACTION DIAGRAMS DESIGINGANALYSISDEVELOPMENTANALYSISTESTINGUNIT INTEGRATION TESTSYSTEM TESTINGUATMANUAL AUTOMATICMANUALLLDUIU2UNPROGRAMMERSSENIOR TESTINTEGRATIONSYSTEMUATHLLDBRD/FRDBRD/FRD1.TOP-BOTTOM2.BOTTOM-TOP3.SANDWICH1.FUNCTIONAL2.USABILTY 3.PERFORMANCE4.SECURITY1.ALPHA2.BETASTLC SOFWARE TEST LIFE CYCLETEST PLANTEST DESIGNTEST EXCUTIONBUG REPORTRESULT ANALYSISTEST SUMMARYDATA MODELINGCONCEPTUAL DESIGNLOGICALPHYHICAL
PROJECT MANAGEMENT SYSTEMPROJECT MANAGEM ENT PHASESINIATIONPLANNINGEXECUTIONMONITORING/CONTROLLINGCLOSING1.PROJECT INTEGRATION 2.PROJECT SCOPE3.PROJECT TIME4.PROJECT COST5.PROJECT QUALITY6.PROJECT HR7.PROJECT RISK8.PROJECT COMMUNICATION9.PROJECT PROCUREMENT10.SOCIAL & PROFESSIONALKNOWLEDGE AREASALL THE BEST FOR THE FUTUREWELCOME AS BUSINESS ANALYSTS
THANKS
COURSE DURATION --27HOURSBDM
CLIENT/STAKE HOLDERS(CEAT)
INTRANET HOME PAGE
TECHNOLOGY---SHARE POINT ---- JAVA ---- .NET
DATA STORAGE---- 3RD PARTY--SAP
KICK OFF MEETING
IT COMPANY
CLIENTS SIDE
1.PROJECT MANAGER2.BUSINESS ANALYST3.BDM4.TECHNICAL MANAGER5.DELIVERY MANAGER
KEY STAKEHOLDERSSubject matter ExpertsTechnical subject Matter ExpertsHead of Departments
MEETINGDISCUSSION REGARDING THE SYSTEM BUSINESS NEEDS
Kick- Off
Analyze
Design
Stabilize
UAT
Implement
Build
BUSINESS ANALYST
Use Case
KICK OFF MEETING
ACTION EVENTS
ACTION REQUIREMENTS
-End1
*
-End2
*
-End3
*
-End4
*
-End7
*
-End8
*
-End9
*
-End10
*
PROJECT MANAGER
Use Case
PREPARES THE RF
REQUEST FORPROPOSAL
REQUEST FORQUOTATION
REQUEST FORINFORMATION
BUSINESS PROPOSAL
-End1
*
-End2
*
-End3
*
-End4
*
-End5
*
-End6
*
-End7
*
-End8
*
-End9
*
-End10
*
-End11
*
-End12
*
-End13
*
-End14
*
-End15
*
-End16
*
PROJECT MANAGER
BUSINESS ANALYST
TEAM MEMBERS
PROGRAM MANAGER
CLIENTS INTERACTIONREQUIREMENTS
BEFORE INTERACTING WITH CLIENTS FOR REQUIREMENTS
BA SURVEYS
PRIMARY DATA COLLECTION
YES
SECONDARY DATA COLLECTION
NO
IN ORDER TO UNDERSTAND STRUCTURE OF CLIENTS COMPANY BEFORE GATHERING REQUIREMENTS
Project management Office
Program manager
PM handles multiple projects
Project Manager
PM handles single or more projects
BA
TECHNICAL LEAD
TEST LEAD
JUNIOR BA
INTERMEDIATE BA
DESIGNER
PROGRAMERS
DEVELOPERS
TEST ENGINEERS