Sheet1IntroductionKey ConceptsKnowledge AreasTasksPurposeDescriptionInputsElementsGuidelines/ToolsTechniquesStakeholdersOutputsUnderlying CompetenciesTechniquesPerspectivesBusiness Analysis Key ConceptsThe Business Analysis Core Concept ModelChangeNeedSolutionStakeholderValueContextKey TermsBusiness AnalysisBusiness Analysis InformationDesignEnterpriseOrganizationPlanRequirementRiskRequirements Classification SchemaBusiness requirements:Stakeholder requirements:Solution requirementsfunctional requirements:non-functional requirementsTransition requirementsStakeholdersRequirements and Designs

BA Planning and MonitoringS.NoTasksPurposeDescriptionInputElementsTechniquesStakeholdersOutput1Plan Business Analysis Approachhow to select an approach to performing business analysis, which stakeholders need to be involved in the decision, who will be consulted regarding and informed of the approach, and the rationale for using itWaterfall approach , agile techniquesUnderstand needs and objectives of OrganizationBusiness NeedExpert JudgmentOrganizational Process AssetsPlan-driven approachesChange-driven approaches

Timing of Business Analysis WorkFormality And Level Of Detail Of Business Analysis DeliverablesRequirements PrioritizationChange ManagementBusiness Analysis Planning ProcessCommunication With StakeholdersRequirements Analysis and Management ToolsProject ComplexityDecision AnalysisProcess ModelingStructured WalkthroughCustomer, Domain SME, End User or SupplierImplementation SMEProject ManagerTesterRegulatorSponsorBusiness Analysis Approach

2Conduct Stakeholder Analysisidentification of stakeholders who may be affected by a proposed initiative or who share a common business need, identifying appropriate stakeholders for the project or project phase, determining stakeholder influence and/or authority regarding the approval of project deliverables.Stakeholders may be grouped into categories that reflect their involvement or interest in the initiativeBusiness NeedEnterprise ArchitectureOrganizational Process AssetsIdentificationComplexity of Stakeholder Group- Number and variety of direct end users- Number of interfacing business processes and automated systemsAttitude and InfluenceAttitude towards The business goals, objectives, and solution approachAttitude towards business analysis:Attitude towards collaboration:Attitude towards the sponsor:Attitude towards team members

Influence on the project.Influence in the organization.Influence needed for the good of the project.Influence with other stakeholders.

Authority Levels For Business Analysis WorkGeneral TechniquesAcceptance and Evaluation Criteria DefinitionBrainstormingInterviewsOrganization ModelingProcess ModelingRequirements WorkshopsRisk AnalysisScenarios and Use Cases and User StoriesScope ModelingSurvey/QuestionnaireRACI MatrixResponsibleAccountableConsultedInformedStakeholder MapMatrix MappingOnion DiagramDomain SMEImplementation SMEProject ManagerTesterRegulatorSponsorStakeholder List, Roles, and Responsibilities

3Plan BA ActivitiesDetermine the activities that must be performedDeliverables that must be produced, Estimate the effort required to perform that work, Identify the management tools required to measure the progress of those activities and deliverablesIdentify business analysis deliverablesDetermine the scope of work for the business analysis activitiesDetermine which activities the business analyst will perform and whenDevelop estimates for business analysis workBusiness Analysis ApproachBusiness Analysis Performance AssessmentOrganizational Process AssetsStakeholder List, Roles, and ResponsibilitiesGeographic Distribution of StakeholdersCollocatedDispersedType of Project or InitiativeFeasibility studiesProcess improvementNew software development (in-house)Software package selectionBusiness Analysis DeliverablesInterviews or facilitated sessions with key stakeholdersReview project documentationReview organizational process assetsDetermine Business Analysis ActivitiesWBS - Work Breakdown StructureActivity list - Unique Number - Activity DescriptionAssumptionsDependenciesMilestonesEstimationFunctional DecompositionRisk AnalysisCustomer, Domain SME, End User, and Supplier:Implementation SME:Operational Support:Project Manager:TesterSponsorBusiness Analysis Plan(s)

4Plan BA Communicationdescribes the proposed structure schedule for communications regarding business analysis activities. Record and organize the activities to provide a basis for setting expectations for business analysis work, meetings, walkthroughs, and other communications.how best to receive, distribute, access, update, and escalate information from project stakeholders, and determining how best to communicate with each stakeholder.Business Analysis ApproachBusiness Analysis Plan(s)Organizational Process AssetsStakeholder List, Roles, and ResponsibilitiesGeographyCultureRelationship to timeRelationship to task completionRelationship to contractsRelationship to formal and informal authorityProject TypeA new, customized in-house software development projectUpgrading the technology or infrastructure of a current systemChange in a business process or new data for an existing applicationPurchase of a software packageShort, focused, agile style iterations of software developmentCommunication FrequencyCommunications FormalityStructured WalkthroughCustomer and SupplierDomain SMEEnd UserImplementation SMEOperational SupportProject ManagerTesterRegulatorSponsorBusiness Analysis Communication Plan

5Plan Requirement Management ProcessApprove requirements for implementation and manage changes to the solution or requirements scopeDetermining the process for requirements change, which stakeholders need to approve change, who will be consulted or informed of changes, and by extension, who does not need to be involved. Assessing the need for requirements traceability and determining which requirements attributes will be captured.Business Analysis ApproachBusiness Analysis PlanOrganizational Process AssetsRepositoryTraceabilitySelect Requirements Attributes - Absolute reference - Author of the requirement - Complexity - Ownership - Priority - Risks - Source of the requirement - Stability - Status - Urgency - cost, resource assignment, and revision number, traced-from and traced-toRequirements Prioritization Process - Formality - Establishing The Process AndTechnique - Plan The ParticipationChange Management - Determine the process for requesting changes - Determine who will authorize changes - Impact Analysis - Plan the wording of the request - Cost and time estimates of change - Benefits and risks of the change - Recommended course of action for change - Coordinate Prioritization Of Change - Change-Driven Methods - Tailoring the Requirements Management Process - Organizational culture - Stakeholder preferences - Complexity of project, project phase, or product (product, service, or result) being delivered. - Organizational maturity - Availability of resourcesDecision Analysis Problem TrackingRisk AnalysisDomain SMEEnd UserImplementation SMEOperational SupportProject ManagerTesterSponsorRequirements Management Plan

6Manage BA Performancemanage the performance of business analysis activities to ensure that they are executed as effectively as possibledetermining which metrics will be used to measure the work performed by the business analysthow to track, assess, and report on the quality of the work and take steps to correct any problemshow organizational process assets governing business analysis activities are managed and updatedBusiness Analysis Performance MetricsBusiness Analysis PlanOrganizational Performance StandardsRequirements Management PlanPerformance MeasuresPerformance ReportingPreventive And Corrective ActionGeneral TechniquesInterviewsLessons Learned ProcessMetrics and Key Performance IndicatorsProblem TrackingProcess ModelingRoot Cause AnalysisSurvey/QuestionnaireVariance AnalysisDomain SME and End UserImplementation SME, Operational Support, and TesterProject ManagerSponsorBusiness Analysis Performance AssessmentBusiness Analysis Process Assets

Enterprise AnalysisS.NoTasksPurposeDescriptionInputElementsTechniquesStakeholdersOutput1Define Business Needwhy a change to organizational systems or capabilities is requiredFrom the top downFrom the bottom upFrom middle managementFrom external driversBusiness Goals and ObjectivesRequirements [Stated]Business Goals and ObjectivesS - SpecificM - MeasurableA - AchievableR - RelevantT - Time-boundedBusiness Problem or OpportunityAdverse ImpactsExpected BenefitsQuickness of problem resolvedSource of ProblemDesired Outcomeshould address problem or opportunityBenchmarkingBrainstormingBusiness Rules AnalysisFocus GroupsFunctional DecompositionRoot Cause AnalysisCustomer or SupplierDomain SME and End UserImplementation SMERegulatorSponsorBusiness Need

2Assess Capability GapsTo identify new capabilities required by the enterprise to meet the business needBusiness NeedEnterprise ArchitectureSolution Performance AssessmentCurrent Capability AnalysisAssessment of New Capability RequirementsAssumptionsDocument AnalysisSWOT AnalysisCustomer and SupplierDomain SME, End User, Implementation SME, and SponsorRequired Capabilities

3Determine Solution ApproachTo determine the most viable solution approach to meet the business need in enough detail to allow for definition of solution scope and prepare the business case.Utilize additional capabilities of existing software/hardwarePurchase or lease software/hardware from a supplierChange the business procedures/processesPartner with other organizations, or outsource work to suppliersBusiness NeedOrganizational Process AssetsRequired CapabilitiesAlternative GenerationAssumptions and ConstraintsRanking and Selection of ApproachesGeneral TechniquesBenchmarkingBrainstormingDecision AnalysisEstimationSWOT AnalysisFeasibility AnalysisCustomer, Domain SME, End User and SupplierImplementation SMESponsorSolution Approach

4Define Solution ScopeTo define which new capabilities a project or iteration will deliver.The scope of analysisThe capabilities supported by solution components,The capabilities to be supported by individual releasesThe enabling capabilitiesAssumptions and ConstraintsBusiness NeedRequired CapabilitiesSolution ApproachSolution Scope DefinitionImplementation ApproachDependenciesGeneral TechniquesFunctional DecompositionInterface AnalysisScope ModelingUser StoriesProblem or Vision StatementDomain SMEImplementation SMEProject ManagerSponsorSolution Scope

5Define Business CaseTo determine if an organization can justify the investment required to deliver a proposed solutionJustify the cost to develop the project to value it bringsAssumptions and ConstraintsBusiness NeedSolution ScopeStakeholder ConcernsBenefitsCostsRisk AssessmentResults MeasurementDecision AnalysisEstimationMetrics and Key Performance IndicatorsRisk AnalysisSWOT AnalysisVendor AssessmentSponsorDomain SMEImplementation SMEProject ManagerBusiness Case

Requirements Analysis

S.NoTasksPurposeDescriptionInputElementsTechniquesStakeholdersOutput1Prioritize RequirementsEnsures that analysis and implementation efforts focus on the most critical requirements.Determine the relative importance of requirements, based on their relative value, risk, difficulty of implementationBusiness CaseBusiness NeedRequirementsRequirements Management PlanStakeholder List, Roles, and ResponsibilitiesBasis for PrioritizationBusiness ValueBusiness or Technical RiskImplementation DifficultyLikelihood of SuccessRegulatory or Policy ComplianceRelationship to Other RequirementsStakeholder AgreementUrgencyChallengesNon-negotiable DemandsUnrealistic TradeoffsGeneral TechniquesDecision AnalysisRisk AnalysisMoSCoW AnalysisMustShouldCouldWon'tTimeboxing/BudgetingAll InAll OutSelectiveVotingDomain SMEImplementation SMEProject ManagerSponsorRequirements [Prioritized]

2Organize Requirementscreate a set of views of the requirements for the new business solution that are comprehensive, complete, consistent, and understood from all stakeholder perspectives.Understand which models are appropriate for the business domain and solution scopeIdentify model interrelationships and dependenciesOrganizational Process AssetsRequirements [Stated]Solution ScopeLevels of AbstractionModel SelectionUser Classes, Profiles, or RolesConcepts and RelationshipsEventsProcessesRulesBusiness Rules AnalysisData Flow DiagramsData ModelingFunctional DecompositionOrganization ModelingProcess ModelingScenarios and Use CasesScope ModelingUser StoriesDomain SME, End User, Implementation SME, and SponsorProject ManagerRequirements Structure

3Specify and Model Requirementsanalyze expressed stakeholder desires and/or the current state of the organization using a combination of textual statements, matrices, diagrams and formal modelsanalyze the functioning of an organization and provide insight into opportunities for improvementdevelopment and implementation of solutions, facilitating communication among stakeholders, supporting training activities and knowledge management, Ensuring compliance with contracts and regulationsRequirements [Stated]Requirements StructureTextMatrix DocumentationModels - Modeling Formats - Notations - Formal versus Informal Models - semantics and iconographyCapture Requirements AttributesImprovement Opportunities - Automate Or Simplify The Work People Perform - Improve Access To Information - Reduce Complexity Of Interfaces - Increase Consistency Of Behavior - Eliminate RedundancyGeneral TechniquesAcceptance and Evaluation Criteria Definition Business Rules AnalysisData Dictionary and Glossary Data Flow DiagramsData ModelingFunctional DecompositionInterface AnalysisMetrics and Key Performance IndicatorsNon-functional Requirements Analysis Organization Modeling Process Modeling PrototypingScenarios and Use CasesSequence DiagramsState DiagramsUser StoriesAny StakeholderRequirements [Analyzed]

4Define Assumptions and ConstraintsIdentify factors other than requirements that may affect which solutions are viableAssumptions are factors that are believed to be true, but have not been confirmed

Constraints are defined as restrictions or limitations on possible solutions.Stakeholder ConcernsAssumptionsBusiness Constraints - budgetary restrictions, - time restrictions, - limits on the number of resources available, - restrictions based on the skills of the project team and the stakeholders, - a requirement that certain stakeholders not be affected by the implementation of the solution, or any other organizational restriction.Technical ConstraintsProblem TrackingRisk AnalysisImplementation SMEProject ManagerAll StakeholdersAssumptions and Constraints

5Verify Requirementsensures that requirements specifications and models meet the necessary standard of quality to allow them to be used effectively to guide further work.ready for formal review and validation by the customers and usersprovide all the information needed for further work based on the requirements to be performedRequirements [Any Except Stated]Characteristics of Requirements Quality - Cohesive - Complete - Consistent - Correct - Feasible - Modifiable - Unambiguous - TestableVerification activitiesGeneral Techniques - Acceptance and Evaluation Criteria Definition - Problem Tracking - Structured WalkthroughChecklistsAll StakeholdersRequirements [Verified]

6Validate Requirementsensure that all requirements support the delivery of value to the business, fulfill its goals and objectives, and meet a stakeholder need.ensure that stakeholder, solution, and transition requirements align to the business requirementsBusiness CaseStakeholder, Solution, or Transition Requirements [Verified]:Identify AssumptionsDefine Measurable Evaluation CriteriaDetermine Business ValueDetermine Dependencies for Benefits RealizationEvaluate Alignment with Business Case and Opportunity CostAcceptance and Evaluation Criteria DefinitionMetrics and Key Performance IndicatorsPrototypingRisk AnalysisStructured WalkthroughAll StakeholdersRequirements [Validated]

Req Mgmt and CommunicationsS.NoTasksPurposeDescriptionInputElementsTechniquesStakeholdersOutput1Manage Solution Scope and RequirementsObtain and maintain consensus among Key stake holders over solution scope and the requirements that will be implementedSecuring apporval of requirements from authorized stake holdersManage issues during elicitation and analysis.Approval can be requested either at the end of project or during the intervals.Requirements are baselined after approval.Change Control Process - any changes after requirements baselined and it also requires approval.Solution scope determines whether the proposed requirements supports business goals and objectivesRequirements Management PlanSolution Scope - is also a requirementStakeholder List, Roles and Responsibilities.Stakeholder, solution and Transition Requirements [Communicated or Traced]Requirements Lifecycle[Stated,specified and modeled, verified, validated]Solution Scope ManagementConflict and Issue ManagementPresenting Requirements for ReviewApprovalProblem TrackingBaseliningSignoffDomain SMEImplementation SMEProject ManagerSponsorRequirements [Approved]

2Manage Requirements TraceabilityCreate and maintain relationships betweenBusiness ObjectivesRequirementssolution componentsTracing - ability to look at the requirement and others to which it is relatedForward Traceability - allocationBackward Traceability - DerivationHelps inScope mangement,Risk Management,Time Management,Cost ManagementCommunication ManagementGoal is to ensure requirements are linked back to business objectiveImpact AnalysisRequirements CoverageRequirements AllocationRequirements Requirements Management PlanRelationships - Necessity - Effort - Subset - Cover - ValueImpact AnalysisConfiguration Management SystemCoverage MatrixImplementation SMEProject ManagerTesterRequirements[Traced]

3Maintain Requirements forRe-useManage requirements knowledge after their implementationLong term usageon-going basisstored in repositoryOrganizational Process AssetRequirementsOngoing Requirements - contractual obligations - quality standards - SLA - business rules - business processessSatisfied RequirementsN/ABusiness AnalystDomain SMEImplementation SMERequirements[Maintained and Reusable]

4Prepare Requirements PackageSelect and structure requirements for -effective communication -understandable -usableClear, concise, accurate and appropriate level of detailingGoal is to convey information clearly and in understandable fashionFormal DocumentationPresentationModelsBusiness Analysis Communication PlanOrganizational Process AssetRequirementsRequirements StructureWork Product and Deliverables - Work Product - DeliverablesFormatAdditional considerations for Requirement DocumentationRequirements Documentation - Business Requirement Doc - Product Roadmap - Software/System Requirement Specification - Supplementary Requirements Specification - Vision DocumentRequirements for Vendor Selection - RFI - Request for Information - RFQ - Request for Quote - RFP - Request for ProposalEvaluation Criteria - implementation costweighting Criteria - how proposed solution meets requirementsDomain SMEs and End UsersImplementation SMEsProject ManagersRegulatorsSponsorsTestersRequirements Package

5Communicate RequirementsBringing Stakeholders to a common understanding of requirementsConversations, notes, documents and presentationsSoft skill - communicationtechnical skill - requirementBusiness Analysis Communication PlanRequirementsRequirements PackageGeneral CommunicationPresentations - Formal - InformalRequirements WorkshopStructured WalkthroughAllCommunicated Requirements

Sol Ass and ValidationS.NoTasksPurposeDescriptionInputElementsTechniquesStakeholdersOutput1Assess Proposed Solutiondetermine how closely they meet stakeholder and solution requirements.single solution or to compare multiple proposed solutions.Assumptions and ConstraintsRequirements [Prioritized and Approved]Solution OptionsRanking of Solution Options - scoring system for complex decision problemsIdentification of Additional Potential CapabilitiesAcceptance and Evaluation Criteria DefinitionDecision AnalysisVendor AssessmentDomain SMEImplementation SMEOperational SupportProject ManagerSupplierSponsorAssessment of Proposed Solution

2Allocate RequirementsAllocate stakeholder and solution requirements among solution components and releasesassessing the tradeoffs between alternatives in order to maximize benefits and minimize costs.objective of allocation is to maximize the business value.Requirements may be allocated between - organizational units, between job functions, between people and software, software application components or releases of a solutionRequirements [Prioritized and Approved]Solution [Designed]Solution ScopeSolution Components - Available resources - Constraints on the solution - Dependencies between requirementsRelease Planning - Org constraints like freeze period for implementationAcceptance and Evaluation Criteria DefinitionBusiness Rules AnalysisDecision AnalysisFunctional DecompositionProcess ModelingScenarios and Use CasesCustomers and SuppliersDomain SMEEnd UserImplementation SMEOperational SupportProject ManagerTesterSponsorRequirements [Allocated]

3Assess Organizational ReadinessAssess whether the organization is ready to make effective use of a new solution.effect a new solution will have on an organization and Organizational readinessEnterprise ArchitectureSolution ScopeSolution [Designed]Stakeholder ConcernsCultural Assessment - Assess the beliefs, attitudes and feelings, willingness common to key stakeholder groupsOperational or Technical AssessmentStakeholder Impact Analysis - Functions - Location - Tasks - ConcernsGeneral Techniques - Acceptance and Evaluation Criteria Definition - Data Flow Diagrams and Process Models - Focus Groups, Interviews and Survey/Questionnaire - Organization Modeling - Problem Tracking - Risk Analysis - SWOT AnalysisForce Field Analysis - graphical representation - identifying the forces that support and oppose a changeDomain SMEImplementation SME - Organizational Change Management SMEs - Usability SMEs - Training SMEsOperational SupportProject ManagerSponsorOrganizational Readiness Assessment

4Define Transition Requirementsdefine requirements for capabilities needed to transition from an existing solution to a new solutiontransition period (the time when both the old and new solutions are operational)enterprise may need to operate both solutions in parallelmove information between the new and old solutionconduct training to enable stakeholdersOrganizational Readiness AssessmentRequirements [Stated]Solution [Deployed] (existing)Solution [Designed]DataOngoing WorkOrganizational ChangeBusiness Rules AnalysisData Flow Diagrams ,Process Modeling Organization ModelingData ModelingCustomerDomain SMEEnd UserImplementation SMEOperational SupportProject ManagerRegulatorTesterSponsorTransition Requirements

5Validate SolutionValidate that a solution meets the business need and determine the most appropriate response to identified defects.delivered solution meets the business needs on an ongoing basisProblems will be reported and prioritized for resolutionSolution [Constructed]Requirements [Prioritized and Validated]Investigate Defective Solution OutputsAssess Defects and IssuesAcceptance and Evaluation Criteria DefinitionProblem TrackingRoot Cause AnalysisDomain SMEEnd UserImplementation SMEOperational SupportProject ManagerTesterRegulatorSponsorIdentified DefectsMitigating ActionsSolution Validation Assessment

6Evaluate Solution Performanceunderstand the value they deliver and identify opportunities for improvement.investigating how a solution is actually used after it is deployedassessing the effect (Positive and Negative)post-implementation assessmentBusiness RequirementsIdentified DefectsSolution Performance Metrics - Quantitative - QualitativeSolution [Deployed]Understand Value Delivered By Solution- actual metricsValidate Solution MetricsSolution Replacement or Elimination - Ongoing Cost versus Initial Investment - Opportunity Cost - Necessity - Sunk Cost - money already committed to initiativeDecision Analysis - Cost/benefit analysisFocus GroupsObservationSurvey/QuestionnaireCustomer, Domain SME, and SupplierEnd UserOperational SupportRegulatorSponsorSolution Performance Assessment

Sheet8

Sheet9

Sheet10

Sheet11

Sheet12

Sheet13

Sheet14

Sheet15