Business Analysis: Essentialsstore.globalknowledge.net/course-overviews/NL/GK2919.pdfbrede kijk op...

GK2919 www.globalknowledge.com/nl-nl/ [email protected] 030 - 60 89 444

Business Analysis: Essentials

Cursusduur: 3 Dagen Cursuscode: GK2919

Beschrijving:

Nederlands:Het inrichten en verbeteren van bedrijfsprocessen is de focus van onze Business Analyse training. Bedrijfsprocessen zijn continu aanverandering onderhevig en dienen maximaal bij te dragen aan het realiseren van de bedrijfsdoelstellingen. IT is veelal één van de belangrijksteinstrumenten om bedrijfsprocessen effectief en efficiënt in te richten. Ingrijpende veranderingen binnen de IT zoals Outsourcing, Rightshoringen de Service georiënteerde Enterprise leiden momenteel tot een versterkte focus op de business en de bedrijfsprocessen. Tijdens dezeopleiding wordt uitgebreid aandacht besteed aan de vraag: hoe kan een organisatie IT goed inzetten en aansturen? De deelnemers krijgen eenbrede kijk op de veelheid aan kennisgebieden rondom het vak van business analist. Engels:Understand the business analyst's role and responsibilities in a successful project. In this introductory course, you'll delve into the role and responsibilities of the business analyst (BA)- the communication link between allbusiness areas and a critical player in project success. Learn techniques for ensuring project success every step of the way-from identifyingand analyzing potential projects to making sure that the final project product meets the requirements you identified. Through hands-onexercises, you'll learn to define the scope of work and master requirements-gathering techniques that will work for a variety of projects andaudiences. You'll consider the unique needs of customers, stakeholders, and the IT department as you work toward building, documenting,communicating, and managing requirements.

Doelgroep:

Systems analysts, business analysts, requirements analysts, developers, software engineers, IT project managers, project managers, projectanalysts, project leaders, senior project managers, team leaders, program managers, testers, and QA specialists.

Doelstelling:

What You'll Learn

Role and importance of the BA Verify and validate requirements

Vocabulary standards and business analysis practices through Elements of requirements management and communication and thethe use of the IIBA A Guide to the Business Analysis Body of BA's role in themKnowledge (BABOK Guide)

Elements of solution verification and validation and possible BAPlan BA requirements activities roles

Elicit requirements from stakeholders, with an emphasis on Enterprise analysis: choosing appropriate projectsinterviews

Necessary competencies and best practices of BAsAnalyze stated requirements, with an overview of modelingtechniques

Waterfall, incremental, and agile lifecycles and how they change BApractices

Document requirements for different types of projects

Vereiste kennis en vaardigheden:


There are no prerequisites for this course.

Vervolgcursussen:

GK2964, Business Analysis: Requirements Development, Documentation and Management


Cursusinhoud:

1. Introduction to Business Analysisline line line

Importance of Effective Business Analysis Role of the BA Role of the BAStandardization and Adaptability Standardization and AdaptabilityVision and Scope Document Vision and Scope Document

line Types of Requirements Types of RequirementsRole of the BA Stakeholders StakeholdersStandardization and Adaptability Business Analysis Plan Business Analysis PlanVision and Scope Document Iterative approach Iterative approachTypes of Requirements Techniques TechniquesStakeholders Interviews InterviewsBusiness Analysis Plan Focus groups Focus groupsIterative approach Requirements workshop: Requirements Requirements workshop: RequirementsTechniques meeting meetingInterviews Requirements workshop: JAD session Requirements workshop: JAD sessionFocus groups Brainstorming BrainstormingRequirements workshop: Requirements Observation Observationmeeting Survey SurveyRequirements workshop: JAD session Prototype PrototypeBrainstorming Document analysis Document analysisObservation Business rules analysis Business rules analysisSurvey Reverse engineering Reverse engineeringPrototype Product trials Product trialsDocument analysis Using Analysis to get Stakeholder Using Analysis to get StakeholderBusiness rules analysis Feedback and Verify and Validate Feedback and Verify and ValidateReverse engineering Developing Requirements Developing RequirementsProduct trials Value of Modeling Techniques in Value of Modeling Techniques in AnalysisUsing Analysis to get Stakeholder Feedback Analysis Modeling Techniquesand Verify and Validate Developing Modeling Techniques Organizational modelRequirements Organizational model Location modelValue of Modeling Techniques in Analysis Location model Process/flow modelsModeling Techniques Process/flow models Use case modelsOrganizational model Use case models Data modelsLocation model Data models State modelProcess/flow models State model Types of RequirementsUse case models Types of Requirements Business Rules AnalysisData models Business Rules Analysis Prioritizing RequirementsState model Prioritizing Requirements Verifying and Validating RequirementsTypes of Requirements Verifying and Validating Requirements Writing for Usability and ComprehensionBusiness Rules Analysis Writing for Usability and Comprehension Common Requirements DocumentPrioritizing Requirements Common Requirements Document DefectsVerifying and Validating Requirements Defects Components of a Formal RequirementsWriting for Usability and Comprehension Components of a Formal Requirements DocumentCommon Requirements Document Defects Document Requirements Verification and ValidationComponents of a Formal Requirements Requirements Verification and Validation Requirements Sign-OffDocument Requirements Sign-Off Change ManagementRequirements Verification and Validation Change Management Define a baselineRequirements Sign-Off Define a baseline Define a change management processChange Management Define a change management process Identify the Change AuthorityDefine a baseline Identify the Change Authority Traceability and Its UsesDefine a change management process Traceability and Its Uses Requirements AttributesIdentify the Change Authority Requirements Attributes Requirements CommunicationTraceability and Its Uses Requirements Communication Purposes of ValidationRequirements Attributes Purposes of Validation Find defectsRequirements Communication Find defects Prove compliance to requirementsPurposes of Validation Prove compliance to requirements Test Cases and Test SuitesFind defects Test Cases and Test Suites Challenges in TestingProve compliance to requirements Challenges in Testing Structured TestingTest Cases and Test Suites Structured Testing Role of the BA in Solution Validation: the VChallenges in Testing Role of the BA in Solution Validation: the ModelStructured Testing V Model Solution Acceptance and ProjectRole of the BA in Solution Validation: the V Solution Acceptance and Project Close-OutModel Close-Out Role of the BA on the Enterprise AnalysisSolution Acceptance and Project Close-Out Role of the BA on the Enterprise Analysis Team


Role of the BA on the Enterprise Analysis Team Steps in Enterprise AnalysisTeam Steps in Enterprise Analysis Define the business needSteps in Enterprise Analysis Define the business need Techniques for root cause analysisDefine the business need Techniques for root cause analysis Assess capability gapsTechniques for root cause analysis Assess capability gaps SWOT analysisAssess capability gaps SWOT analysis Determine the solution approachSWOT analysis Determine the solution approach Define the solution scopeDetermine the solution approach Define the solution scope Define the business caseDefine the solution scope Define the business case Contents of business caseDefine the business case Contents of business case Who does what?: the BA's limited role inContents of business case Who does what?: the BA's limited role in developing a business caseWho does what?: the BA's limited role in developing a business case BA Necessary Competenciesdeveloping a business case BA Necessary Competencies Analytical thinking and problem solvingBA Necessary Competencies Analytical thinking and problem solving Behavioral characteristicsAnalytical thinking and problem solving Behavioral characteristics Business knowledgeBehavioral characteristics Business knowledge Communication skillsBusiness knowledge Communication skills Interaction skillsCommunication skills Interaction skills Software application knowledgeInteraction skills Software application knowledge Best PracticesSoftware application knowledge Best Practices Use iterative analysisBest Practices Use iterative analysis Focus on process improvementUse iterative analysis Focus on process improvement Apply progressive elaborationFocus on process improvement Apply progressive elaboration Check as you goApply progressive elaboration Check as you go Use the investigative approachCheck as you go Use the investigative approach Adopt traceabilityUse the investigative approach Adopt traceability Formalize business analysis throughAdopt traceability Formalize business analysis through standardizationFormalize business analysis through standardization Improve communication through modelingstandardization Improve communication through Life Cycle ModelsImprove communication through modeling modeling WaterfallLife Cycle Models Life Cycle Models IncrementalWaterfall Waterfall AgileIncremental Incremental Effects on business analysisAgile Agile Leadership SkillsEffects on business analysis Effects on business analysis Problem-Solving SkillsLeadership Skills Leadership Skills Business KnowledgeProblem-Solving Skills Problem-Solving Skills IT KnowledgeBusiness Knowledge Business KnowledgeIT Knowledge IT Knowledge

lineRole of the BA

line line Standardization and AdaptabilityRole of the BA Role of the BA Vision and Scope DocumentStandardization and Adaptability Standardization and Adaptability Types of RequirementsVision and Scope Document Vision and Scope Document StakeholdersTypes of Requirements Types of Requirements Business Analysis PlanStakeholders Stakeholders Iterative approachBusiness Analysis Plan Business Analysis Plan TechniquesIterative approach Iterative approach InterviewsTechniques Techniques Focus groupsInterviews Interviews Requirements workshop: RequirementsFocus groups Focus groups meetingRequirements workshop: Requirements Requirements workshop: Requirements Requirements workshop: JAD sessionmeeting meeting BrainstormingRequirements workshop: JAD session Requirements workshop: JAD session ObservationBrainstorming Brainstorming SurveyObservation Observation PrototypeSurvey Survey Document analysisPrototype Prototype Business rules analysisDocument analysis Document analysis Reverse engineeringBusiness rules analysis Business rules analysis Product trialsReverse engineering Reverse engineering Using Analysis to get StakeholderProduct trials Product trials Feedback and Verify and ValidateUsing Analysis to get Stakeholder Feedback Using Analysis to get Stakeholder Developing Requirementsand Verify and Validate Developing Feedback and Verify and Validate Value of Modeling Techniques in AnalysisRequirements Developing Requirements Modeling Techniques


Value of Modeling Techniques in Analysis Value of Modeling Techniques in Organizational modelModeling Techniques Analysis Location modelOrganizational model Modeling Techniques Process/flow modelsLocation model Organizational model Use case modelsProcess/flow models Location model Data modelsUse case models Process/flow models State modelData models Use case models Types of RequirementsState model Data models Business Rules AnalysisTypes of Requirements State model Prioritizing RequirementsBusiness Rules Analysis Types of Requirements Verifying and Validating RequirementsPrioritizing Requirements Business Rules Analysis Writing for Usability and ComprehensionVerifying and Validating Requirements Prioritizing Requirements Common Requirements DocumentWriting for Usability and Comprehension Verifying and Validating Requirements DefectsCommon Requirements Document Defects Writing for Usability and Comprehension Components of a Formal RequirementsComponents of a Formal Requirements Common Requirements Document DocumentDocument Defects Requirements Verification and ValidationRequirements Verification and Validation Components of a Formal Requirements Requirements Sign-OffRequirements Sign-Off Document Change ManagementChange Management Requirements Verification and Validation Define a baselineDefine a baseline Requirements Sign-Off Define a change management processDefine a change management process Change Management Identify the Change AuthorityIdentify the Change Authority Define a baseline Traceability and Its UsesTraceability and Its Uses Define a change management process Requirements AttributesRequirements Attributes Identify the Change Authority Requirements CommunicationRequirements Communication Traceability and Its Uses Purposes of ValidationPurposes of Validation Requirements Attributes Find defectsFind defects Requirements Communication Prove compliance to requirementsProve compliance to requirements Purposes of Validation Test Cases and Test SuitesTest Cases and Test Suites Find defects Challenges in TestingChallenges in Testing Prove compliance to requirements Structured TestingStructured Testing Test Cases and Test Suites Role of the BA in Solution Validation: the VRole of the BA in Solution Validation: the V Challenges in Testing ModelModel Structured Testing Solution Acceptance and ProjectSolution Acceptance and Project Close-Out Role of the BA in Solution Validation: the Close-OutRole of the BA on the Enterprise Analysis V Model Role of the BA on the Enterprise AnalysisTeam Solution Acceptance and Project TeamSteps in Enterprise Analysis Close-Out Steps in Enterprise AnalysisDefine the business need Role of the BA on the Enterprise Analysis Define the business needTechniques for root cause analysis Team Techniques for root cause analysisAssess capability gaps Steps in Enterprise Analysis Assess capability gapsSWOT analysis Define the business need SWOT analysisDetermine the solution approach Techniques for root cause analysis Determine the solution approachDefine the solution scope Assess capability gaps Define the solution scopeDefine the business case SWOT analysis Define the business caseContents of business case Determine the solution approach Contents of business caseWho does what?: the BA's limited role in Define the solution scope Who does what?: the BA's limited role indeveloping a business case Define the business case developing a business caseBA Necessary Competencies Contents of business case BA Necessary CompetenciesAnalytical thinking and problem solving Who does what?: the BA's limited role in Analytical thinking and problem solvingBehavioral characteristics developing a business case Behavioral characteristicsBusiness knowledge BA Necessary Competencies Business knowledgeCommunication skills Analytical thinking and problem solving Communication skillsInteraction skills Behavioral characteristics Interaction skillsSoftware application knowledge Business knowledge Software application knowledgeBest Practices Communication skills Best PracticesUse iterative analysis Interaction skills Use iterative analysisFocus on process improvement Software application knowledge Focus on process improvementApply progressive elaboration Best Practices Apply progressive elaborationCheck as you go Use iterative analysis Check as you goUse the investigative approach Focus on process improvement Use the investigative approachAdopt traceability Apply progressive elaboration Adopt traceabilityFormalize business analysis through Check as you go Formalize business analysis throughstandardization Use the investigative approach standardizationImprove communication through modeling Adopt traceability Improve communication through modelingLife Cycle Models Formalize business analysis through Life Cycle ModelsWaterfall standardization Waterfall


Incremental Improve communication through IncrementalAgile modeling AgileEffects on business analysis Life Cycle Models Effects on business analysisLeadership Skills Waterfall Leadership SkillsProblem-Solving Skills Incremental Problem-Solving SkillsBusiness Knowledge Agile Business KnowledgeIT Knowledge Effects on business analysis IT Knowledge

Leadership Skills2. Requirements Planning Problem-Solving Skillsline Business Knowledge line

Role of the BA in Requirements Planning IT Knowledge Role of the BAStandardization and AdaptabilityVision and Scope Document

line line Types of RequirementsRole of the BA Role of the BA StakeholdersStandardization and Adaptability Standardization and Adaptability Business Analysis PlanVision and Scope Document Vision and Scope Document Iterative approachTypes of Requirements Types of Requirements TechniquesStakeholders Stakeholders InterviewsBusiness Analysis Plan Business Analysis Plan Focus groupsIterative approach Iterative approach Requirements workshop: RequirementsTechniques Techniques meetingInterviews Interviews Requirements workshop: JAD sessionFocus groups Focus groups BrainstormingRequirements workshop: Requirements Requirements workshop: Requirements Observationmeeting meeting SurveyRequirements workshop: JAD session Requirements workshop: JAD session PrototypeBrainstorming Brainstorming Document analysisObservation Observation Business rules analysisSurvey Survey Reverse engineeringPrototype Prototype Product trialsDocument analysis Document analysis Using Analysis to get StakeholderBusiness rules analysis Business rules analysis Feedback and Verify and ValidateReverse engineering Reverse engineering Developing RequirementsProduct trials Product trials Value of Modeling Techniques in AnalysisUsing Analysis to get Stakeholder Feedback Using Analysis to get Stakeholder Modeling Techniquesand Verify and Validate Developing Feedback and Verify and Validate Organizational modelRequirements Developing Requirements Location modelValue of Modeling Techniques in Analysis Value of Modeling Techniques in Process/flow modelsModeling Techniques Analysis Use case modelsOrganizational model Modeling Techniques Data modelsLocation model Organizational model State modelProcess/flow models Location model Types of RequirementsUse case models Process/flow models Business Rules AnalysisData models Use case models Prioritizing RequirementsState model Data models Verifying and Validating RequirementsTypes of Requirements State model Writing for Usability and ComprehensionBusiness Rules Analysis Types of Requirements Common Requirements DocumentPrioritizing Requirements Business Rules Analysis DefectsVerifying and Validating Requirements Prioritizing Requirements Components of a Formal RequirementsWriting for Usability and Comprehension Verifying and Validating Requirements DocumentCommon Requirements Document Defects Writing for Usability and Comprehension Requirements Verification and ValidationComponents of a Formal Requirements Common Requirements Document Requirements Sign-OffDocument Defects Change ManagementRequirements Verification and Validation Components of a Formal Requirements Define a baselineRequirements Sign-Off Document Define a change management processChange Management Requirements Verification and Validation Identify the Change AuthorityDefine a baseline Requirements Sign-Off Traceability and Its UsesDefine a change management process Change Management Requirements AttributesIdentify the Change Authority Define a baseline Requirements CommunicationTraceability and Its Uses Define a change management process Purposes of ValidationRequirements Attributes Identify the Change Authority Find defectsRequirements Communication Traceability and Its Uses Prove compliance to requirementsPurposes of Validation Requirements Attributes Test Cases and Test SuitesFind defects Requirements Communication Challenges in TestingProve compliance to requirements Purposes of Validation Structured Testing


Test Cases and Test Suites Find defects Role of the BA in Solution Validation: the VChallenges in Testing Prove compliance to requirements ModelStructured Testing Test Cases and Test Suites Solution Acceptance and ProjectRole of the BA in Solution Validation: the V Challenges in Testing Close-OutModel Structured Testing Role of the BA on the Enterprise AnalysisSolution Acceptance and Project Close-Out Role of the BA in Solution Validation: the TeamRole of the BA on the Enterprise Analysis V Model Steps in Enterprise AnalysisTeam Solution Acceptance and Project Define the business needSteps in Enterprise Analysis Close-Out Techniques for root cause analysisDefine the business need Role of the BA on the Enterprise Analysis Assess capability gapsTechniques for root cause analysis Team SWOT analysisAssess capability gaps Steps in Enterprise Analysis Determine the solution approachSWOT analysis Define the business need Define the solution scopeDetermine the solution approach Techniques for root cause analysis Define the business caseDefine the solution scope Assess capability gaps Contents of business caseDefine the business case SWOT analysis Who does what?: the BA's limited role inContents of business case Determine the solution approach developing a business caseWho does what?: the BA's limited role in Define the solution scope BA Necessary Competenciesdeveloping a business case Define the business case Analytical thinking and problem solvingBA Necessary Competencies Contents of business case Behavioral characteristicsAnalytical thinking and problem solving Who does what?: the BA's limited role in Business knowledgeBehavioral characteristics developing a business case Communication skillsBusiness knowledge BA Necessary Competencies Interaction skillsCommunication skills Analytical thinking and problem solving Software application knowledgeInteraction skills Behavioral characteristics Best PracticesSoftware application knowledge Business knowledge Use iterative analysisBest Practices Communication skills Focus on process improvementUse iterative analysis Interaction skills Apply progressive elaborationFocus on process improvement Software application knowledge Check as you goApply progressive elaboration Best Practices Use the investigative approachCheck as you go Use iterative analysis Adopt traceabilityUse the investigative approach Focus on process improvement Formalize business analysis throughAdopt traceability Apply progressive elaboration standardizationFormalize business analysis through Check as you go Improve communication through modelingstandardization Use the investigative approach Life Cycle ModelsImprove communication through modeling Adopt traceability WaterfallLife Cycle Models Formalize business analysis through IncrementalWaterfall standardization AgileIncremental Improve communication through Effects on business analysisAgile modeling Leadership SkillsEffects on business analysis Life Cycle Models Problem-Solving SkillsLeadership Skills Waterfall Business KnowledgeProblem-Solving Skills Incremental IT KnowledgeBusiness Knowledge AgileIT Knowledge Effects on business analysis

Leadership Skills lineProblem-Solving Skills Role of the BA

line Business Knowledge Standardization and AdaptabilityRole of the BA IT Knowledge Vision and Scope DocumentStandardization and Adaptability Types of RequirementsVision and Scope Document StakeholdersTypes of Requirements line Business Analysis PlanStakeholders Role of the BA Iterative approachBusiness Analysis Plan Standardization and Adaptability TechniquesIterative approach Vision and Scope Document InterviewsTechniques Types of Requirements Focus groupsInterviews Stakeholders Requirements workshop: RequirementsFocus groups Business Analysis Plan meetingRequirements workshop: Requirements Iterative approach Requirements workshop: JAD sessionmeeting Techniques BrainstormingRequirements workshop: JAD session Interviews ObservationBrainstorming Focus groups SurveyObservation Requirements workshop: Requirements PrototypeSurvey meeting Document analysisPrototype Requirements workshop: JAD session Business rules analysisDocument analysis Brainstorming Reverse engineering


Business rules analysis Observation Product trialsReverse engineering Survey Using Analysis to get StakeholderProduct trials Prototype Feedback and Verify and ValidateUsing Analysis to get Stakeholder Feedback Document analysis Developing Requirementsand Verify and Validate Developing Business rules analysis Value of Modeling Techniques in AnalysisRequirements Reverse engineering Modeling TechniquesValue of Modeling Techniques in Analysis Product trials Organizational modelModeling Techniques Using Analysis to get Stakeholder Location modelOrganizational model Feedback and Verify and Validate Process/flow modelsLocation model Developing Requirements Use case modelsProcess/flow models Value of Modeling Techniques in Data modelsUse case models Analysis State modelData models Modeling Techniques Types of RequirementsState model Organizational model Business Rules AnalysisTypes of Requirements Location model Prioritizing RequirementsBusiness Rules Analysis Process/flow models Verifying and Validating RequirementsPrioritizing Requirements Use case models Writing for Usability and ComprehensionVerifying and Validating Requirements Data models Common Requirements DocumentWriting for Usability and Comprehension State model DefectsCommon Requirements Document Defects Types of Requirements Components of a Formal RequirementsComponents of a Formal Requirements Business Rules Analysis DocumentDocument Prioritizing Requirements Requirements Verification and ValidationRequirements Verification and Validation Verifying and Validating Requirements Requirements Sign-OffRequirements Sign-Off Writing for Usability and Comprehension Change ManagementChange Management Common Requirements Document Define a baselineDefine a baseline Defects Define a change management processDefine a change management process Components of a Formal Requirements Identify the Change AuthorityIdentify the Change Authority Document Traceability and Its UsesTraceability and Its Uses Requirements Verification and Validation Requirements AttributesRequirements Attributes Requirements Sign-Off Requirements CommunicationRequirements Communication Change Management Purposes of ValidationPurposes of Validation Define a baseline Find defectsFind defects Define a change management process Prove compliance to requirementsProve compliance to requirements Identify the Change Authority Test Cases and Test SuitesTest Cases and Test Suites Traceability and Its Uses Challenges in TestingChallenges in Testing Requirements Attributes Structured TestingStructured Testing Requirements Communication Role of the BA in Solution Validation: the VRole of the BA in Solution Validation: the V Purposes of Validation ModelModel Find defects Solution Acceptance and ProjectSolution Acceptance and Project Close-Out Prove compliance to requirements Close-OutRole of the BA on the Enterprise Analysis Test Cases and Test Suites Role of the BA on the Enterprise AnalysisTeam Challenges in Testing TeamSteps in Enterprise Analysis Structured Testing Steps in Enterprise AnalysisDefine the business need Role of the BA in Solution Validation: the Define the business needTechniques for root cause analysis V Model Techniques for root cause analysisAssess capability gaps Solution Acceptance and Project Assess capability gapsSWOT analysis Close-Out SWOT analysisDetermine the solution approach Role of the BA on the Enterprise Analysis Determine the solution approachDefine the solution scope Team Define the solution scopeDefine the business case Steps in Enterprise Analysis Define the business caseContents of business case Define the business need Contents of business caseWho does what?: the BA's limited role in Techniques for root cause analysis Who does what?: the BA's limited role indeveloping a business case Assess capability gaps developing a business caseBA Necessary Competencies SWOT analysis BA Necessary CompetenciesAnalytical thinking and problem solving Determine the solution approach Analytical thinking and problem solvingBehavioral characteristics Define the solution scope Behavioral characteristicsBusiness knowledge Define the business case Business knowledgeCommunication skills Contents of business case Communication skillsInteraction skills Who does what?: the BA's limited role in Interaction skillsSoftware application knowledge developing a business case Software application knowledgeBest Practices BA Necessary Competencies Best PracticesUse iterative analysis Analytical thinking and problem solving Use iterative analysisFocus on process improvement Behavioral characteristics Focus on process improvementApply progressive elaboration Business knowledge Apply progressive elaborationCheck as you go Communication skills Check as you goUse the investigative approach Interaction skills Use the investigative approach


Adopt traceability Software application knowledge Adopt traceabilityFormalize business analysis through Best Practices Formalize business analysis throughstandardization Use iterative analysis standardizationImprove communication through modeling Focus on process improvement Improve communication through modelingLife Cycle Models Apply progressive elaboration Life Cycle ModelsWaterfall Check as you go WaterfallIncremental Use the investigative approach IncrementalAgile Adopt traceability AgileEffects on business analysis Formalize business analysis through Effects on business analysisLeadership Skills standardization Leadership SkillsProblem-Solving Skills Improve communication through Problem-Solving SkillsBusiness Knowledge modeling Business KnowledgeIT Knowledge Life Cycle Models IT Knowledge

WaterfallIncremental 9. Competencies, Best Practices, and Life

line Agile Cycle ModelsRole of the BA Effects on business analysis lineStandardization and Adaptability Leadership Skills Competency ProficiencyVision and Scope Document Problem-Solving SkillsTypes of Requirements Business KnowledgeStakeholders IT Knowledge lineBusiness Analysis Plan Role of the BAIterative approach Standardization and AdaptabilityTechniques line Vision and Scope DocumentInterviews Role of the BA Types of RequirementsFocus groups Standardization and Adaptability StakeholdersRequirements workshop: Requirements Vision and Scope Document Business Analysis Planmeeting Types of Requirements Iterative approachRequirements workshop: JAD session Stakeholders TechniquesBrainstorming Business Analysis Plan InterviewsObservation Iterative approach Focus groupsSurvey Techniques Requirements workshop: RequirementsPrototype Interviews meetingDocument analysis Focus groups Requirements workshop: JAD sessionBusiness rules analysis Requirements workshop: Requirements BrainstormingReverse engineering meeting ObservationProduct trials Requirements workshop: JAD session SurveyUsing Analysis to get Stakeholder Feedback Brainstorming Prototypeand Verify and Validate Developing Observation Document analysisRequirements Survey Business rules analysisValue of Modeling Techniques in Analysis Prototype Reverse engineeringModeling Techniques Document analysis Product trialsOrganizational model Business rules analysis Using Analysis to get StakeholderLocation model Reverse engineering Feedback and Verify and ValidateProcess/flow models Product trials Developing RequirementsUse case models Using Analysis to get Stakeholder Value of Modeling Techniques in AnalysisData models Feedback and Verify and Validate Modeling TechniquesState model Developing Requirements Organizational modelTypes of Requirements Value of Modeling Techniques in Location modelBusiness Rules Analysis Analysis Process/flow modelsPrioritizing Requirements Modeling Techniques Use case modelsVerifying and Validating Requirements Organizational model Data modelsWriting for Usability and Comprehension Location model State modelCommon Requirements Document Defects Process/flow models Types of RequirementsComponents of a Formal Requirements Use case models Business Rules AnalysisDocument Data models Prioritizing RequirementsRequirements Verification and Validation State model Verifying and Validating RequirementsRequirements Sign-Off Types of Requirements Writing for Usability and ComprehensionChange Management Business Rules Analysis Common Requirements DocumentDefine a baseline Prioritizing Requirements DefectsDefine a change management process Verifying and Validating Requirements Components of a Formal RequirementsIdentify the Change Authority Writing for Usability and Comprehension DocumentTraceability and Its Uses Common Requirements Document Requirements Verification and ValidationRequirements Attributes Defects Requirements Sign-OffRequirements Communication Components of a Formal Requirements Change ManagementPurposes of Validation Document Define a baseline


Find defects Requirements Verification and Validation Define a change management processProve compliance to requirements Requirements Sign-Off Identify the Change AuthorityTest Cases and Test Suites Change Management Traceability and Its UsesChallenges in Testing Define a baseline Requirements AttributesStructured Testing Define a change management process Requirements CommunicationRole of the BA in Solution Validation: the V Identify the Change Authority Purposes of ValidationModel Traceability and Its Uses Find defectsSolution Acceptance and Project Close-Out Requirements Attributes Prove compliance to requirementsRole of the BA on the Enterprise Analysis Requirements Communication Test Cases and Test SuitesTeam Purposes of Validation Challenges in TestingSteps in Enterprise Analysis Find defects Structured TestingDefine the business need Prove compliance to requirements Role of the BA in Solution Validation: the VTechniques for root cause analysis Test Cases and Test Suites ModelAssess capability gaps Challenges in Testing Solution Acceptance and ProjectSWOT analysis Structured Testing Close-OutDetermine the solution approach Role of the BA in Solution Validation: the Role of the BA on the Enterprise AnalysisDefine the solution scope V Model TeamDefine the business case Solution Acceptance and Project Steps in Enterprise AnalysisContents of business case Close-Out Define the business needWho does what?: the BA's limited role in Role of the BA on the Enterprise Analysis Techniques for root cause analysisdeveloping a business case Team Assess capability gapsBA Necessary Competencies Steps in Enterprise Analysis SWOT analysisAnalytical thinking and problem solving Define the business need Determine the solution approachBehavioral characteristics Techniques for root cause analysis Define the solution scopeBusiness knowledge Assess capability gaps Define the business caseCommunication skills SWOT analysis Contents of business caseInteraction skills Determine the solution approach Who does what?: the BA's limited role inSoftware application knowledge Define the solution scope developing a business caseBest Practices Define the business case BA Necessary CompetenciesUse iterative analysis Contents of business case Analytical thinking and problem solvingFocus on process improvement Who does what?: the BA's limited role in Behavioral characteristicsApply progressive elaboration developing a business case Business knowledgeCheck as you go BA Necessary Competencies Communication skillsUse the investigative approach Analytical thinking and problem solving Interaction skillsAdopt traceability Behavioral characteristics Software application knowledgeFormalize business analysis through Business knowledge Best Practicesstandardization Communication skills Use iterative analysisImprove communication through modeling Interaction skills Focus on process improvementLife Cycle Models Software application knowledge Apply progressive elaborationWaterfall Best Practices Check as you goIncremental Use iterative analysis Use the investigative approachAgile Focus on process improvement Adopt traceabilityEffects on business analysis Apply progressive elaboration Formalize business analysis throughLeadership Skills Check as you go standardizationProblem-Solving Skills Use the investigative approach Improve communication through modelingBusiness Knowledge Adopt traceability Life Cycle ModelsIT Knowledge Formalize business analysis through Waterfall

standardization IncrementalImprove communication through Agile

line modeling Effects on business analysisRole of the BA Life Cycle Models Leadership SkillsStandardization and Adaptability Waterfall Problem-Solving SkillsVision and Scope Document Incremental Business KnowledgeTypes of Requirements Agile IT KnowledgeStakeholders Effects on business analysisBusiness Analysis Plan Leadership SkillsIterative approach Problem-Solving Skills lineTechniques Business Knowledge Role of the BAInterviews IT Knowledge Standardization and AdaptabilityFocus groups Vision and Scope DocumentRequirements workshop: Requirements 5. Requirements Documentation Types of Requirementsmeeting line StakeholdersRequirements workshop: JAD session Formal and Informal Documentation and Business Analysis PlanBrainstorming the, Level of Detail Required Iterative approachObservation TechniquesSurvey Interviews


Prototype line Focus groupsDocument analysis Role of the BA Requirements workshop: RequirementsBusiness rules analysis Standardization and Adaptability meetingReverse engineering Vision and Scope Document Requirements workshop: JAD sessionProduct trials Types of Requirements BrainstormingUsing Analysis to get Stakeholder Feedback Stakeholders Observationand Verify and Validate Developing Business Analysis Plan SurveyRequirements Iterative approach PrototypeValue of Modeling Techniques in Analysis Techniques Document analysisModeling Techniques Interviews Business rules analysisOrganizational model Focus groups Reverse engineeringLocation model Requirements workshop: Requirements Product trialsProcess/flow models meeting Using Analysis to get StakeholderUse case models Requirements workshop: JAD session Feedback and Verify and ValidateData models Brainstorming Developing RequirementsState model Observation Value of Modeling Techniques in AnalysisTypes of Requirements Survey Modeling TechniquesBusiness Rules Analysis Prototype Organizational modelPrioritizing Requirements Document analysis Location modelVerifying and Validating Requirements Business rules analysis Process/flow modelsWriting for Usability and Comprehension Reverse engineering Use case modelsCommon Requirements Document Defects Product trials Data modelsComponents of a Formal Requirements Using Analysis to get Stakeholder State modelDocument Feedback and Verify and Validate Types of RequirementsRequirements Verification and Validation Developing Requirements Business Rules AnalysisRequirements Sign-Off Value of Modeling Techniques in Prioritizing RequirementsChange Management Analysis Verifying and Validating RequirementsDefine a baseline Modeling Techniques Writing for Usability and ComprehensionDefine a change management process Organizational model Common Requirements DocumentIdentify the Change Authority Location model DefectsTraceability and Its Uses Process/flow models Components of a Formal RequirementsRequirements Attributes Use case models DocumentRequirements Communication Data models Requirements Verification and ValidationPurposes of Validation State model Requirements Sign-OffFind defects Types of Requirements Change ManagementProve compliance to requirements Business Rules Analysis Define a baselineTest Cases and Test Suites Prioritizing Requirements Define a change management processChallenges in Testing Verifying and Validating Requirements Identify the Change AuthorityStructured Testing Writing for Usability and Comprehension Traceability and Its UsesRole of the BA in Solution Validation: the V Common Requirements Document Requirements AttributesModel Defects Requirements CommunicationSolution Acceptance and Project Close-Out Components of a Formal Requirements Purposes of ValidationRole of the BA on the Enterprise Analysis Document Find defectsTeam Requirements Verification and Validation Prove compliance to requirementsSteps in Enterprise Analysis Requirements Sign-Off Test Cases and Test SuitesDefine the business need Change Management Challenges in TestingTechniques for root cause analysis Define a baseline Structured TestingAssess capability gaps Define a change management process Role of the BA in Solution Validation: the VSWOT analysis Identify the Change Authority ModelDetermine the solution approach Traceability and Its Uses Solution Acceptance and ProjectDefine the solution scope Requirements Attributes Close-OutDefine the business case Requirements Communication Role of the BA on the Enterprise AnalysisContents of business case Purposes of Validation TeamWho does what?: the BA's limited role in Find defects Steps in Enterprise Analysisdeveloping a business case Prove compliance to requirements Define the business needBA Necessary Competencies Test Cases and Test Suites Techniques for root cause analysisAnalytical thinking and problem solving Challenges in Testing Assess capability gapsBehavioral characteristics Structured Testing SWOT analysisBusiness knowledge Role of the BA in Solution Validation: the Determine the solution approachCommunication skills V Model Define the solution scopeInteraction skills Solution Acceptance and Project Define the business caseSoftware application knowledge Close-Out Contents of business caseBest Practices Role of the BA on the Enterprise Analysis Who does what?: the BA's limited role inUse iterative analysis Team developing a business caseFocus on process improvement Steps in Enterprise Analysis BA Necessary CompetenciesApply progressive elaboration Define the business need Analytical thinking and problem solving


Check as you go Techniques for root cause analysis Behavioral characteristicsUse the investigative approach Assess capability gaps Business knowledgeAdopt traceability SWOT analysis Communication skillsFormalize business analysis through Determine the solution approach Interaction skillsstandardization Define the solution scope Software application knowledgeImprove communication through modeling Define the business case Best PracticesLife Cycle Models Contents of business case Use iterative analysisWaterfall Who does what?: the BA's limited role in Focus on process improvementIncremental developing a business case Apply progressive elaborationAgile BA Necessary Competencies Check as you goEffects on business analysis Analytical thinking and problem solving Use the investigative approachLeadership Skills Behavioral characteristics Adopt traceabilityProblem-Solving Skills Business knowledge Formalize business analysis throughBusiness Knowledge Communication skills standardizationIT Knowledge Interaction skills Improve communication through modeling

Software application knowledge Life Cycle Models3. Requirements Elicitation Best Practices Waterfallline Use iterative analysis Incremental

Role of the BA in Requirements Elicitation Focus on process improvement AgileInvestigative approach Apply progressive elaboration Effects on business analysis

Check as you go Leadership SkillsUse the investigative approach Problem-Solving Skills

line Adopt traceability Business KnowledgeRole of the BA Formalize business analysis through IT KnowledgeStandardization and Adaptability standardizationVision and Scope Document Improve communication throughTypes of Requirements modeling lineStakeholders Life Cycle Models Role of the BABusiness Analysis Plan Waterfall Standardization and AdaptabilityIterative approach Incremental Vision and Scope DocumentTechniques Agile Types of RequirementsInterviews Effects on business analysis StakeholdersFocus groups Leadership Skills Business Analysis PlanRequirements workshop: Requirements Problem-Solving Skills Iterative approachmeeting Business Knowledge TechniquesRequirements workshop: JAD session IT Knowledge InterviewsBrainstorming Focus groupsObservation Requirements workshop: RequirementsSurvey line meetingPrototype Role of the BA Requirements workshop: JAD sessionDocument analysis Standardization and Adaptability BrainstormingBusiness rules analysis Vision and Scope Document ObservationReverse engineering Types of Requirements SurveyProduct trials Stakeholders PrototypeUsing Analysis to get Stakeholder Feedback Business Analysis Plan Document analysisand Verify and Validate Developing Iterative approach Business rules analysisRequirements Techniques Reverse engineeringValue of Modeling Techniques in Analysis Interviews Product trialsModeling Techniques Focus groups Using Analysis to get StakeholderOrganizational model Requirements workshop: Requirements Feedback and Verify and ValidateLocation model meeting Developing RequirementsProcess/flow models Requirements workshop: JAD session Value of Modeling Techniques in AnalysisUse case models Brainstorming Modeling TechniquesData models Observation Organizational modelState model Survey Location modelTypes of Requirements Prototype Process/flow modelsBusiness Rules Analysis Document analysis Use case modelsPrioritizing Requirements Business rules analysis Data modelsVerifying and Validating Requirements Reverse engineering State modelWriting for Usability and Comprehension Product trials Types of RequirementsCommon Requirements Document Defects Using Analysis to get Stakeholder Business Rules AnalysisComponents of a Formal Requirements Feedback and Verify and Validate Prioritizing RequirementsDocument Developing Requirements Verifying and Validating RequirementsRequirements Verification and Validation Value of Modeling Techniques in Writing for Usability and ComprehensionRequirements Sign-Off Analysis Common Requirements DocumentChange Management Modeling Techniques Defects


Define a baseline Organizational model Components of a Formal RequirementsDefine a change management process Location model DocumentIdentify the Change Authority Process/flow models Requirements Verification and ValidationTraceability and Its Uses Use case models Requirements Sign-OffRequirements Attributes Data models Change ManagementRequirements Communication State model Define a baselinePurposes of Validation Types of Requirements Define a change management processFind defects Business Rules Analysis Identify the Change AuthorityProve compliance to requirements Prioritizing Requirements Traceability and Its UsesTest Cases and Test Suites Verifying and Validating Requirements Requirements AttributesChallenges in Testing Writing for Usability and Comprehension Requirements CommunicationStructured Testing Common Requirements Document Purposes of ValidationRole of the BA in Solution Validation: the V Defects Find defectsModel Components of a Formal Requirements Prove compliance to requirementsSolution Acceptance and Project Close-Out Document Test Cases and Test SuitesRole of the BA on the Enterprise Analysis Requirements Verification and Validation Challenges in TestingTeam Requirements Sign-Off Structured TestingSteps in Enterprise Analysis Change Management Role of the BA in Solution Validation: the VDefine the business need Define a baseline ModelTechniques for root cause analysis Define a change management process Solution Acceptance and ProjectAssess capability gaps Identify the Change Authority Close-OutSWOT analysis Traceability and Its Uses Role of the BA on the Enterprise AnalysisDetermine the solution approach Requirements Attributes TeamDefine the solution scope Requirements Communication Steps in Enterprise AnalysisDefine the business case Purposes of Validation Define the business needContents of business case Find defects Techniques for root cause analysisWho does what?: the BA's limited role in Prove compliance to requirements Assess capability gapsdeveloping a business case Test Cases and Test Suites SWOT analysisBA Necessary Competencies Challenges in Testing Determine the solution approachAnalytical thinking and problem solving Structured Testing Define the solution scopeBehavioral characteristics Role of the BA in Solution Validation: the Define the business caseBusiness knowledge V Model Contents of business caseCommunication skills Solution Acceptance and Project Who does what?: the BA's limited role inInteraction skills Close-Out developing a business caseSoftware application knowledge Role of the BA on the Enterprise Analysis BA Necessary CompetenciesBest Practices Team Analytical thinking and problem solvingUse iterative analysis Steps in Enterprise Analysis Behavioral characteristicsFocus on process improvement Define the business need Business knowledgeApply progressive elaboration Techniques for root cause analysis Communication skillsCheck as you go Assess capability gaps Interaction skillsUse the investigative approach SWOT analysis Software application knowledgeAdopt traceability Determine the solution approach Best PracticesFormalize business analysis through Define the solution scope Use iterative analysisstandardization Define the business case Focus on process improvementImprove communication through modeling Contents of business case Apply progressive elaborationLife Cycle Models Who does what?: the BA's limited role in Check as you goWaterfall developing a business case Use the investigative approachIncremental BA Necessary Competencies Adopt traceabilityAgile Analytical thinking and problem solving Formalize business analysis throughEffects on business analysis Behavioral characteristics standardizationLeadership Skills Business knowledge Improve communication through modelingProblem-Solving Skills Communication skills Life Cycle ModelsBusiness Knowledge Interaction skills WaterfallIT Knowledge Software application knowledge Incremental

Best Practices AgileUse iterative analysis Effects on business analysis

line Focus on process improvement Leadership SkillsRole of the BA Apply progressive elaboration Problem-Solving SkillsStandardization and Adaptability Check as you go Business KnowledgeVision and Scope Document Use the investigative approach IT KnowledgeTypes of Requirements Adopt traceabilityStakeholders Formalize business analysis throughBusiness Analysis Plan standardization lineIterative approach Improve communication through Role of the BATechniques modeling Standardization and AdaptabilityInterviews Life Cycle Models Vision and Scope Document


Focus groups Waterfall Types of RequirementsRequirements workshop: Requirements Incremental Stakeholdersmeeting Agile Business Analysis PlanRequirements workshop: JAD session Effects on business analysis Iterative approachBrainstorming Leadership Skills TechniquesObservation Problem-Solving Skills InterviewsSurvey Business Knowledge Focus groupsPrototype IT Knowledge Requirements workshop: RequirementsDocument analysis meetingBusiness rules analysis Requirements workshop: JAD sessionReverse engineering line BrainstormingProduct trials Role of the BA ObservationUsing Analysis to get Stakeholder Feedback Standardization and Adaptability Surveyand Verify and Validate Developing Vision and Scope Document PrototypeRequirements Types of Requirements Document analysisValue of Modeling Techniques in Analysis Stakeholders Business rules analysisModeling Techniques Business Analysis Plan Reverse engineeringOrganizational model Iterative approach Product trialsLocation model Techniques Using Analysis to get StakeholderProcess/flow models Interviews Feedback and Verify and ValidateUse case models Focus groups Developing RequirementsData models Requirements workshop: Requirements Value of Modeling Techniques in AnalysisState model meeting Modeling TechniquesTypes of Requirements Requirements workshop: JAD session Organizational modelBusiness Rules Analysis Brainstorming Location modelPrioritizing Requirements Observation Process/flow modelsVerifying and Validating Requirements Survey Use case modelsWriting for Usability and Comprehension Prototype Data modelsCommon Requirements Document Defects Document analysis State modelComponents of a Formal Requirements Business rules analysis Types of RequirementsDocument Reverse engineering Business Rules AnalysisRequirements Verification and Validation Product trials Prioritizing RequirementsRequirements Sign-Off Using Analysis to get Stakeholder Verifying and Validating RequirementsChange Management Feedback and Verify and Validate Writing for Usability and ComprehensionDefine a baseline Developing Requirements Common Requirements DocumentDefine a change management process Value of Modeling Techniques in DefectsIdentify the Change Authority Analysis Components of a Formal RequirementsTraceability and Its Uses Modeling Techniques DocumentRequirements Attributes Organizational model Requirements Verification and ValidationRequirements Communication Location model Requirements Sign-OffPurposes of Validation Process/flow models Change ManagementFind defects Use case models Define a baselineProve compliance to requirements Data models Define a change management processTest Cases and Test Suites State model Identify the Change AuthorityChallenges in Testing Types of Requirements Traceability and Its UsesStructured Testing Business Rules Analysis Requirements AttributesRole of the BA in Solution Validation: the V Prioritizing Requirements Requirements CommunicationModel Verifying and Validating Requirements Purposes of ValidationSolution Acceptance and Project Close-Out Writing for Usability and Comprehension Find defectsRole of the BA on the Enterprise Analysis Common Requirements Document Prove compliance to requirementsTeam Defects Test Cases and Test SuitesSteps in Enterprise Analysis Components of a Formal Requirements Challenges in TestingDefine the business need Document Structured TestingTechniques for root cause analysis Requirements Verification and Validation Role of the BA in Solution Validation: the VAssess capability gaps Requirements Sign-Off ModelSWOT analysis Change Management Solution Acceptance and ProjectDetermine the solution approach Define a baseline Close-OutDefine the solution scope Define a change management process Role of the BA on the Enterprise AnalysisDefine the business case Identify the Change Authority TeamContents of business case Traceability and Its Uses Steps in Enterprise AnalysisWho does what?: the BA's limited role in Requirements Attributes Define the business needdeveloping a business case Requirements Communication Techniques for root cause analysisBA Necessary Competencies Purposes of Validation Assess capability gapsAnalytical thinking and problem solving Find defects SWOT analysisBehavioral characteristics Prove compliance to requirements Determine the solution approachBusiness knowledge Test Cases and Test Suites Define the solution scope


Communication skills Challenges in Testing Define the business caseInteraction skills Structured Testing Contents of business caseSoftware application knowledge Role of the BA in Solution Validation: the Who does what?: the BA's limited role inBest Practices V Model developing a business caseUse iterative analysis Solution Acceptance and Project BA Necessary CompetenciesFocus on process improvement Close-Out Analytical thinking and problem solvingApply progressive elaboration Role of the BA on the Enterprise Analysis Behavioral characteristicsCheck as you go Team Business knowledgeUse the investigative approach Steps in Enterprise Analysis Communication skillsAdopt traceability Define the business need Interaction skillsFormalize business analysis through Techniques for root cause analysis Software application knowledgestandardization Assess capability gaps Best PracticesImprove communication through modeling SWOT analysis Use iterative analysisLife Cycle Models Determine the solution approach Focus on process improvementWaterfall Define the solution scope Apply progressive elaborationIncremental Define the business case Check as you goAgile Contents of business case Use the investigative approachEffects on business analysis Who does what?: the BA's limited role in Adopt traceabilityLeadership Skills developing a business case Formalize business analysis throughProblem-Solving Skills BA Necessary Competencies standardizationBusiness Knowledge Analytical thinking and problem solving Improve communication through modelingIT Knowledge Behavioral characteristics Life Cycle Models

Business knowledge WaterfallCommunication skills Incremental

line Interaction skills AgileRole of the BA Software application knowledge Effects on business analysisStandardization and Adaptability Best Practices Leadership SkillsVision and Scope Document Use iterative analysis Problem-Solving SkillsTypes of Requirements Focus on process improvement Business KnowledgeStakeholders Apply progressive elaboration IT KnowledgeBusiness Analysis Plan Check as you goIterative approach Use the investigative approachTechniques Adopt traceability lineInterviews Formalize business analysis through Role of the BAFocus groups standardization Standardization and AdaptabilityRequirements workshop: Requirements Improve communication through Vision and Scope Documentmeeting modeling Types of RequirementsRequirements workshop: JAD session Life Cycle Models StakeholdersBrainstorming Waterfall Business Analysis PlanObservation Incremental Iterative approachSurvey Agile TechniquesPrototype Effects on business analysis InterviewsDocument analysis Leadership Skills Focus groupsBusiness rules analysis Problem-Solving Skills Requirements workshop: RequirementsReverse engineering Business Knowledge meetingProduct trials IT Knowledge Requirements workshop: JAD sessionUsing Analysis to get Stakeholder Feedback Brainstormingand Verify and Validate Developing ObservationRequirements line SurveyValue of Modeling Techniques in Analysis Role of the BA PrototypeModeling Techniques Standardization and Adaptability Document analysisOrganizational model Vision and Scope Document Business rules analysisLocation model Types of Requirements Reverse engineeringProcess/flow models Stakeholders Product trialsUse case models Business Analysis Plan Using Analysis to get StakeholderData models Iterative approach Feedback and Verify and ValidateState model Techniques Developing RequirementsTypes of Requirements Interviews Value of Modeling Techniques in AnalysisBusiness Rules Analysis Focus groups Modeling TechniquesPrioritizing Requirements Requirements workshop: Requirements Organizational modelVerifying and Validating Requirements meeting Location modelWriting for Usability and Comprehension Requirements workshop: JAD session Process/flow modelsCommon Requirements Document Defects Brainstorming Use case modelsComponents of a Formal Requirements Observation Data modelsDocument Survey State modelRequirements Verification and Validation Prototype Types of Requirements


Requirements Sign-Off Document analysis Business Rules AnalysisChange Management Business rules analysis Prioritizing RequirementsDefine a baseline Reverse engineering Verifying and Validating RequirementsDefine a change management process Product trials Writing for Usability and ComprehensionIdentify the Change Authority Using Analysis to get Stakeholder Common Requirements DocumentTraceability and Its Uses Feedback and Verify and Validate DefectsRequirements Attributes Developing Requirements Components of a Formal RequirementsRequirements Communication Value of Modeling Techniques in DocumentPurposes of Validation Analysis Requirements Verification and ValidationFind defects Modeling Techniques Requirements Sign-OffProve compliance to requirements Organizational model Change ManagementTest Cases and Test Suites Location model Define a baselineChallenges in Testing Process/flow models Define a change management processStructured Testing Use case models Identify the Change AuthorityRole of the BA in Solution Validation: the V Data models Traceability and Its UsesModel State model Requirements AttributesSolution Acceptance and Project Close-Out Types of Requirements Requirements CommunicationRole of the BA on the Enterprise Analysis Business Rules Analysis Purposes of ValidationTeam Prioritizing Requirements Find defectsSteps in Enterprise Analysis Verifying and Validating Requirements Prove compliance to requirementsDefine the business need Writing for Usability and Comprehension Test Cases and Test SuitesTechniques for root cause analysis Common Requirements Document Challenges in TestingAssess capability gaps Defects Structured TestingSWOT analysis Components of a Formal Requirements Role of the BA in Solution Validation: the VDetermine the solution approach Document ModelDefine the solution scope Requirements Verification and Validation Solution Acceptance and ProjectDefine the business case Requirements Sign-Off Close-OutContents of business case Change Management Role of the BA on the Enterprise AnalysisWho does what?: the BA's limited role in Define a baseline Teamdeveloping a business case Define a change management process Steps in Enterprise AnalysisBA Necessary Competencies Identify the Change Authority Define the business needAnalytical thinking and problem solving Traceability and Its Uses Techniques for root cause analysisBehavioral characteristics Requirements Attributes Assess capability gapsBusiness knowledge Requirements Communication SWOT analysisCommunication skills Purposes of Validation Determine the solution approachInteraction skills Find defects Define the solution scopeSoftware application knowledge Prove compliance to requirements Define the business caseBest Practices Test Cases and Test Suites Contents of business caseUse iterative analysis Challenges in Testing Who does what?: the BA's limited role inFocus on process improvement Structured Testing developing a business caseApply progressive elaboration Role of the BA in Solution Validation: the BA Necessary CompetenciesCheck as you go V Model Analytical thinking and problem solvingUse the investigative approach Solution Acceptance and Project Behavioral characteristicsAdopt traceability Close-Out Business knowledgeFormalize business analysis through Role of the BA on the Enterprise Analysis Communication skillsstandardization Team Interaction skillsImprove communication through modeling Steps in Enterprise Analysis Software application knowledgeLife Cycle Models Define the business need Best PracticesWaterfall Techniques for root cause analysis Use iterative analysisIncremental Assess capability gaps Focus on process improvementAgile SWOT analysis Apply progressive elaborationEffects on business analysis Determine the solution approach Check as you goLeadership Skills Define the solution scope Use the investigative approachProblem-Solving Skills Define the business case Adopt traceabilityBusiness Knowledge Contents of business case Formalize business analysis throughIT Knowledge Who does what?: the BA's limited role in standardization

developing a business case Improve communication through modelingBA Necessary Competencies Life Cycle Models

line Analytical thinking and problem solving WaterfallRole of the BA Behavioral characteristics IncrementalStandardization and Adaptability Business knowledge AgileVision and Scope Document Communication skills Effects on business analysisTypes of Requirements Interaction skills Leadership SkillsStakeholders Software application knowledge Problem-Solving SkillsBusiness Analysis Plan Best Practices Business KnowledgeIterative approach Use iterative analysis IT Knowledge


Techniques Focus on process improvementInterviews Apply progressive elaborationFocus groups Check as you go lineRequirements workshop: Requirements Use the investigative approach Role of the BAmeeting Adopt traceability Standardization and AdaptabilityRequirements workshop: JAD session Formalize business analysis through Vision and Scope DocumentBrainstorming standardization Types of RequirementsObservation Improve communication through StakeholdersSurvey modeling Business Analysis PlanPrototype Life Cycle Models Iterative approachDocument analysis Waterfall TechniquesBusiness rules analysis Incremental InterviewsReverse engineering Agile Focus groupsProduct trials Effects on business analysis Requirements workshop: RequirementsUsing Analysis to get Stakeholder Feedback Leadership Skills meetingand Verify and Validate Developing Problem-Solving Skills Requirements workshop: JAD sessionRequirements Business Knowledge BrainstormingValue of Modeling Techniques in Analysis IT Knowledge ObservationModeling Techniques SurveyOrganizational model PrototypeLocation model line Document analysisProcess/flow models Role of the BA Business rules analysisUse case models Standardization and Adaptability Reverse engineeringData models Vision and Scope Document Product trialsState model Types of Requirements Using Analysis to get StakeholderTypes of Requirements Stakeholders Feedback and Verify and ValidateBusiness Rules Analysis Business Analysis Plan Developing RequirementsPrioritizing Requirements Iterative approach Value of Modeling Techniques in AnalysisVerifying and Validating Requirements Techniques Modeling TechniquesWriting for Usability and Comprehension Interviews Organizational modelCommon Requirements Document Defects Focus groups Location modelComponents of a Formal Requirements Requirements workshop: Requirements Process/flow modelsDocument meeting Use case modelsRequirements Verification and Validation Requirements workshop: JAD session Data modelsRequirements Sign-Off Brainstorming State modelChange Management Observation Types of RequirementsDefine a baseline Survey Business Rules AnalysisDefine a change management process Prototype Prioritizing RequirementsIdentify the Change Authority Document analysis Verifying and Validating RequirementsTraceability and Its Uses Business rules analysis Writing for Usability and ComprehensionRequirements Attributes Reverse engineering Common Requirements DocumentRequirements Communication Product trials DefectsPurposes of Validation Using Analysis to get Stakeholder Components of a Formal RequirementsFind defects Feedback and Verify and Validate DocumentProve compliance to requirements Developing Requirements Requirements Verification and ValidationTest Cases and Test Suites Value of Modeling Techniques in Requirements Sign-OffChallenges in Testing Analysis Change ManagementStructured Testing Modeling Techniques Define a baselineRole of the BA in Solution Validation: the V Organizational model Define a change management processModel Location model Identify the Change AuthoritySolution Acceptance and Project Close-Out Process/flow models Traceability and Its UsesRole of the BA on the Enterprise Analysis Use case models Requirements AttributesTeam Data models Requirements CommunicationSteps in Enterprise Analysis State model Purposes of ValidationDefine the business need Types of Requirements Find defectsTechniques for root cause analysis Business Rules Analysis Prove compliance to requirementsAssess capability gaps Prioritizing Requirements Test Cases and Test SuitesSWOT analysis Verifying and Validating Requirements Challenges in TestingDetermine the solution approach Writing for Usability and Comprehension Structured TestingDefine the solution scope Common Requirements Document Role of the BA in Solution Validation: the VDefine the business case Defects ModelContents of business case Components of a Formal Requirements Solution Acceptance and ProjectWho does what?: the BA's limited role in Document Close-Outdeveloping a business case Requirements Verification and Validation Role of the BA on the Enterprise AnalysisBA Necessary Competencies Requirements Sign-Off TeamAnalytical thinking and problem solving Change Management Steps in Enterprise Analysis


Behavioral characteristics Define a baseline Define the business needBusiness knowledge Define a change management process Techniques for root cause analysisCommunication skills Identify the Change Authority Assess capability gapsInteraction skills Traceability and Its Uses SWOT analysisSoftware application knowledge Requirements Attributes Determine the solution approachBest Practices Requirements Communication Define the solution scopeUse iterative analysis Purposes of Validation Define the business caseFocus on process improvement Find defects Contents of business caseApply progressive elaboration Prove compliance to requirements Who does what?: the BA's limited role inCheck as you go Test Cases and Test Suites developing a business caseUse the investigative approach Challenges in Testing BA Necessary CompetenciesAdopt traceability Structured Testing Analytical thinking and problem solvingFormalize business analysis through Role of the BA in Solution Validation: the Behavioral characteristicsstandardization V Model Business knowledgeImprove communication through modeling Solution Acceptance and Project Communication skillsLife Cycle Models Close-Out Interaction skillsWaterfall Role of the BA on the Enterprise Analysis Software application knowledgeIncremental Team Best PracticesAgile Steps in Enterprise Analysis Use iterative analysisEffects on business analysis Define the business need Focus on process improvementLeadership Skills Techniques for root cause analysis Apply progressive elaborationProblem-Solving Skills Assess capability gaps Check as you goBusiness Knowledge SWOT analysis Use the investigative approachIT Knowledge Determine the solution approach Adopt traceability

Define the solution scope Formalize business analysis throughDefine the business case standardization

line Contents of business case Improve communication through modelingRole of the BA Who does what?: the BA's limited role in Life Cycle ModelsStandardization and Adaptability developing a business case WaterfallVision and Scope Document BA Necessary Competencies IncrementalTypes of Requirements Analytical thinking and problem solving AgileStakeholders Behavioral characteristics Effects on business analysisBusiness Analysis Plan Business knowledge Leadership SkillsIterative approach Communication skills Problem-Solving SkillsTechniques Interaction skills Business KnowledgeInterviews Software application knowledge IT KnowledgeFocus groups Best PracticesRequirements workshop: Requirements Use iterative analysismeeting Focus on process improvement lineRequirements workshop: JAD session Apply progressive elaboration Role of the BABrainstorming Check as you go Standardization and AdaptabilityObservation Use the investigative approach Vision and Scope DocumentSurvey Adopt traceability Types of RequirementsPrototype Formalize business analysis through StakeholdersDocument analysis standardization Business Analysis PlanBusiness rules analysis Improve communication through Iterative approachReverse engineering modeling TechniquesProduct trials Life Cycle Models InterviewsUsing Analysis to get Stakeholder Feedback Waterfall Focus groupsand Verify and Validate Developing Incremental Requirements workshop: RequirementsRequirements Agile meetingValue of Modeling Techniques in Analysis Effects on business analysis Requirements workshop: JAD sessionModeling Techniques Leadership Skills BrainstormingOrganizational model Problem-Solving Skills ObservationLocation model Business Knowledge SurveyProcess/flow models IT Knowledge PrototypeUse case models Document analysisData models 6. Requirements Management and Business rules analysisState model Communication Reverse engineeringTypes of Requirements line Product trialsBusiness Rules Analysis Throughout the Project and to Using Analysis to get StakeholderPrioritizing Requirements Decommission Feedback and Verify and ValidateVerifying and Validating Requirements Developing RequirementsWriting for Usability and Comprehension Value of Modeling Techniques in AnalysisCommon Requirements Document Defects line Modeling TechniquesComponents of a Formal Requirements Role of the BA Organizational model


Document Standardization and Adaptability Location modelRequirements Verification and Validation Vision and Scope Document Process/flow modelsRequirements Sign-Off Types of Requirements Use case modelsChange Management Stakeholders Data modelsDefine a baseline Business Analysis Plan State modelDefine a change management process Iterative approach Types of RequirementsIdentify the Change Authority Techniques Business Rules AnalysisTraceability and Its Uses Interviews Prioritizing RequirementsRequirements Attributes Focus groups Verifying and Validating RequirementsRequirements Communication Requirements workshop: Requirements Writing for Usability and ComprehensionPurposes of Validation meeting Common Requirements DocumentFind defects Requirements workshop: JAD session DefectsProve compliance to requirements Brainstorming Components of a Formal RequirementsTest Cases and Test Suites Observation DocumentChallenges in Testing Survey Requirements Verification and ValidationStructured Testing Prototype Requirements Sign-OffRole of the BA in Solution Validation: the V Document analysis Change ManagementModel Business rules analysis Define a baselineSolution Acceptance and Project Close-Out Reverse engineering Define a change management processRole of the BA on the Enterprise Analysis Product trials Identify the Change AuthorityTeam Using Analysis to get Stakeholder Traceability and Its UsesSteps in Enterprise Analysis Feedback and Verify and Validate Requirements AttributesDefine the business need Developing Requirements Requirements CommunicationTechniques for root cause analysis Value of Modeling Techniques in Purposes of ValidationAssess capability gaps Analysis Find defectsSWOT analysis Modeling Techniques Prove compliance to requirementsDetermine the solution approach Organizational model Test Cases and Test SuitesDefine the solution scope Location model Challenges in TestingDefine the business case Process/flow models Structured TestingContents of business case Use case models Role of the BA in Solution Validation: the VWho does what?: the BA's limited role in Data models Modeldeveloping a business case State model Solution Acceptance and ProjectBA Necessary Competencies Types of Requirements Close-OutAnalytical thinking and problem solving Business Rules Analysis Role of the BA on the Enterprise AnalysisBehavioral characteristics Prioritizing Requirements TeamBusiness knowledge Verifying and Validating Requirements Steps in Enterprise AnalysisCommunication skills Writing for Usability and Comprehension Define the business needInteraction skills Common Requirements Document Techniques for root cause analysisSoftware application knowledge Defects Assess capability gapsBest Practices Components of a Formal Requirements SWOT analysisUse iterative analysis Document Determine the solution approachFocus on process improvement Requirements Verification and Validation Define the solution scopeApply progressive elaboration Requirements Sign-Off Define the business caseCheck as you go Change Management Contents of business caseUse the investigative approach Define a baseline Who does what?: the BA's limited role inAdopt traceability Define a change management process developing a business caseFormalize business analysis through Identify the Change Authority BA Necessary Competenciesstandardization Traceability and Its Uses Analytical thinking and problem solvingImprove communication through modeling Requirements Attributes Behavioral characteristicsLife Cycle Models Requirements Communication Business knowledgeWaterfall Purposes of Validation Communication skillsIncremental Find defects Interaction skillsAgile Prove compliance to requirements Software application knowledgeEffects on business analysis Test Cases and Test Suites Best PracticesLeadership Skills Challenges in Testing Use iterative analysisProblem-Solving Skills Structured Testing Focus on process improvementBusiness Knowledge Role of the BA in Solution Validation: the Apply progressive elaborationIT Knowledge V Model Check as you go

Solution Acceptance and Project Use the investigative approachClose-Out Adopt traceability

line Role of the BA on the Enterprise Analysis Formalize business analysis throughRole of the BA Team standardizationStandardization and Adaptability Steps in Enterprise Analysis Improve communication through modelingVision and Scope Document Define the business need Life Cycle ModelsTypes of Requirements Techniques for root cause analysis WaterfallStakeholders Assess capability gaps Incremental


Business Analysis Plan SWOT analysis AgileIterative approach Determine the solution approach Effects on business analysisTechniques Define the solution scope Leadership SkillsInterviews Define the business case Problem-Solving SkillsFocus groups Contents of business case Business KnowledgeRequirements workshop: Requirements Who does what?: the BA's limited role in IT Knowledgemeeting developing a business caseRequirements workshop: JAD session BA Necessary CompetenciesBrainstorming Analytical thinking and problem solving lineObservation Behavioral characteristics Role of the BASurvey Business knowledge Standardization and AdaptabilityPrototype Communication skills Vision and Scope DocumentDocument analysis Interaction skills Types of RequirementsBusiness rules analysis Software application knowledge StakeholdersReverse engineering Best Practices Business Analysis PlanProduct trials Use iterative analysis Iterative approachUsing Analysis to get Stakeholder Feedback Focus on process improvement Techniquesand Verify and Validate Developing Apply progressive elaboration InterviewsRequirements Check as you go Focus groupsValue of Modeling Techniques in Analysis Use the investigative approach Requirements workshop: RequirementsModeling Techniques Adopt traceability meetingOrganizational model Formalize business analysis through Requirements workshop: JAD sessionLocation model standardization BrainstormingProcess/flow models Improve communication through ObservationUse case models modeling SurveyData models Life Cycle Models PrototypeState model Waterfall Document analysisTypes of Requirements Incremental Business rules analysisBusiness Rules Analysis Agile Reverse engineeringPrioritizing Requirements Effects on business analysis Product trialsVerifying and Validating Requirements Leadership Skills Using Analysis to get StakeholderWriting for Usability and Comprehension Problem-Solving Skills Feedback and Verify and ValidateCommon Requirements Document Defects Business Knowledge Developing RequirementsComponents of a Formal Requirements IT Knowledge Value of Modeling Techniques in AnalysisDocument Modeling TechniquesRequirements Verification and Validation Organizational modelRequirements Sign-Off line Location modelChange Management Role of the BA Process/flow modelsDefine a baseline Standardization and Adaptability Use case modelsDefine a change management process Vision and Scope Document Data modelsIdentify the Change Authority Types of Requirements State modelTraceability and Its Uses Stakeholders Types of RequirementsRequirements Attributes Business Analysis Plan Business Rules AnalysisRequirements Communication Iterative approach Prioritizing RequirementsPurposes of Validation Techniques Verifying and Validating RequirementsFind defects Interviews Writing for Usability and ComprehensionProve compliance to requirements Focus groups Common Requirements DocumentTest Cases and Test Suites Requirements workshop: Requirements DefectsChallenges in Testing meeting Components of a Formal RequirementsStructured Testing Requirements workshop: JAD session DocumentRole of the BA in Solution Validation: the V Brainstorming Requirements Verification and ValidationModel Observation Requirements Sign-OffSolution Acceptance and Project Close-Out Survey Change ManagementRole of the BA on the Enterprise Analysis Prototype Define a baselineTeam Document analysis Define a change management processSteps in Enterprise Analysis Business rules analysis Identify the Change AuthorityDefine the business need Reverse engineering Traceability and Its UsesTechniques for root cause analysis Product trials Requirements AttributesAssess capability gaps Using Analysis to get Stakeholder Requirements CommunicationSWOT analysis Feedback and Verify and Validate Purposes of ValidationDetermine the solution approach Developing Requirements Find defectsDefine the solution scope Value of Modeling Techniques in Prove compliance to requirementsDefine the business case Analysis Test Cases and Test SuitesContents of business case Modeling Techniques Challenges in TestingWho does what?: the BA's limited role in Organizational model Structured Testingdeveloping a business case Location model Role of the BA in Solution Validation: the V


BA Necessary Competencies Process/flow models ModelAnalytical thinking and problem solving Use case models Solution Acceptance and ProjectBehavioral characteristics Data models Close-OutBusiness knowledge State model Role of the BA on the Enterprise AnalysisCommunication skills Types of Requirements TeamInteraction skills Business Rules Analysis Steps in Enterprise AnalysisSoftware application knowledge Prioritizing Requirements Define the business needBest Practices Verifying and Validating Requirements Techniques for root cause analysisUse iterative analysis Writing for Usability and Comprehension Assess capability gapsFocus on process improvement Common Requirements Document SWOT analysisApply progressive elaboration Defects Determine the solution approachCheck as you go Components of a Formal Requirements Define the solution scopeUse the investigative approach Document Define the business caseAdopt traceability Requirements Verification and Validation Contents of business caseFormalize business analysis through Requirements Sign-Off Who does what?: the BA's limited role instandardization Change Management developing a business caseImprove communication through modeling Define a baseline BA Necessary CompetenciesLife Cycle Models Define a change management process Analytical thinking and problem solvingWaterfall Identify the Change Authority Behavioral characteristicsIncremental Traceability and Its Uses Business knowledgeAgile Requirements Attributes Communication skillsEffects on business analysis Requirements Communication Interaction skillsLeadership Skills Purposes of Validation Software application knowledgeProblem-Solving Skills Find defects Best PracticesBusiness Knowledge Prove compliance to requirements Use iterative analysisIT Knowledge Test Cases and Test Suites Focus on process improvement

Challenges in Testing Apply progressive elaborationStructured Testing Check as you go

line Role of the BA in Solution Validation: the Use the investigative approachRole of the BA V Model Adopt traceabilityStandardization and Adaptability Solution Acceptance and Project Formalize business analysis throughVision and Scope Document Close-Out standardizationTypes of Requirements Role of the BA on the Enterprise Analysis Improve communication through modelingStakeholders Team Life Cycle ModelsBusiness Analysis Plan Steps in Enterprise Analysis WaterfallIterative approach Define the business need IncrementalTechniques Techniques for root cause analysis AgileInterviews Assess capability gaps Effects on business analysisFocus groups SWOT analysis Leadership SkillsRequirements workshop: Requirements Determine the solution approach Problem-Solving Skillsmeeting Define the solution scope Business KnowledgeRequirements workshop: JAD session Define the business case IT KnowledgeBrainstorming Contents of business caseObservation Who does what?: the BA's limited role inSurvey developing a business case linePrototype BA Necessary Competencies Role of the BADocument analysis Analytical thinking and problem solving Standardization and AdaptabilityBusiness rules analysis Behavioral characteristics Vision and Scope DocumentReverse engineering Business knowledge Types of RequirementsProduct trials Communication skills StakeholdersUsing Analysis to get Stakeholder Feedback Interaction skills Business Analysis Planand Verify and Validate Developing Software application knowledge Iterative approachRequirements Best Practices TechniquesValue of Modeling Techniques in Analysis Use iterative analysis InterviewsModeling Techniques Focus on process improvement Focus groupsOrganizational model Apply progressive elaboration Requirements workshop: RequirementsLocation model Check as you go meetingProcess/flow models Use the investigative approach Requirements workshop: JAD sessionUse case models Adopt traceability BrainstormingData models Formalize business analysis through ObservationState model standardization SurveyTypes of Requirements Improve communication through PrototypeBusiness Rules Analysis modeling Document analysisPrioritizing Requirements Life Cycle Models Business rules analysisVerifying and Validating Requirements Waterfall Reverse engineeringWriting for Usability and Comprehension Incremental Product trials


Common Requirements Document Defects Agile Using Analysis to get StakeholderComponents of a Formal Requirements Effects on business analysis Feedback and Verify and ValidateDocument Leadership Skills Developing RequirementsRequirements Verification and Validation Problem-Solving Skills Value of Modeling Techniques in AnalysisRequirements Sign-Off Business Knowledge Modeling TechniquesChange Management IT Knowledge Organizational modelDefine a baseline Location modelDefine a change management process Process/flow modelsIdentify the Change Authority line Use case modelsTraceability and Its Uses Role of the BA Data modelsRequirements Attributes Standardization and Adaptability State modelRequirements Communication Vision and Scope Document Types of RequirementsPurposes of Validation Types of Requirements Business Rules AnalysisFind defects Stakeholders Prioritizing RequirementsProve compliance to requirements Business Analysis Plan Verifying and Validating RequirementsTest Cases and Test Suites Iterative approach Writing for Usability and ComprehensionChallenges in Testing Techniques Common Requirements DocumentStructured Testing Interviews DefectsRole of the BA in Solution Validation: the V Focus groups Components of a Formal RequirementsModel Requirements workshop: Requirements DocumentSolution Acceptance and Project Close-Out meeting Requirements Verification and ValidationRole of the BA on the Enterprise Analysis Requirements workshop: JAD session Requirements Sign-OffTeam Brainstorming Change ManagementSteps in Enterprise Analysis Observation Define a baselineDefine the business need Survey Define a change management processTechniques for root cause analysis Prototype Identify the Change AuthorityAssess capability gaps Document analysis Traceability and Its UsesSWOT analysis Business rules analysis Requirements AttributesDetermine the solution approach Reverse engineering Requirements CommunicationDefine the solution scope Product trials Purposes of ValidationDefine the business case Using Analysis to get Stakeholder Find defectsContents of business case Feedback and Verify and Validate Prove compliance to requirementsWho does what?: the BA's limited role in Developing Requirements Test Cases and Test Suitesdeveloping a business case Value of Modeling Techniques in Challenges in TestingBA Necessary Competencies Analysis Structured TestingAnalytical thinking and problem solving Modeling Techniques Role of the BA in Solution Validation: the VBehavioral characteristics Organizational model ModelBusiness knowledge Location model Solution Acceptance and ProjectCommunication skills Process/flow models Close-OutInteraction skills Use case models Role of the BA on the Enterprise AnalysisSoftware application knowledge Data models TeamBest Practices State model Steps in Enterprise AnalysisUse iterative analysis Types of Requirements Define the business needFocus on process improvement Business Rules Analysis Techniques for root cause analysisApply progressive elaboration Prioritizing Requirements Assess capability gapsCheck as you go Verifying and Validating Requirements SWOT analysisUse the investigative approach Writing for Usability and Comprehension Determine the solution approachAdopt traceability Common Requirements Document Define the solution scopeFormalize business analysis through Defects Define the business casestandardization Components of a Formal Requirements Contents of business caseImprove communication through modeling Document Who does what?: the BA's limited role inLife Cycle Models Requirements Verification and Validation developing a business caseWaterfall Requirements Sign-Off BA Necessary CompetenciesIncremental Change Management Analytical thinking and problem solvingAgile Define a baseline Behavioral characteristicsEffects on business analysis Define a change management process Business knowledgeLeadership Skills Identify the Change Authority Communication skillsProblem-Solving Skills Traceability and Its Uses Interaction skillsBusiness Knowledge Requirements Attributes Software application knowledgeIT Knowledge Requirements Communication Best Practices

Purposes of Validation Use iterative analysisFind defects Focus on process improvement

line Prove compliance to requirements Apply progressive elaborationRole of the BA Test Cases and Test Suites Check as you goStandardization and Adaptability Challenges in Testing Use the investigative approachVision and Scope Document Structured Testing Adopt traceability


Types of Requirements Role of the BA in Solution Validation: the Formalize business analysis throughStakeholders V Model standardizationBusiness Analysis Plan Solution Acceptance and Project Improve communication through modelingIterative approach Close-Out Life Cycle ModelsTechniques Role of the BA on the Enterprise Analysis WaterfallInterviews Team IncrementalFocus groups Steps in Enterprise Analysis AgileRequirements workshop: Requirements Define the business need Effects on business analysismeeting Techniques for root cause analysis Leadership SkillsRequirements workshop: JAD session Assess capability gaps Problem-Solving SkillsBrainstorming SWOT analysis Business KnowledgeObservation Determine the solution approach IT KnowledgeSurvey Define the solution scopePrototype Define the business caseDocument analysis Contents of business case lineBusiness rules analysis Who does what?: the BA's limited role in Role of the BAReverse engineering developing a business case Standardization and AdaptabilityProduct trials BA Necessary Competencies Vision and Scope DocumentUsing Analysis to get Stakeholder Feedback Analytical thinking and problem solving Types of Requirementsand Verify and Validate Developing Behavioral characteristics StakeholdersRequirements Business knowledge Business Analysis PlanValue of Modeling Techniques in Analysis Communication skills Iterative approachModeling Techniques Interaction skills TechniquesOrganizational model Software application knowledge InterviewsLocation model Best Practices Focus groupsProcess/flow models Use iterative analysis Requirements workshop: RequirementsUse case models Focus on process improvement meetingData models Apply progressive elaboration Requirements workshop: JAD sessionState model Check as you go BrainstormingTypes of Requirements Use the investigative approach ObservationBusiness Rules Analysis Adopt traceability SurveyPrioritizing Requirements Formalize business analysis through PrototypeVerifying and Validating Requirements standardization Document analysisWriting for Usability and Comprehension Improve communication through Business rules analysisCommon Requirements Document Defects modeling Reverse engineeringComponents of a Formal Requirements Life Cycle Models Product trialsDocument Waterfall Using Analysis to get StakeholderRequirements Verification and Validation Incremental Feedback and Verify and ValidateRequirements Sign-Off Agile Developing RequirementsChange Management Effects on business analysis Value of Modeling Techniques in AnalysisDefine a baseline Leadership Skills Modeling TechniquesDefine a change management process Problem-Solving Skills Organizational modelIdentify the Change Authority Business Knowledge Location modelTraceability and Its Uses IT Knowledge Process/flow modelsRequirements Attributes Use case modelsRequirements Communication Data modelsPurposes of Validation line State modelFind defects Role of the BA Types of RequirementsProve compliance to requirements Standardization and Adaptability Business Rules AnalysisTest Cases and Test Suites Vision and Scope Document Prioritizing RequirementsChallenges in Testing Types of Requirements Verifying and Validating RequirementsStructured Testing Stakeholders Writing for Usability and ComprehensionRole of the BA in Solution Validation: the V Business Analysis Plan Common Requirements DocumentModel Iterative approach DefectsSolution Acceptance and Project Close-Out Techniques Components of a Formal RequirementsRole of the BA on the Enterprise Analysis Interviews DocumentTeam Focus groups Requirements Verification and ValidationSteps in Enterprise Analysis Requirements workshop: Requirements Requirements Sign-OffDefine the business need meeting Change ManagementTechniques for root cause analysis Requirements workshop: JAD session Define a baselineAssess capability gaps Brainstorming Define a change management processSWOT analysis Observation Identify the Change AuthorityDetermine the solution approach Survey Traceability and Its UsesDefine the solution scope Prototype Requirements AttributesDefine the business case Document analysis Requirements CommunicationContents of business case Business rules analysis Purposes of Validation


Who does what?: the BA's limited role in Reverse engineering Find defectsdeveloping a business case Product trials Prove compliance to requirementsBA Necessary Competencies Using Analysis to get Stakeholder Test Cases and Test SuitesAnalytical thinking and problem solving Feedback and Verify and Validate Challenges in TestingBehavioral characteristics Developing Requirements Structured TestingBusiness knowledge Value of Modeling Techniques in Role of the BA in Solution Validation: the VCommunication skills Analysis ModelInteraction skills Modeling Techniques Solution Acceptance and ProjectSoftware application knowledge Organizational model Close-OutBest Practices Location model Role of the BA on the Enterprise AnalysisUse iterative analysis Process/flow models TeamFocus on process improvement Use case models Steps in Enterprise AnalysisApply progressive elaboration Data models Define the business needCheck as you go State model Techniques for root cause analysisUse the investigative approach Types of Requirements Assess capability gapsAdopt traceability Business Rules Analysis SWOT analysisFormalize business analysis through Prioritizing Requirements Determine the solution approachstandardization Verifying and Validating Requirements Define the solution scopeImprove communication through modeling Writing for Usability and Comprehension Define the business caseLife Cycle Models Common Requirements Document Contents of business caseWaterfall Defects Who does what?: the BA's limited role inIncremental Components of a Formal Requirements developing a business caseAgile Document BA Necessary CompetenciesEffects on business analysis Requirements Verification and Validation Analytical thinking and problem solvingLeadership Skills Requirements Sign-Off Behavioral characteristicsProblem-Solving Skills Change Management Business knowledgeBusiness Knowledge Define a baseline Communication skillsIT Knowledge Define a change management process Interaction skills

Identify the Change Authority Software application knowledgeTraceability and Its Uses Best Practices

line Requirements Attributes Use iterative analysisRole of the BA Requirements Communication Focus on process improvementStandardization and Adaptability Purposes of Validation Apply progressive elaborationVision and Scope Document Find defects Check as you goTypes of Requirements Prove compliance to requirements Use the investigative approachStakeholders Test Cases and Test Suites Adopt traceabilityBusiness Analysis Plan Challenges in Testing Formalize business analysis throughIterative approach Structured Testing standardizationTechniques Role of the BA in Solution Validation: the Improve communication through modelingInterviews V Model Life Cycle ModelsFocus groups Solution Acceptance and Project WaterfallRequirements workshop: Requirements Close-Out Incrementalmeeting Role of the BA on the Enterprise Analysis AgileRequirements workshop: JAD session Team Effects on business analysisBrainstorming Steps in Enterprise Analysis Leadership SkillsObservation Define the business need Problem-Solving SkillsSurvey Techniques for root cause analysis Business KnowledgePrototype Assess capability gaps IT KnowledgeDocument analysis SWOT analysisBusiness rules analysis Determine the solution approachReverse engineering Define the solution scope lineProduct trials Define the business case Role of the BAUsing Analysis to get Stakeholder Feedback Contents of business case Standardization and Adaptabilityand Verify and Validate Developing Who does what?: the BA's limited role in Vision and Scope DocumentRequirements developing a business case Types of RequirementsValue of Modeling Techniques in Analysis BA Necessary Competencies StakeholdersModeling Techniques Analytical thinking and problem solving Business Analysis PlanOrganizational model Behavioral characteristics Iterative approachLocation model Business knowledge TechniquesProcess/flow models Communication skills InterviewsUse case models Interaction skills Focus groupsData models Software application knowledge Requirements workshop: RequirementsState model Best Practices meetingTypes of Requirements Use iterative analysis Requirements workshop: JAD sessionBusiness Rules Analysis Focus on process improvement BrainstormingPrioritizing Requirements Apply progressive elaboration Observation


Verifying and Validating Requirements Check as you go SurveyWriting for Usability and Comprehension Use the investigative approach PrototypeCommon Requirements Document Defects Adopt traceability Document analysisComponents of a Formal Requirements Formalize business analysis through Business rules analysisDocument standardization Reverse engineeringRequirements Verification and Validation Improve communication through Product trialsRequirements Sign-Off modeling Using Analysis to get StakeholderChange Management Life Cycle Models Feedback and Verify and ValidateDefine a baseline Waterfall Developing RequirementsDefine a change management process Incremental Value of Modeling Techniques in AnalysisIdentify the Change Authority Agile Modeling TechniquesTraceability and Its Uses Effects on business analysis Organizational modelRequirements Attributes Leadership Skills Location modelRequirements Communication Problem-Solving Skills Process/flow modelsPurposes of Validation Business Knowledge Use case modelsFind defects IT Knowledge Data modelsProve compliance to requirements State modelTest Cases and Test Suites Types of RequirementsChallenges in Testing line Business Rules AnalysisStructured Testing Role of the BA Prioritizing RequirementsRole of the BA in Solution Validation: the V Standardization and Adaptability Verifying and Validating RequirementsModel Vision and Scope Document Writing for Usability and ComprehensionSolution Acceptance and Project Close-Out Types of Requirements Common Requirements DocumentRole of the BA on the Enterprise Analysis Stakeholders DefectsTeam Business Analysis Plan Components of a Formal RequirementsSteps in Enterprise Analysis Iterative approach DocumentDefine the business need Techniques Requirements Verification and ValidationTechniques for root cause analysis Interviews Requirements Sign-OffAssess capability gaps Focus groups Change ManagementSWOT analysis Requirements workshop: Requirements Define a baselineDetermine the solution approach meeting Define a change management processDefine the solution scope Requirements workshop: JAD session Identify the Change AuthorityDefine the business case Brainstorming Traceability and Its UsesContents of business case Observation Requirements AttributesWho does what?: the BA's limited role in Survey Requirements Communicationdeveloping a business case Prototype Purposes of ValidationBA Necessary Competencies Document analysis Find defectsAnalytical thinking and problem solving Business rules analysis Prove compliance to requirementsBehavioral characteristics Reverse engineering Test Cases and Test SuitesBusiness knowledge Product trials Challenges in TestingCommunication skills Using Analysis to get Stakeholder Structured TestingInteraction skills Feedback and Verify and Validate Role of the BA in Solution Validation: the VSoftware application knowledge Developing Requirements ModelBest Practices Value of Modeling Techniques in Solution Acceptance and ProjectUse iterative analysis Analysis Close-OutFocus on process improvement Modeling Techniques Role of the BA on the Enterprise AnalysisApply progressive elaboration Organizational model TeamCheck as you go Location model Steps in Enterprise AnalysisUse the investigative approach Process/flow models Define the business needAdopt traceability Use case models Techniques for root cause analysisFormalize business analysis through Data models Assess capability gapsstandardization State model SWOT analysisImprove communication through modeling Types of Requirements Determine the solution approachLife Cycle Models Business Rules Analysis Define the solution scopeWaterfall Prioritizing Requirements Define the business caseIncremental Verifying and Validating Requirements Contents of business caseAgile Writing for Usability and Comprehension Who does what?: the BA's limited role inEffects on business analysis Common Requirements Document developing a business caseLeadership Skills Defects BA Necessary CompetenciesProblem-Solving Skills Components of a Formal Requirements Analytical thinking and problem solvingBusiness Knowledge Document Behavioral characteristicsIT Knowledge Requirements Verification and Validation Business knowledge

Requirements Sign-Off Communication skillsChange Management Interaction skills

line Define a baseline Software application knowledgeRole of the BA Define a change management process Best Practices


Standardization and Adaptability Identify the Change Authority Use iterative analysisVision and Scope Document Traceability and Its Uses Focus on process improvementTypes of Requirements Requirements Attributes Apply progressive elaborationStakeholders Requirements Communication Check as you goBusiness Analysis Plan Purposes of Validation Use the investigative approachIterative approach Find defects Adopt traceabilityTechniques Prove compliance to requirements Formalize business analysis throughInterviews Test Cases and Test Suites standardizationFocus groups Challenges in Testing Improve communication through modelingRequirements workshop: Requirements Structured Testing Life Cycle Modelsmeeting Role of the BA in Solution Validation: the WaterfallRequirements workshop: JAD session V Model IncrementalBrainstorming Solution Acceptance and Project AgileObservation Close-Out Effects on business analysisSurvey Role of the BA on the Enterprise Analysis Leadership SkillsPrototype Team Problem-Solving SkillsDocument analysis Steps in Enterprise Analysis Business KnowledgeBusiness rules analysis Define the business need IT KnowledgeReverse engineering Techniques for root cause analysisProduct trials Assess capability gapsUsing Analysis to get Stakeholder Feedback SWOT analysis lineand Verify and Validate Developing Determine the solution approach Role of the BARequirements Define the solution scope Standardization and AdaptabilityValue of Modeling Techniques in Analysis Define the business case Vision and Scope DocumentModeling Techniques Contents of business case Types of RequirementsOrganizational model Who does what?: the BA's limited role in StakeholdersLocation model developing a business case Business Analysis PlanProcess/flow models BA Necessary Competencies Iterative approachUse case models Analytical thinking and problem solving TechniquesData models Behavioral characteristics InterviewsState model Business knowledge Focus groupsTypes of Requirements Communication skills Requirements workshop: RequirementsBusiness Rules Analysis Interaction skills meetingPrioritizing Requirements Software application knowledge Requirements workshop: JAD sessionVerifying and Validating Requirements Best Practices BrainstormingWriting for Usability and Comprehension Use iterative analysis ObservationCommon Requirements Document Defects Focus on process improvement SurveyComponents of a Formal Requirements Apply progressive elaboration PrototypeDocument Check as you go Document analysisRequirements Verification and Validation Use the investigative approach Business rules analysisRequirements Sign-Off Adopt traceability Reverse engineeringChange Management Formalize business analysis through Product trialsDefine a baseline standardization Using Analysis to get StakeholderDefine a change management process Improve communication through Feedback and Verify and ValidateIdentify the Change Authority modeling Developing RequirementsTraceability and Its Uses Life Cycle Models Value of Modeling Techniques in AnalysisRequirements Attributes Waterfall Modeling TechniquesRequirements Communication Incremental Organizational modelPurposes of Validation Agile Location modelFind defects Effects on business analysis Process/flow modelsProve compliance to requirements Leadership Skills Use case modelsTest Cases and Test Suites Problem-Solving Skills Data modelsChallenges in Testing Business Knowledge State modelStructured Testing IT Knowledge Types of RequirementsRole of the BA in Solution Validation: the V Business Rules AnalysisModel Prioritizing RequirementsSolution Acceptance and Project Close-Out line Verifying and Validating RequirementsRole of the BA on the Enterprise Analysis Role of the BA Writing for Usability and ComprehensionTeam Standardization and Adaptability Common Requirements DocumentSteps in Enterprise Analysis Vision and Scope Document DefectsDefine the business need Types of Requirements Components of a Formal RequirementsTechniques for root cause analysis Stakeholders DocumentAssess capability gaps Business Analysis Plan Requirements Verification and ValidationSWOT analysis Iterative approach Requirements Sign-OffDetermine the solution approach Techniques Change ManagementDefine the solution scope Interviews Define a baseline


Define the business case Focus groups Define a change management processContents of business case Requirements workshop: Requirements Identify the Change AuthorityWho does what?: the BA's limited role in meeting Traceability and Its Usesdeveloping a business case Requirements workshop: JAD session Requirements AttributesBA Necessary Competencies Brainstorming Requirements CommunicationAnalytical thinking and problem solving Observation Purposes of ValidationBehavioral characteristics Survey Find defectsBusiness knowledge Prototype Prove compliance to requirementsCommunication skills Document analysis Test Cases and Test SuitesInteraction skills Business rules analysis Challenges in TestingSoftware application knowledge Reverse engineering Structured TestingBest Practices Product trials Role of the BA in Solution Validation: the VUse iterative analysis Using Analysis to get Stakeholder ModelFocus on process improvement Feedback and Verify and Validate Solution Acceptance and ProjectApply progressive elaboration Developing Requirements Close-OutCheck as you go Value of Modeling Techniques in Role of the BA on the Enterprise AnalysisUse the investigative approach Analysis TeamAdopt traceability Modeling Techniques Steps in Enterprise AnalysisFormalize business analysis through Organizational model Define the business needstandardization Location model Techniques for root cause analysisImprove communication through modeling Process/flow models Assess capability gapsLife Cycle Models Use case models SWOT analysisWaterfall Data models Determine the solution approachIncremental State model Define the solution scopeAgile Types of Requirements Define the business caseEffects on business analysis Business Rules Analysis Contents of business caseLeadership Skills Prioritizing Requirements Who does what?: the BA's limited role inProblem-Solving Skills Verifying and Validating Requirements developing a business caseBusiness Knowledge Writing for Usability and Comprehension BA Necessary CompetenciesIT Knowledge Common Requirements Document Analytical thinking and problem solving

Defects Behavioral characteristicsComponents of a Formal Requirements Business knowledge

line Document Communication skillsRole of the BA Requirements Verification and Validation Interaction skillsStandardization and Adaptability Requirements Sign-Off Software application knowledgeVision and Scope Document Change Management Best PracticesTypes of Requirements Define a baseline Use iterative analysisStakeholders Define a change management process Focus on process improvementBusiness Analysis Plan Identify the Change Authority Apply progressive elaborationIterative approach Traceability and Its Uses Check as you goTechniques Requirements Attributes Use the investigative approachInterviews Requirements Communication Adopt traceabilityFocus groups Purposes of Validation Formalize business analysis throughRequirements workshop: Requirements Find defects standardizationmeeting Prove compliance to requirements Improve communication through modelingRequirements workshop: JAD session Test Cases and Test Suites Life Cycle ModelsBrainstorming Challenges in Testing WaterfallObservation Structured Testing IncrementalSurvey Role of the BA in Solution Validation: the AgilePrototype V Model Effects on business analysisDocument analysis Solution Acceptance and Project Leadership SkillsBusiness rules analysis Close-Out Problem-Solving SkillsReverse engineering Role of the BA on the Enterprise Analysis Business KnowledgeProduct trials Team IT KnowledgeUsing Analysis to get Stakeholder Feedback Steps in Enterprise Analysisand Verify and Validate Developing Define the business needRequirements Techniques for root cause analysis lineValue of Modeling Techniques in Analysis Assess capability gaps Role of the BAModeling Techniques SWOT analysis Standardization and AdaptabilityOrganizational model Determine the solution approach Vision and Scope DocumentLocation model Define the solution scope Types of RequirementsProcess/flow models Define the business case StakeholdersUse case models Contents of business case Business Analysis PlanData models Who does what?: the BA's limited role in Iterative approachState model developing a business case TechniquesTypes of Requirements BA Necessary Competencies Interviews


Business Rules Analysis Analytical thinking and problem solving Focus groupsPrioritizing Requirements Behavioral characteristics Requirements workshop: RequirementsVerifying and Validating Requirements Business knowledge meetingWriting for Usability and Comprehension Communication skills Requirements workshop: JAD sessionCommon Requirements Document Defects Interaction skills BrainstormingComponents of a Formal Requirements Software application knowledge ObservationDocument Best Practices SurveyRequirements Verification and Validation Use iterative analysis PrototypeRequirements Sign-Off Focus on process improvement Document analysisChange Management Apply progressive elaboration Business rules analysisDefine a baseline Check as you go Reverse engineeringDefine a change management process Use the investigative approach Product trialsIdentify the Change Authority Adopt traceability Using Analysis to get StakeholderTraceability and Its Uses Formalize business analysis through Feedback and Verify and ValidateRequirements Attributes standardization Developing RequirementsRequirements Communication Improve communication through Value of Modeling Techniques in AnalysisPurposes of Validation modeling Modeling TechniquesFind defects Life Cycle Models Organizational modelProve compliance to requirements Waterfall Location modelTest Cases and Test Suites Incremental Process/flow modelsChallenges in Testing Agile Use case modelsStructured Testing Effects on business analysis Data modelsRole of the BA in Solution Validation: the V Leadership Skills State modelModel Problem-Solving Skills Types of RequirementsSolution Acceptance and Project Close-Out Business Knowledge Business Rules AnalysisRole of the BA on the Enterprise Analysis IT Knowledge Prioritizing RequirementsTeam Verifying and Validating RequirementsSteps in Enterprise Analysis 7. Solution Validation and Acceptance Writing for Usability and ComprehensionDefine the business need line Common Requirements DocumentTechniques for root cause analysis Testing and Non-Testing Methods DefectsAssess capability gaps Components of a Formal RequirementsSWOT analysis DocumentDetermine the solution approach line Requirements Verification and ValidationDefine the solution scope Role of the BA Requirements Sign-OffDefine the business case Standardization and Adaptability Change ManagementContents of business case Vision and Scope Document Define a baselineWho does what?: the BA's limited role in Types of Requirements Define a change management processdeveloping a business case Stakeholders Identify the Change AuthorityBA Necessary Competencies Business Analysis Plan Traceability and Its UsesAnalytical thinking and problem solving Iterative approach Requirements AttributesBehavioral characteristics Techniques Requirements CommunicationBusiness knowledge Interviews Purposes of ValidationCommunication skills Focus groups Find defectsInteraction skills Requirements workshop: Requirements Prove compliance to requirementsSoftware application knowledge meeting Test Cases and Test SuitesBest Practices Requirements workshop: JAD session Challenges in TestingUse iterative analysis Brainstorming Structured TestingFocus on process improvement Observation Role of the BA in Solution Validation: the VApply progressive elaboration Survey ModelCheck as you go Prototype Solution Acceptance and ProjectUse the investigative approach Document analysis Close-OutAdopt traceability Business rules analysis Role of the BA on the Enterprise AnalysisFormalize business analysis through Reverse engineering Teamstandardization Product trials Steps in Enterprise AnalysisImprove communication through modeling Using Analysis to get Stakeholder Define the business needLife Cycle Models Feedback and Verify and Validate Techniques for root cause analysisWaterfall Developing Requirements Assess capability gapsIncremental Value of Modeling Techniques in SWOT analysisAgile Analysis Determine the solution approachEffects on business analysis Modeling Techniques Define the solution scopeLeadership Skills Organizational model Define the business caseProblem-Solving Skills Location model Contents of business caseBusiness Knowledge Process/flow models Who does what?: the BA's limited role inIT Knowledge Use case models developing a business case

Data models BA Necessary CompetenciesState model Analytical thinking and problem solving


line Types of Requirements Behavioral characteristicsRole of the BA Business Rules Analysis Business knowledgeStandardization and Adaptability Prioritizing Requirements Communication skillsVision and Scope Document Verifying and Validating Requirements Interaction skillsTypes of Requirements Writing for Usability and Comprehension Software application knowledgeStakeholders Common Requirements Document Best PracticesBusiness Analysis Plan Defects Use iterative analysisIterative approach Components of a Formal Requirements Focus on process improvementTechniques Document Apply progressive elaborationInterviews Requirements Verification and Validation Check as you goFocus groups Requirements Sign-Off Use the investigative approachRequirements workshop: Requirements Change Management Adopt traceabilitymeeting Define a baseline Formalize business analysis throughRequirements workshop: JAD session Define a change management process standardizationBrainstorming Identify the Change Authority Improve communication through modelingObservation Traceability and Its Uses Life Cycle ModelsSurvey Requirements Attributes WaterfallPrototype Requirements Communication IncrementalDocument analysis Purposes of Validation AgileBusiness rules analysis Find defects Effects on business analysisReverse engineering Prove compliance to requirements Leadership SkillsProduct trials Test Cases and Test Suites Problem-Solving SkillsUsing Analysis to get Stakeholder Feedback Challenges in Testing Business Knowledgeand Verify and Validate Developing Structured Testing IT KnowledgeRequirements Role of the BA in Solution Validation: theValue of Modeling Techniques in Analysis V ModelModeling Techniques Solution Acceptance and Project lineOrganizational model Close-Out Role of the BALocation model Role of the BA on the Enterprise Analysis Standardization and AdaptabilityProcess/flow models Team Vision and Scope DocumentUse case models Steps in Enterprise Analysis Types of RequirementsData models Define the business need StakeholdersState model Techniques for root cause analysis Business Analysis PlanTypes of Requirements Assess capability gaps Iterative approachBusiness Rules Analysis SWOT analysis TechniquesPrioritizing Requirements Determine the solution approach InterviewsVerifying and Validating Requirements Define the solution scope Focus groupsWriting for Usability and Comprehension Define the business case Requirements workshop: RequirementsCommon Requirements Document Defects Contents of business case meetingComponents of a Formal Requirements Who does what?: the BA's limited role in Requirements workshop: JAD sessionDocument developing a business case BrainstormingRequirements Verification and Validation BA Necessary Competencies ObservationRequirements Sign-Off Analytical thinking and problem solving SurveyChange Management Behavioral characteristics PrototypeDefine a baseline Business knowledge Document analysisDefine a change management process Communication skills Business rules analysisIdentify the Change Authority Interaction skills Reverse engineeringTraceability and Its Uses Software application knowledge Product trialsRequirements Attributes Best Practices Using Analysis to get StakeholderRequirements Communication Use iterative analysis Feedback and Verify and ValidatePurposes of Validation Focus on process improvement Developing RequirementsFind defects Apply progressive elaboration Value of Modeling Techniques in AnalysisProve compliance to requirements Check as you go Modeling TechniquesTest Cases and Test Suites Use the investigative approach Organizational modelChallenges in Testing Adopt traceability Location modelStructured Testing Formalize business analysis through Process/flow modelsRole of the BA in Solution Validation: the V standardization Use case modelsModel Improve communication through Data modelsSolution Acceptance and Project Close-Out modeling State modelRole of the BA on the Enterprise Analysis Life Cycle Models Types of RequirementsTeam Waterfall Business Rules AnalysisSteps in Enterprise Analysis Incremental Prioritizing RequirementsDefine the business need Agile Verifying and Validating RequirementsTechniques for root cause analysis Effects on business analysis Writing for Usability and ComprehensionAssess capability gaps Leadership Skills Common Requirements DocumentSWOT analysis Problem-Solving Skills Defects


Determine the solution approach Business Knowledge Components of a Formal RequirementsDefine the solution scope IT Knowledge DocumentDefine the business case Requirements Verification and ValidationContents of business case Requirements Sign-OffWho does what?: the BA's limited role in line Change Managementdeveloping a business case Role of the BA Define a baselineBA Necessary Competencies Standardization and Adaptability Define a change management processAnalytical thinking and problem solving Vision and Scope Document Identify the Change AuthorityBehavioral characteristics Types of Requirements Traceability and Its UsesBusiness knowledge Stakeholders Requirements AttributesCommunication skills Business Analysis Plan Requirements CommunicationInteraction skills Iterative approach Purposes of ValidationSoftware application knowledge Techniques Find defectsBest Practices Interviews Prove compliance to requirementsUse iterative analysis Focus groups Test Cases and Test SuitesFocus on process improvement Requirements workshop: Requirements Challenges in TestingApply progressive elaboration meeting Structured TestingCheck as you go Requirements workshop: JAD session Role of the BA in Solution Validation: the VUse the investigative approach Brainstorming ModelAdopt traceability Observation Solution Acceptance and ProjectFormalize business analysis through Survey Close-Outstandardization Prototype Role of the BA on the Enterprise AnalysisImprove communication through modeling Document analysis TeamLife Cycle Models Business rules analysis Steps in Enterprise AnalysisWaterfall Reverse engineering Define the business needIncremental Product trials Techniques for root cause analysisAgile Using Analysis to get Stakeholder Assess capability gapsEffects on business analysis Feedback and Verify and Validate SWOT analysisLeadership Skills Developing Requirements Determine the solution approachProblem-Solving Skills Value of Modeling Techniques in Define the solution scopeBusiness Knowledge Analysis Define the business caseIT Knowledge Modeling Techniques Contents of business case

Organizational model Who does what?: the BA's limited role inLocation model developing a business case

line Process/flow models BA Necessary CompetenciesRole of the BA Use case models Analytical thinking and problem solvingStandardization and Adaptability Data models Behavioral characteristicsVision and Scope Document State model Business knowledgeTypes of Requirements Types of Requirements Communication skillsStakeholders Business Rules Analysis Interaction skillsBusiness Analysis Plan Prioritizing Requirements Software application knowledgeIterative approach Verifying and Validating Requirements Best PracticesTechniques Writing for Usability and Comprehension Use iterative analysisInterviews Common Requirements Document Focus on process improvementFocus groups Defects Apply progressive elaborationRequirements workshop: Requirements Components of a Formal Requirements Check as you gomeeting Document Use the investigative approachRequirements workshop: JAD session Requirements Verification and Validation Adopt traceabilityBrainstorming Requirements Sign-Off Formalize business analysis throughObservation Change Management standardizationSurvey Define a baseline Improve communication through modelingPrototype Define a change management process Life Cycle ModelsDocument analysis Identify the Change Authority WaterfallBusiness rules analysis Traceability and Its Uses IncrementalReverse engineering Requirements Attributes AgileProduct trials Requirements Communication Effects on business analysisUsing Analysis to get Stakeholder Feedback Purposes of Validation Leadership Skillsand Verify and Validate Developing Find defects Problem-Solving SkillsRequirements Prove compliance to requirements Business KnowledgeValue of Modeling Techniques in Analysis Test Cases and Test Suites IT KnowledgeModeling Techniques Challenges in TestingOrganizational model Structured TestingLocation model Role of the BA in Solution Validation: the lineProcess/flow models V Model Role of the BAUse case models Solution Acceptance and Project Standardization and AdaptabilityData models Close-Out Vision and Scope Document


State model Role of the BA on the Enterprise Analysis Types of RequirementsTypes of Requirements Team StakeholdersBusiness Rules Analysis Steps in Enterprise Analysis Business Analysis PlanPrioritizing Requirements Define the business need Iterative approachVerifying and Validating Requirements Techniques for root cause analysis TechniquesWriting for Usability and Comprehension Assess capability gaps InterviewsCommon Requirements Document Defects SWOT analysis Focus groupsComponents of a Formal Requirements Determine the solution approach Requirements workshop: RequirementsDocument Define the solution scope meetingRequirements Verification and Validation Define the business case Requirements workshop: JAD sessionRequirements Sign-Off Contents of business case BrainstormingChange Management Who does what?: the BA's limited role in ObservationDefine a baseline developing a business case SurveyDefine a change management process BA Necessary Competencies PrototypeIdentify the Change Authority Analytical thinking and problem solving Document analysisTraceability and Its Uses Behavioral characteristics Business rules analysisRequirements Attributes Business knowledge Reverse engineeringRequirements Communication Communication skills Product trialsPurposes of Validation Interaction skills Using Analysis to get StakeholderFind defects Software application knowledge Feedback and Verify and ValidateProve compliance to requirements Best Practices Developing RequirementsTest Cases and Test Suites Use iterative analysis Value of Modeling Techniques in AnalysisChallenges in Testing Focus on process improvement Modeling TechniquesStructured Testing Apply progressive elaboration Organizational modelRole of the BA in Solution Validation: the V Check as you go Location modelModel Use the investigative approach Process/flow modelsSolution Acceptance and Project Close-Out Adopt traceability Use case modelsRole of the BA on the Enterprise Analysis Formalize business analysis through Data modelsTeam standardization State modelSteps in Enterprise Analysis Improve communication through Types of RequirementsDefine the business need modeling Business Rules AnalysisTechniques for root cause analysis Life Cycle Models Prioritizing RequirementsAssess capability gaps Waterfall Verifying and Validating RequirementsSWOT analysis Incremental Writing for Usability and ComprehensionDetermine the solution approach Agile Common Requirements DocumentDefine the solution scope Effects on business analysis DefectsDefine the business case Leadership Skills Components of a Formal RequirementsContents of business case Problem-Solving Skills DocumentWho does what?: the BA's limited role in Business Knowledge Requirements Verification and Validationdeveloping a business case IT Knowledge Requirements Sign-OffBA Necessary Competencies Change ManagementAnalytical thinking and problem solving Define a baselineBehavioral characteristics line Define a change management processBusiness knowledge Role of the BA Identify the Change AuthorityCommunication skills Standardization and Adaptability Traceability and Its UsesInteraction skills Vision and Scope Document Requirements AttributesSoftware application knowledge Types of Requirements Requirements CommunicationBest Practices Stakeholders Purposes of ValidationUse iterative analysis Business Analysis Plan Find defectsFocus on process improvement Iterative approach Prove compliance to requirementsApply progressive elaboration Techniques Test Cases and Test SuitesCheck as you go Interviews Challenges in TestingUse the investigative approach Focus groups Structured TestingAdopt traceability Requirements workshop: Requirements Role of the BA in Solution Validation: the VFormalize business analysis through meeting Modelstandardization Requirements workshop: JAD session Solution Acceptance and ProjectImprove communication through modeling Brainstorming Close-OutLife Cycle Models Observation Role of the BA on the Enterprise AnalysisWaterfall Survey TeamIncremental Prototype Steps in Enterprise AnalysisAgile Document analysis Define the business needEffects on business analysis Business rules analysis Techniques for root cause analysisLeadership Skills Reverse engineering Assess capability gapsProblem-Solving Skills Product trials SWOT analysisBusiness Knowledge Using Analysis to get Stakeholder Determine the solution approachIT Knowledge Feedback and Verify and Validate Define the solution scope


Developing Requirements Define the business case4. Requirements Analysis Value of Modeling Techniques in Contents of business caseline Analysis Who does what?: the BA's limited role in

Need for Analysis Modeling Techniques developing a business caseOrganizational model BA Necessary CompetenciesLocation model Analytical thinking and problem solving

line Process/flow models Behavioral characteristicsRole of the BA Use case models Business knowledgeStandardization and Adaptability Data models Communication skillsVision and Scope Document State model Interaction skillsTypes of Requirements Types of Requirements Software application knowledgeStakeholders Business Rules Analysis Best PracticesBusiness Analysis Plan Prioritizing Requirements Use iterative analysisIterative approach Verifying and Validating Requirements Focus on process improvementTechniques Writing for Usability and Comprehension Apply progressive elaborationInterviews Common Requirements Document Check as you goFocus groups Defects Use the investigative approachRequirements workshop: Requirements Components of a Formal Requirements Adopt traceabilitymeeting Document Formalize business analysis throughRequirements workshop: JAD session Requirements Verification and Validation standardizationBrainstorming Requirements Sign-Off Improve communication through modelingObservation Change Management Life Cycle ModelsSurvey Define a baseline WaterfallPrototype Define a change management process IncrementalDocument analysis Identify the Change Authority AgileBusiness rules analysis Traceability and Its Uses Effects on business analysisReverse engineering Requirements Attributes Leadership SkillsProduct trials Requirements Communication Problem-Solving SkillsUsing Analysis to get Stakeholder Feedback Purposes of Validation Business Knowledgeand Verify and Validate Developing Find defects IT KnowledgeRequirements Prove compliance to requirementsValue of Modeling Techniques in Analysis Test Cases and Test SuitesModeling Techniques Challenges in Testing lineOrganizational model Structured Testing Role of the BALocation model Role of the BA in Solution Validation: the Standardization and AdaptabilityProcess/flow models V Model Vision and Scope DocumentUse case models Solution Acceptance and Project Types of RequirementsData models Close-Out StakeholdersState model Role of the BA on the Enterprise Analysis Business Analysis PlanTypes of Requirements Team Iterative approachBusiness Rules Analysis Steps in Enterprise Analysis TechniquesPrioritizing Requirements Define the business need InterviewsVerifying and Validating Requirements Techniques for root cause analysis Focus groupsWriting for Usability and Comprehension Assess capability gaps Requirements workshop: RequirementsCommon Requirements Document Defects SWOT analysis meetingComponents of a Formal Requirements Determine the solution approach Requirements workshop: JAD sessionDocument Define the solution scope BrainstormingRequirements Verification and Validation Define the business case ObservationRequirements Sign-Off Contents of business case SurveyChange Management Who does what?: the BA's limited role in PrototypeDefine a baseline developing a business case Document analysisDefine a change management process BA Necessary Competencies Business rules analysisIdentify the Change Authority Analytical thinking and problem solving Reverse engineeringTraceability and Its Uses Behavioral characteristics Product trialsRequirements Attributes Business knowledge Using Analysis to get StakeholderRequirements Communication Communication skills Feedback and Verify and ValidatePurposes of Validation Interaction skills Developing RequirementsFind defects Software application knowledge Value of Modeling Techniques in AnalysisProve compliance to requirements Best Practices Modeling TechniquesTest Cases and Test Suites Use iterative analysis Organizational modelChallenges in Testing Focus on process improvement Location modelStructured Testing Apply progressive elaboration Process/flow modelsRole of the BA in Solution Validation: the V Check as you go Use case modelsModel Use the investigative approach Data modelsSolution Acceptance and Project Close-Out Adopt traceability State modelRole of the BA on the Enterprise Analysis Formalize business analysis through Types of Requirements


Team standardization Business Rules AnalysisSteps in Enterprise Analysis Improve communication through Prioritizing RequirementsDefine the business need modeling Verifying and Validating RequirementsTechniques for root cause analysis Life Cycle Models Writing for Usability and ComprehensionAssess capability gaps Waterfall Common Requirements DocumentSWOT analysis Incremental DefectsDetermine the solution approach Agile Components of a Formal RequirementsDefine the solution scope Effects on business analysis DocumentDefine the business case Leadership Skills Requirements Verification and ValidationContents of business case Problem-Solving Skills Requirements Sign-OffWho does what?: the BA's limited role in Business Knowledge Change Managementdeveloping a business case IT Knowledge Define a baselineBA Necessary Competencies Define a change management processAnalytical thinking and problem solving Identify the Change AuthorityBehavioral characteristics line Traceability and Its UsesBusiness knowledge Role of the BA Requirements AttributesCommunication skills Standardization and Adaptability Requirements CommunicationInteraction skills Vision and Scope Document Purposes of ValidationSoftware application knowledge Types of Requirements Find defectsBest Practices Stakeholders Prove compliance to requirementsUse iterative analysis Business Analysis Plan Test Cases and Test SuitesFocus on process improvement Iterative approach Challenges in TestingApply progressive elaboration Techniques Structured TestingCheck as you go Interviews Role of the BA in Solution Validation: the VUse the investigative approach Focus groups ModelAdopt traceability Requirements workshop: Requirements Solution Acceptance and ProjectFormalize business analysis through meeting Close-Outstandardization Requirements workshop: JAD session Role of the BA on the Enterprise AnalysisImprove communication through modeling Brainstorming TeamLife Cycle Models Observation Steps in Enterprise AnalysisWaterfall Survey Define the business needIncremental Prototype Techniques for root cause analysisAgile Document analysis Assess capability gapsEffects on business analysis Business rules analysis SWOT analysisLeadership Skills Reverse engineering Determine the solution approachProblem-Solving Skills Product trials Define the solution scopeBusiness Knowledge Using Analysis to get Stakeholder Define the business caseIT Knowledge Feedback and Verify and Validate Contents of business case

Developing Requirements Who does what?: the BA's limited role inValue of Modeling Techniques in developing a business case

line Analysis BA Necessary CompetenciesRole of the BA Modeling Techniques Analytical thinking and problem solvingStandardization and Adaptability Organizational model Behavioral characteristicsVision and Scope Document Location model Business knowledgeTypes of Requirements Process/flow models Communication skillsStakeholders Use case models Interaction skillsBusiness Analysis Plan Data models Software application knowledgeIterative approach State model Best PracticesTechniques Types of Requirements Use iterative analysisInterviews Business Rules Analysis Focus on process improvementFocus groups Prioritizing Requirements Apply progressive elaborationRequirements workshop: Requirements Verifying and Validating Requirements Check as you gomeeting Writing for Usability and Comprehension Use the investigative approachRequirements workshop: JAD session Common Requirements Document Adopt traceabilityBrainstorming Defects Formalize business analysis throughObservation Components of a Formal Requirements standardizationSurvey Document Improve communication through modelingPrototype Requirements Verification and Validation Life Cycle ModelsDocument analysis Requirements Sign-Off WaterfallBusiness rules analysis Change Management IncrementalReverse engineering Define a baseline AgileProduct trials Define a change management process Effects on business analysisUsing Analysis to get Stakeholder Feedback Identify the Change Authority Leadership Skillsand Verify and Validate Developing Traceability and Its Uses Problem-Solving SkillsRequirements Requirements Attributes Business KnowledgeValue of Modeling Techniques in Analysis Requirements Communication IT Knowledge


Modeling Techniques Purposes of ValidationOrganizational model Find defectsLocation model Prove compliance to requirements lineProcess/flow models Test Cases and Test Suites Role of the BAUse case models Challenges in Testing Standardization and AdaptabilityData models Structured Testing Vision and Scope DocumentState model Role of the BA in Solution Validation: the Types of RequirementsTypes of Requirements V Model StakeholdersBusiness Rules Analysis Solution Acceptance and Project Business Analysis PlanPrioritizing Requirements Close-Out Iterative approachVerifying and Validating Requirements Role of the BA on the Enterprise Analysis TechniquesWriting for Usability and Comprehension Team InterviewsCommon Requirements Document Defects Steps in Enterprise Analysis Focus groupsComponents of a Formal Requirements Define the business need Requirements workshop: RequirementsDocument Techniques for root cause analysis meetingRequirements Verification and Validation Assess capability gaps Requirements workshop: JAD sessionRequirements Sign-Off SWOT analysis BrainstormingChange Management Determine the solution approach ObservationDefine a baseline Define the solution scope SurveyDefine a change management process Define the business case PrototypeIdentify the Change Authority Contents of business case Document analysisTraceability and Its Uses Who does what?: the BA's limited role in Business rules analysisRequirements Attributes developing a business case Reverse engineeringRequirements Communication BA Necessary Competencies Product trialsPurposes of Validation Analytical thinking and problem solving Using Analysis to get StakeholderFind defects Behavioral characteristics Feedback and Verify and ValidateProve compliance to requirements Business knowledge Developing RequirementsTest Cases and Test Suites Communication skills Value of Modeling Techniques in AnalysisChallenges in Testing Interaction skills Modeling TechniquesStructured Testing Software application knowledge Organizational modelRole of the BA in Solution Validation: the V Best Practices Location modelModel Use iterative analysis Process/flow modelsSolution Acceptance and Project Close-Out Focus on process improvement Use case modelsRole of the BA on the Enterprise Analysis Apply progressive elaboration Data modelsTeam Check as you go State modelSteps in Enterprise Analysis Use the investigative approach Types of RequirementsDefine the business need Adopt traceability Business Rules AnalysisTechniques for root cause analysis Formalize business analysis through Prioritizing RequirementsAssess capability gaps standardization Verifying and Validating RequirementsSWOT analysis Improve communication through Writing for Usability and ComprehensionDetermine the solution approach modeling Common Requirements DocumentDefine the solution scope Life Cycle Models DefectsDefine the business case Waterfall Components of a Formal RequirementsContents of business case Incremental DocumentWho does what?: the BA's limited role in Agile Requirements Verification and Validationdeveloping a business case Effects on business analysis Requirements Sign-OffBA Necessary Competencies Leadership Skills Change ManagementAnalytical thinking and problem solving Problem-Solving Skills Define a baselineBehavioral characteristics Business Knowledge Define a change management processBusiness knowledge IT Knowledge Identify the Change AuthorityCommunication skills Traceability and Its UsesInteraction skills Requirements AttributesSoftware application knowledge line Requirements CommunicationBest Practices Role of the BA Purposes of ValidationUse iterative analysis Standardization and Adaptability Find defectsFocus on process improvement Vision and Scope Document Prove compliance to requirementsApply progressive elaboration Types of Requirements Test Cases and Test SuitesCheck as you go Stakeholders Challenges in TestingUse the investigative approach Business Analysis Plan Structured TestingAdopt traceability Iterative approach Role of the BA in Solution Validation: the VFormalize business analysis through Techniques Modelstandardization Interviews Solution Acceptance and ProjectImprove communication through modeling Focus groups Close-OutLife Cycle Models Requirements workshop: Requirements Role of the BA on the Enterprise AnalysisWaterfall meeting TeamIncremental Requirements workshop: JAD session Steps in Enterprise Analysis


Agile Brainstorming Define the business needEffects on business analysis Observation Techniques for root cause analysisLeadership Skills Survey Assess capability gapsProblem-Solving Skills Prototype SWOT analysisBusiness Knowledge Document analysis Determine the solution approachIT Knowledge Business rules analysis Define the solution scope

Reverse engineering Define the business caseProduct trials Contents of business case

line Using Analysis to get Stakeholder Who does what?: the BA's limited role inRole of the BA Feedback and Verify and Validate developing a business caseStandardization and Adaptability Developing Requirements BA Necessary CompetenciesVision and Scope Document Value of Modeling Techniques in Analytical thinking and problem solvingTypes of Requirements Analysis Behavioral characteristicsStakeholders Modeling Techniques Business knowledgeBusiness Analysis Plan Organizational model Communication skillsIterative approach Location model Interaction skillsTechniques Process/flow models Software application knowledgeInterviews Use case models Best PracticesFocus groups Data models Use iterative analysisRequirements workshop: Requirements State model Focus on process improvementmeeting Types of Requirements Apply progressive elaborationRequirements workshop: JAD session Business Rules Analysis Check as you goBrainstorming Prioritizing Requirements Use the investigative approachObservation Verifying and Validating Requirements Adopt traceabilitySurvey Writing for Usability and Comprehension Formalize business analysis throughPrototype Common Requirements Document standardizationDocument analysis Defects Improve communication through modelingBusiness rules analysis Components of a Formal Requirements Life Cycle ModelsReverse engineering Document WaterfallProduct trials Requirements Verification and Validation IncrementalUsing Analysis to get Stakeholder Feedback Requirements Sign-Off Agileand Verify and Validate Developing Change Management Effects on business analysisRequirements Define a baseline Leadership SkillsValue of Modeling Techniques in Analysis Define a change management process Problem-Solving SkillsModeling Techniques Identify the Change Authority Business KnowledgeOrganizational model Traceability and Its Uses IT KnowledgeLocation model Requirements AttributesProcess/flow models Requirements CommunicationUse case models Purposes of Validation lineData models Find defects Role of the BAState model Prove compliance to requirements Standardization and AdaptabilityTypes of Requirements Test Cases and Test Suites Vision and Scope DocumentBusiness Rules Analysis Challenges in Testing Types of RequirementsPrioritizing Requirements Structured Testing StakeholdersVerifying and Validating Requirements Role of the BA in Solution Validation: the Business Analysis PlanWriting for Usability and Comprehension V Model Iterative approachCommon Requirements Document Defects Solution Acceptance and Project TechniquesComponents of a Formal Requirements Close-Out InterviewsDocument Role of the BA on the Enterprise Analysis Focus groupsRequirements Verification and Validation Team Requirements workshop: RequirementsRequirements Sign-Off Steps in Enterprise Analysis meetingChange Management Define the business need Requirements workshop: JAD sessionDefine a baseline Techniques for root cause analysis BrainstormingDefine a change management process Assess capability gaps ObservationIdentify the Change Authority SWOT analysis SurveyTraceability and Its Uses Determine the solution approach PrototypeRequirements Attributes Define the solution scope Document analysisRequirements Communication Define the business case Business rules analysisPurposes of Validation Contents of business case Reverse engineeringFind defects Who does what?: the BA's limited role in Product trialsProve compliance to requirements developing a business case Using Analysis to get StakeholderTest Cases and Test Suites BA Necessary Competencies Feedback and Verify and ValidateChallenges in Testing Analytical thinking and problem solving Developing RequirementsStructured Testing Behavioral characteristics Value of Modeling Techniques in AnalysisRole of the BA in Solution Validation: the V Business knowledge Modeling TechniquesModel Communication skills Organizational model


Solution Acceptance and Project Close-Out Interaction skills Location modelRole of the BA on the Enterprise Analysis Software application knowledge Process/flow modelsTeam Best Practices Use case modelsSteps in Enterprise Analysis Use iterative analysis Data modelsDefine the business need Focus on process improvement State modelTechniques for root cause analysis Apply progressive elaboration Types of RequirementsAssess capability gaps Check as you go Business Rules AnalysisSWOT analysis Use the investigative approach Prioritizing RequirementsDetermine the solution approach Adopt traceability Verifying and Validating RequirementsDefine the solution scope Formalize business analysis through Writing for Usability and ComprehensionDefine the business case standardization Common Requirements DocumentContents of business case Improve communication through DefectsWho does what?: the BA's limited role in modeling Components of a Formal Requirementsdeveloping a business case Life Cycle Models DocumentBA Necessary Competencies Waterfall Requirements Verification and ValidationAnalytical thinking and problem solving Incremental Requirements Sign-OffBehavioral characteristics Agile Change ManagementBusiness knowledge Effects on business analysis Define a baselineCommunication skills Leadership Skills Define a change management processInteraction skills Problem-Solving Skills Identify the Change AuthoritySoftware application knowledge Business Knowledge Traceability and Its UsesBest Practices IT Knowledge Requirements AttributesUse iterative analysis Requirements CommunicationFocus on process improvement Purposes of ValidationApply progressive elaboration line Find defectsCheck as you go Role of the BA Prove compliance to requirementsUse the investigative approach Standardization and Adaptability Test Cases and Test SuitesAdopt traceability Vision and Scope Document Challenges in TestingFormalize business analysis through Types of Requirements Structured Testingstandardization Stakeholders Role of the BA in Solution Validation: the VImprove communication through modeling Business Analysis Plan ModelLife Cycle Models Iterative approach Solution Acceptance and ProjectWaterfall Techniques Close-OutIncremental Interviews Role of the BA on the Enterprise AnalysisAgile Focus groups TeamEffects on business analysis Requirements workshop: Requirements Steps in Enterprise AnalysisLeadership Skills meeting Define the business needProblem-Solving Skills Requirements workshop: JAD session Techniques for root cause analysisBusiness Knowledge Brainstorming Assess capability gapsIT Knowledge Observation SWOT analysis

Survey Determine the solution approachPrototype Define the solution scope

line Document analysis Define the business caseRole of the BA Business rules analysis Contents of business caseStandardization and Adaptability Reverse engineering Who does what?: the BA's limited role inVision and Scope Document Product trials developing a business caseTypes of Requirements Using Analysis to get Stakeholder BA Necessary CompetenciesStakeholders Feedback and Verify and Validate Analytical thinking and problem solvingBusiness Analysis Plan Developing Requirements Behavioral characteristicsIterative approach Value of Modeling Techniques in Business knowledgeTechniques Analysis Communication skillsInterviews Modeling Techniques Interaction skillsFocus groups Organizational model Software application knowledgeRequirements workshop: Requirements Location model Best Practicesmeeting Process/flow models Use iterative analysisRequirements workshop: JAD session Use case models Focus on process improvementBrainstorming Data models Apply progressive elaborationObservation State model Check as you goSurvey Types of Requirements Use the investigative approachPrototype Business Rules Analysis Adopt traceabilityDocument analysis Prioritizing Requirements Formalize business analysis throughBusiness rules analysis Verifying and Validating Requirements standardizationReverse engineering Writing for Usability and Comprehension Improve communication through modelingProduct trials Common Requirements Document Life Cycle ModelsUsing Analysis to get Stakeholder Feedback Defects Waterfalland Verify and Validate Developing Components of a Formal Requirements Incremental


Requirements Document AgileValue of Modeling Techniques in Analysis Requirements Verification and Validation Effects on business analysisModeling Techniques Requirements Sign-Off Leadership SkillsOrganizational model Change Management Problem-Solving SkillsLocation model Define a baseline Business KnowledgeProcess/flow models Define a change management process IT KnowledgeUse case models Identify the Change AuthorityData models Traceability and Its Uses 10. BA FundamentalsState model Requirements Attributes lineTypes of Requirements Requirements Communication Communication SkillsBusiness Rules Analysis Purposes of ValidationPrioritizing Requirements Find defectsVerifying and Validating Requirements Prove compliance to requirements lineWriting for Usability and Comprehension Test Cases and Test Suites Role of the BACommon Requirements Document Defects Challenges in Testing Standardization and AdaptabilityComponents of a Formal Requirements Structured Testing Vision and Scope DocumentDocument Role of the BA in Solution Validation: the Types of RequirementsRequirements Verification and Validation V Model StakeholdersRequirements Sign-Off Solution Acceptance and Project Business Analysis PlanChange Management Close-Out Iterative approachDefine a baseline Role of the BA on the Enterprise Analysis TechniquesDefine a change management process Team InterviewsIdentify the Change Authority Steps in Enterprise Analysis Focus groupsTraceability and Its Uses Define the business need Requirements workshop: RequirementsRequirements Attributes Techniques for root cause analysis meetingRequirements Communication Assess capability gaps Requirements workshop: JAD sessionPurposes of Validation SWOT analysis BrainstormingFind defects Determine the solution approach ObservationProve compliance to requirements Define the solution scope SurveyTest Cases and Test Suites Define the business case PrototypeChallenges in Testing Contents of business case Document analysisStructured Testing Who does what?: the BA's limited role in Business rules analysisRole of the BA in Solution Validation: the V developing a business case Reverse engineeringModel BA Necessary Competencies Product trialsSolution Acceptance and Project Close-Out Analytical thinking and problem solving Using Analysis to get StakeholderRole of the BA on the Enterprise Analysis Behavioral characteristics Feedback and Verify and ValidateTeam Business knowledge Developing RequirementsSteps in Enterprise Analysis Communication skills Value of Modeling Techniques in AnalysisDefine the business need Interaction skills Modeling TechniquesTechniques for root cause analysis Software application knowledge Organizational modelAssess capability gaps Best Practices Location modelSWOT analysis Use iterative analysis Process/flow modelsDetermine the solution approach Focus on process improvement Use case modelsDefine the solution scope Apply progressive elaboration Data modelsDefine the business case Check as you go State modelContents of business case Use the investigative approach Types of RequirementsWho does what?: the BA's limited role in Adopt traceability Business Rules Analysisdeveloping a business case Formalize business analysis through Prioritizing RequirementsBA Necessary Competencies standardization Verifying and Validating RequirementsAnalytical thinking and problem solving Improve communication through Writing for Usability and ComprehensionBehavioral characteristics modeling Common Requirements DocumentBusiness knowledge Life Cycle Models DefectsCommunication skills Waterfall Components of a Formal RequirementsInteraction skills Incremental DocumentSoftware application knowledge Agile Requirements Verification and ValidationBest Practices Effects on business analysis Requirements Sign-OffUse iterative analysis Leadership Skills Change ManagementFocus on process improvement Problem-Solving Skills Define a baselineApply progressive elaboration Business Knowledge Define a change management processCheck as you go IT Knowledge Identify the Change AuthorityUse the investigative approach Traceability and Its UsesAdopt traceability Requirements AttributesFormalize business analysis through line Requirements Communicationstandardization Role of the BA Purposes of ValidationImprove communication through modeling Standardization and Adaptability Find defectsLife Cycle Models Vision and Scope Document Prove compliance to requirements


Waterfall Types of Requirements Test Cases and Test SuitesIncremental Stakeholders Challenges in TestingAgile Business Analysis Plan Structured TestingEffects on business analysis Iterative approach Role of the BA in Solution Validation: the VLeadership Skills Techniques ModelProblem-Solving Skills Interviews Solution Acceptance and ProjectBusiness Knowledge Focus groups Close-OutIT Knowledge Requirements workshop: Requirements Role of the BA on the Enterprise Analysis

meeting TeamRequirements workshop: JAD session Steps in Enterprise Analysis

line Brainstorming Define the business needRole of the BA Observation Techniques for root cause analysisStandardization and Adaptability Survey Assess capability gapsVision and Scope Document Prototype SWOT analysisTypes of Requirements Document analysis Determine the solution approachStakeholders Business rules analysis Define the solution scopeBusiness Analysis Plan Reverse engineering Define the business caseIterative approach Product trials Contents of business caseTechniques Using Analysis to get Stakeholder Who does what?: the BA's limited role inInterviews Feedback and Verify and Validate developing a business caseFocus groups Developing Requirements BA Necessary CompetenciesRequirements workshop: Requirements Value of Modeling Techniques in Analytical thinking and problem solvingmeeting Analysis Behavioral characteristicsRequirements workshop: JAD session Modeling Techniques Business knowledgeBrainstorming Organizational model Communication skillsObservation Location model Interaction skillsSurvey Process/flow models Software application knowledgePrototype Use case models Best PracticesDocument analysis Data models Use iterative analysisBusiness rules analysis State model Focus on process improvementReverse engineering Types of Requirements Apply progressive elaborationProduct trials Business Rules Analysis Check as you goUsing Analysis to get Stakeholder Feedback Prioritizing Requirements Use the investigative approachand Verify and Validate Developing Verifying and Validating Requirements Adopt traceabilityRequirements Writing for Usability and Comprehension Formalize business analysis throughValue of Modeling Techniques in Analysis Common Requirements Document standardizationModeling Techniques Defects Improve communication through modelingOrganizational model Components of a Formal Requirements Life Cycle ModelsLocation model Document WaterfallProcess/flow models Requirements Verification and Validation IncrementalUse case models Requirements Sign-Off AgileData models Change Management Effects on business analysisState model Define a baseline Leadership SkillsTypes of Requirements Define a change management process Problem-Solving SkillsBusiness Rules Analysis Identify the Change Authority Business KnowledgePrioritizing Requirements Traceability and Its Uses IT KnowledgeVerifying and Validating Requirements Requirements AttributesWriting for Usability and Comprehension Requirements CommunicationCommon Requirements Document Defects Purposes of Validation lineComponents of a Formal Requirements Find defects Role of the BADocument Prove compliance to requirements Standardization and AdaptabilityRequirements Verification and Validation Test Cases and Test Suites Vision and Scope DocumentRequirements Sign-Off Challenges in Testing Types of RequirementsChange Management Structured Testing StakeholdersDefine a baseline Role of the BA in Solution Validation: the Business Analysis PlanDefine a change management process V Model Iterative approachIdentify the Change Authority Solution Acceptance and Project TechniquesTraceability and Its Uses Close-Out InterviewsRequirements Attributes Role of the BA on the Enterprise Analysis Focus groupsRequirements Communication Team Requirements workshop: RequirementsPurposes of Validation Steps in Enterprise Analysis meetingFind defects Define the business need Requirements workshop: JAD sessionProve compliance to requirements Techniques for root cause analysis BrainstormingTest Cases and Test Suites Assess capability gaps ObservationChallenges in Testing SWOT analysis SurveyStructured Testing Determine the solution approach Prototype


Role of the BA in Solution Validation: the V Define the solution scope Document analysisModel Define the business case Business rules analysisSolution Acceptance and Project Close-Out Contents of business case Reverse engineeringRole of the BA on the Enterprise Analysis Who does what?: the BA's limited role in Product trialsTeam developing a business case Using Analysis to get StakeholderSteps in Enterprise Analysis BA Necessary Competencies Feedback and Verify and ValidateDefine the business need Analytical thinking and problem solving Developing RequirementsTechniques for root cause analysis Behavioral characteristics Value of Modeling Techniques in AnalysisAssess capability gaps Business knowledge Modeling TechniquesSWOT analysis Communication skills Organizational modelDetermine the solution approach Interaction skills Location modelDefine the solution scope Software application knowledge Process/flow modelsDefine the business case Best Practices Use case modelsContents of business case Use iterative analysis Data modelsWho does what?: the BA's limited role in Focus on process improvement State modeldeveloping a business case Apply progressive elaboration Types of RequirementsBA Necessary Competencies Check as you go Business Rules AnalysisAnalytical thinking and problem solving Use the investigative approach Prioritizing RequirementsBehavioral characteristics Adopt traceability Verifying and Validating RequirementsBusiness knowledge Formalize business analysis through Writing for Usability and ComprehensionCommunication skills standardization Common Requirements DocumentInteraction skills Improve communication through DefectsSoftware application knowledge modeling Components of a Formal RequirementsBest Practices Life Cycle Models DocumentUse iterative analysis Waterfall Requirements Verification and ValidationFocus on process improvement Incremental Requirements Sign-OffApply progressive elaboration Agile Change ManagementCheck as you go Effects on business analysis Define a baselineUse the investigative approach Leadership Skills Define a change management processAdopt traceability Problem-Solving Skills Identify the Change AuthorityFormalize business analysis through Business Knowledge Traceability and Its Usesstandardization IT Knowledge Requirements AttributesImprove communication through modeling Requirements CommunicationLife Cycle Models 8. Enterprise Analysis Purposes of ValidationWaterfall line Find defectsIncremental Definition and Causes Prove compliance to requirementsAgile Test Cases and Test SuitesEffects on business analysis Challenges in TestingLeadership Skills line Structured TestingProblem-Solving Skills Role of the BA Role of the BA in Solution Validation: the VBusiness Knowledge Standardization and Adaptability ModelIT Knowledge Vision and Scope Document Solution Acceptance and Project

Types of Requirements Close-OutStakeholders Role of the BA on the Enterprise Analysis

line Business Analysis Plan TeamRole of the BA Iterative approach Steps in Enterprise AnalysisStandardization and Adaptability Techniques Define the business needVision and Scope Document Interviews Techniques for root cause analysisTypes of Requirements Focus groups Assess capability gapsStakeholders Requirements workshop: Requirements SWOT analysisBusiness Analysis Plan meeting Determine the solution approachIterative approach Requirements workshop: JAD session Define the solution scopeTechniques Brainstorming Define the business caseInterviews Observation Contents of business caseFocus groups Survey Who does what?: the BA's limited role inRequirements workshop: Requirements Prototype developing a business casemeeting Document analysis BA Necessary CompetenciesRequirements workshop: JAD session Business rules analysis Analytical thinking and problem solvingBrainstorming Reverse engineering Behavioral characteristicsObservation Product trials Business knowledgeSurvey Using Analysis to get Stakeholder Communication skillsPrototype Feedback and Verify and Validate Interaction skillsDocument analysis Developing Requirements Software application knowledgeBusiness rules analysis Value of Modeling Techniques in Best PracticesReverse engineering Analysis Use iterative analysisProduct trials Modeling Techniques Focus on process improvement


Using Analysis to get Stakeholder Feedback Organizational model Apply progressive elaborationand Verify and Validate Developing Location model Check as you goRequirements Process/flow models Use the investigative approachValue of Modeling Techniques in Analysis Use case models Adopt traceabilityModeling Techniques Data models Formalize business analysis throughOrganizational model State model standardizationLocation model Types of Requirements Improve communication through modelingProcess/flow models Business Rules Analysis Life Cycle ModelsUse case models Prioritizing Requirements WaterfallData models Verifying and Validating Requirements IncrementalState model Writing for Usability and Comprehension AgileTypes of Requirements Common Requirements Document Effects on business analysisBusiness Rules Analysis Defects Leadership SkillsPrioritizing Requirements Components of a Formal Requirements Problem-Solving SkillsVerifying and Validating Requirements Document Business KnowledgeWriting for Usability and Comprehension Requirements Verification and Validation IT KnowledgeCommon Requirements Document Defects Requirements Sign-OffComponents of a Formal Requirements Change ManagementDocument Define a baseline lineRequirements Verification and Validation Define a change management process Role of the BARequirements Sign-Off Identify the Change Authority Standardization and AdaptabilityChange Management Traceability and Its Uses Vision and Scope DocumentDefine a baseline Requirements Attributes Types of RequirementsDefine a change management process Requirements Communication StakeholdersIdentify the Change Authority Purposes of Validation Business Analysis PlanTraceability and Its Uses Find defects Iterative approachRequirements Attributes Prove compliance to requirements TechniquesRequirements Communication Test Cases and Test Suites InterviewsPurposes of Validation Challenges in Testing Focus groupsFind defects Structured Testing Requirements workshop: RequirementsProve compliance to requirements Role of the BA in Solution Validation: the meetingTest Cases and Test Suites V Model Requirements workshop: JAD sessionChallenges in Testing Solution Acceptance and Project BrainstormingStructured Testing Close-Out ObservationRole of the BA in Solution Validation: the V Role of the BA on the Enterprise Analysis SurveyModel Team PrototypeSolution Acceptance and Project Close-Out Steps in Enterprise Analysis Document analysisRole of the BA on the Enterprise Analysis Define the business need Business rules analysisTeam Techniques for root cause analysis Reverse engineeringSteps in Enterprise Analysis Assess capability gaps Product trialsDefine the business need SWOT analysis Using Analysis to get StakeholderTechniques for root cause analysis Determine the solution approach Feedback and Verify and ValidateAssess capability gaps Define the solution scope Developing RequirementsSWOT analysis Define the business case Value of Modeling Techniques in AnalysisDetermine the solution approach Contents of business case Modeling TechniquesDefine the solution scope Who does what?: the BA's limited role in Organizational modelDefine the business case developing a business case Location modelContents of business case BA Necessary Competencies Process/flow modelsWho does what?: the BA's limited role in Analytical thinking and problem solving Use case modelsdeveloping a business case Behavioral characteristics Data modelsBA Necessary Competencies Business knowledge State modelAnalytical thinking and problem solving Communication skills Types of RequirementsBehavioral characteristics Interaction skills Business Rules AnalysisBusiness knowledge Software application knowledge Prioritizing RequirementsCommunication skills Best Practices Verifying and Validating RequirementsInteraction skills Use iterative analysis Writing for Usability and ComprehensionSoftware application knowledge Focus on process improvement Common Requirements DocumentBest Practices Apply progressive elaboration DefectsUse iterative analysis Check as you go Components of a Formal RequirementsFocus on process improvement Use the investigative approach DocumentApply progressive elaboration Adopt traceability Requirements Verification and ValidationCheck as you go Formalize business analysis through Requirements Sign-OffUse the investigative approach standardization Change ManagementAdopt traceability Improve communication through Define a baselineFormalize business analysis through modeling Define a change management processstandardization Life Cycle Models Identify the Change Authority


Improve communication through modeling Waterfall Traceability and Its UsesLife Cycle Models Incremental Requirements AttributesWaterfall Agile Requirements CommunicationIncremental Effects on business analysis Purposes of ValidationAgile Leadership Skills Find defectsEffects on business analysis Problem-Solving Skills Prove compliance to requirementsLeadership Skills Business Knowledge Test Cases and Test SuitesProblem-Solving Skills IT Knowledge Challenges in TestingBusiness Knowledge Structured TestingIT Knowledge Role of the BA in Solution Validation: the V

line ModelRole of the BA Solution Acceptance and Project

line Standardization and Adaptability Close-OutRole of the BA Vision and Scope Document Role of the BA on the Enterprise AnalysisStandardization and Adaptability Types of Requirements TeamVision and Scope Document Stakeholders Steps in Enterprise AnalysisTypes of Requirements Business Analysis Plan Define the business needStakeholders Iterative approach Techniques for root cause analysisBusiness Analysis Plan Techniques Assess capability gapsIterative approach Interviews SWOT analysisTechniques Focus groups Determine the solution approachInterviews Requirements workshop: Requirements Define the solution scopeFocus groups meeting Define the business caseRequirements workshop: Requirements Requirements workshop: JAD session Contents of business casemeeting Brainstorming Who does what?: the BA's limited role inRequirements workshop: JAD session Observation developing a business caseBrainstorming Survey BA Necessary CompetenciesObservation Prototype Analytical thinking and problem solvingSurvey Document analysis Behavioral characteristicsPrototype Business rules analysis Business knowledgeDocument analysis Reverse engineering Communication skillsBusiness rules analysis Product trials Interaction skillsReverse engineering Using Analysis to get Stakeholder Software application knowledgeProduct trials Feedback and Verify and Validate Best PracticesUsing Analysis to get Stakeholder Feedback Developing Requirements Use iterative analysisand Verify and Validate Developing Value of Modeling Techniques in Focus on process improvementRequirements Analysis Apply progressive elaborationValue of Modeling Techniques in Analysis Modeling Techniques Check as you goModeling Techniques Organizational model Use the investigative approachOrganizational model Location model Adopt traceabilityLocation model Process/flow models Formalize business analysis throughProcess/flow models Use case models standardizationUse case models Data models Improve communication through modelingData models State model Life Cycle ModelsState model Types of Requirements WaterfallTypes of Requirements Business Rules Analysis IncrementalBusiness Rules Analysis Prioritizing Requirements AgilePrioritizing Requirements Verifying and Validating Requirements Effects on business analysisVerifying and Validating Requirements Writing for Usability and Comprehension Leadership SkillsWriting for Usability and Comprehension Common Requirements Document Problem-Solving SkillsCommon Requirements Document Defects Defects Business KnowledgeComponents of a Formal Requirements Components of a Formal Requirements IT KnowledgeDocument DocumentRequirements Verification and Validation Requirements Verification and ValidationRequirements Sign-Off Requirements Sign-Off lineChange Management Change Management Role of the BADefine a baseline Define a baseline Standardization and AdaptabilityDefine a change management process Define a change management process Vision and Scope DocumentIdentify the Change Authority Identify the Change Authority Types of RequirementsTraceability and Its Uses Traceability and Its Uses StakeholdersRequirements Attributes Requirements Attributes Business Analysis PlanRequirements Communication Requirements Communication Iterative approachPurposes of Validation Purposes of Validation TechniquesFind defects Find defects InterviewsProve compliance to requirements Prove compliance to requirements Focus groupsTest Cases and Test Suites Test Cases and Test Suites Requirements workshop: Requirements


Challenges in Testing Challenges in Testing meetingStructured Testing Structured Testing Requirements workshop: JAD sessionRole of the BA in Solution Validation: the V Role of the BA in Solution Validation: the BrainstormingModel V Model ObservationSolution Acceptance and Project Close-Out Solution Acceptance and Project SurveyRole of the BA on the Enterprise Analysis Close-Out PrototypeTeam Role of the BA on the Enterprise Analysis Document analysisSteps in Enterprise Analysis Team Business rules analysisDefine the business need Steps in Enterprise Analysis Reverse engineeringTechniques for root cause analysis Define the business need Product trialsAssess capability gaps Techniques for root cause analysis Using Analysis to get StakeholderSWOT analysis Assess capability gaps Feedback and Verify and ValidateDetermine the solution approach SWOT analysis Developing RequirementsDefine the solution scope Determine the solution approach Value of Modeling Techniques in AnalysisDefine the business case Define the solution scope Modeling TechniquesContents of business case Define the business case Organizational modelWho does what?: the BA's limited role in Contents of business case Location modeldeveloping a business case Who does what?: the BA's limited role in Process/flow modelsBA Necessary Competencies developing a business case Use case modelsAnalytical thinking and problem solving BA Necessary Competencies Data modelsBehavioral characteristics Analytical thinking and problem solving State modelBusiness knowledge Behavioral characteristics Types of RequirementsCommunication skills Business knowledge Business Rules AnalysisInteraction skills Communication skills Prioritizing RequirementsSoftware application knowledge Interaction skills Verifying and Validating RequirementsBest Practices Software application knowledge Writing for Usability and ComprehensionUse iterative analysis Best Practices Common Requirements DocumentFocus on process improvement Use iterative analysis DefectsApply progressive elaboration Focus on process improvement Components of a Formal RequirementsCheck as you go Apply progressive elaboration DocumentUse the investigative approach Check as you go Requirements Verification and ValidationAdopt traceability Use the investigative approach Requirements Sign-OffFormalize business analysis through Adopt traceability Change Managementstandardization Formalize business analysis through Define a baselineImprove communication through modeling standardization Define a change management processLife Cycle Models Improve communication through Identify the Change AuthorityWaterfall modeling Traceability and Its UsesIncremental Life Cycle Models Requirements AttributesAgile Waterfall Requirements CommunicationEffects on business analysis Incremental Purposes of ValidationLeadership Skills Agile Find defectsProblem-Solving Skills Effects on business analysis Prove compliance to requirementsBusiness Knowledge Leadership Skills Test Cases and Test SuitesIT Knowledge Problem-Solving Skills Challenges in Testing

Business Knowledge Structured TestingIT Knowledge Role of the BA in Solution Validation: the V

ModelSolution Acceptance and Project

line Close-OutRole of the BA Role of the BA on the Enterprise AnalysisStandardization and Adaptability TeamVision and Scope Document Steps in Enterprise AnalysisTypes of Requirements Define the business needStakeholders Techniques for root cause analysisBusiness Analysis Plan Assess capability gapsIterative approach SWOT analysisTechniques Determine the solution approachInterviews Define the solution scopeFocus groups Define the business caseRequirements workshop: Requirements Contents of business casemeeting Who does what?: the BA's limited role inRequirements workshop: JAD session developing a business caseBrainstorming BA Necessary CompetenciesObservation Analytical thinking and problem solvingSurvey Behavioral characteristicsPrototype Business knowledge


Document analysis Communication skillsBusiness rules analysis Interaction skillsReverse engineering Software application knowledgeProduct trials Best PracticesUsing Analysis to get Stakeholder Use iterative analysisFeedback and Verify and Validate Focus on process improvementDeveloping Requirements Apply progressive elaborationValue of Modeling Techniques in Check as you goAnalysis Use the investigative approachModeling Techniques Adopt traceabilityOrganizational model Formalize business analysis throughLocation model standardizationProcess/flow models Improve communication through modelingUse case models Life Cycle ModelsData models WaterfallState model IncrementalTypes of Requirements AgileBusiness Rules Analysis Effects on business analysisPrioritizing Requirements Leadership SkillsVerifying and Validating Requirements Problem-Solving SkillsWriting for Usability and Comprehension Business KnowledgeCommon Requirements Document IT KnowledgeDefectsComponents of a Formal Requirements 11. Case StudiesDocument lineRequirements Verification and ValidationRequirements Sign-Off 12. ExercisesChange Management lineDefine a baselineDefine a change management processIdentify the Change AuthorityTraceability and Its UsesRequirements AttributesRequirements CommunicationPurposes of ValidationFind defectsProve compliance to requirementsTest Cases and Test SuitesChallenges in TestingStructured TestingRole of the BA in Solution Validation: theV ModelSolution Acceptance and ProjectClose-OutRole of the BA on the Enterprise AnalysisTeamSteps in Enterprise AnalysisDefine the business needTechniques for root cause analysisAssess capability gapsSWOT analysisDetermine the solution approachDefine the solution scopeDefine the business caseContents of business caseWho does what?: the BA's limited role indeveloping a business caseBA Necessary CompetenciesAnalytical thinking and problem solvingBehavioral characteristicsBusiness knowledgeCommunication skillsInteraction skillsSoftware application knowledgeBest PracticesUse iterative analysis


Focus on process improvementApply progressive elaborationCheck as you goUse the investigative approachAdopt traceabilityFormalize business analysis throughstandardizationImprove communication throughmodelingLife Cycle ModelsWaterfallIncrementalAgileEffects on business analysisLeadership SkillsProblem-Solving SkillsBusiness KnowledgeIT Knowledge

Nadere informatie:

Neem voor nadere informatie of boekingen contact op met onze Customer Service Desk 030 - 60 89 444

[email protected]

www.globalknowledge.com/nl-nl/

Iepenhoeve 5, 3438 MR Nieuwegein

http://www.globalknowledge.com/nl-nl/

Business Analysis: Essentialsstore.globalknowledge.net/course-overviews/NL/GK2919.pdfbrede kijk op...

Documents

Transcript of Business Analysis: Essentialsstore.globalknowledge.net/course-overviews/NL/GK2919.pdfbrede kijk op...