distinguishing between typical ba projects

• Agile
• Business intelligence
• Information technology
• Business architecture
• Business process
• Determining the role and focus of BA based on project type

identifying underlying competencies

• Recognizing behavioral and thinking paradigms
• Highlighting communication and interaction skills

describing key components

• Establishing the vocabulary
• BACCM
• Stakeholders
• Requirements
• Designs

Researching the business organization in context to new change

• Performing situational state analysis: current vs. future
• Listing the business drivers and the problem/opportunity

Understanding analytical methodologies and approaches

• Defining and analyzing potential adverse events
• Carrying out an enterprise readiness assessment
• SWOT
• KPIs
• Functional decomposition

Choosing a BA approach and establishing governance

• Predictive vs. adaptive
• Level of formality
• Timing
• Documenting and communicating requirements changes

Understanding the community of stakeholders

• Conducting a stakeholder analysis
• Communicating: details, frequency, modality
• Personas
• Rules analysis
• Organizational modeling

Preparing and conducting elicitation sessions

• Developing an elicitation activity plan
• Collaboration
• Research
• Experiments

Capturing accurate and consistent information

• Comparing elicitation results to sources
• Ensuring a shared understanding of information
• Brainstorming
• Interviews
• Stakeholder maps

Specifying and modeling requirements and designs

• Creating matrices and diagrams
• Collecting and representing attributes
• Implementing appropriate levels of abstraction
• Process modeling
• Sequence diagrams
• State modeling

Structuring and organizing requirements and designs

• Illustrating flows of inputs, information, and outputs
• Checking for correctness and completeness
• Evaluating against solution scope
• Verifying and validating specified and modeled requirements
• Use cases
• Data flow diagrams
• Non-functional analysis

Defining types and deriving relationships

• Finding relationships between requirements
• Choosing prioritization criteria and requirements states

Approving requirements and designs

• Managing conflicts and issues
• Gaining consensus and communicating approval
• Item tracking
• Workshops
• Acceptance and evaluation criteria

Determining if what was specified solves the business problem

• Recording and applying solution performance measurements
• Identifying and analyzing limitations in the solution and the enterprise

Recommending alternatives and actions to increase value

• Listing and understanding external and internal factors
• Considering solution replacement or retirement
• Decision analysis
• Organizational modeling
• Risk analysis

Foundation concepts

• Controlled Start: Business Analysis Planning and Monitoring
  • Controlled Start: Strategy Analysis

business analysis

• Duration: 5 weeks course (50 Hours)
• (2 hours daily, 5 days a week)
• Description of the Course: 5 weeks course aimed at providing training in Business Analysis.
• Prerequisite: High school diploma, TASC, GED
• Cost for Training: $1000
• Books Cost: $100 optional, student can purchase books