Please enable JavaScript.

Coggle requires JavaScript to display documents.

Business Analysis Planning and Monitoring (1.1 Plan the BA approach…

- - - - Predictive: very formal, detailed documentation of all requirements. must be approved before the start of work.
      - Adaptive: requirements gathered through interactions and feedback on work in process. High-level requirements documented only.
    - - Risks involved
      - No of business areas or systems affected
      - Size of the change
      - Technological complexities
      - geographical and cultural considerations
    - - Availability of resources
      - Priority and/or urgency of the initiative
      - Other concurrent initiatives
      - constraints such as contract terms or regulatory deadlines
    - - Predictive: most BA work should be done at first. detailed understanding before beginning is impt. Cost of change is high. Waterfall
      - Adaptive: priority requirements quick off, requirements gathering occurs iteratively. Prioritising constantly. Rapid delivery. High uncertainty. Agile methodstext
    - - Experience level of the business analyst
      - extent of domain knowledge held by the business analyst,
      - level of experience stakeholders have in communicating their needs
      - stakeholder attitudes about the change and business analysis in general
      - amount of time allocated by stakeholders to the business analysis activities
      - any pre-selected framework, methodology, tools, and/or techniques imposed by organizational policies and pracrtices
      - cultural norms of the organization
- - - - Attitudes towards the goals, BA process, the changes, team members, the sponsor and collaboration
        
        Level of power or influence: how much influence is needed to implement a change
        compared to the amount of influence the key stakeholders can bring. If there is a
        mismatch business analysts develop risk plans,
        responses and other strategies that might be needed to obtain the required level
        of support.
        
        Decision Making Authority
      - identify roles
    - - timing and frequency
      - location
      - tools
      - delivery method
      - stakeholder preferences
    - - What to be communicated
      - Audience
      - Method
      - frequency
      - When
      - Location
      - Level of details
      - Level of formality
- - - - Determine the process for requesting change
      - Determine the elements of the change request
        
        Cost and time estimaets
        
        Benefits
        
        Risks
        
        Priority
        
        Courses of action
      - Determine how changes will be prioritized
      - Determine how changes will be documented
      - Determine how changes will be communicated
      - Determine who will perform the impact analysis
      - Determine who will authorize changes
    - - Formality
      - Criteria
      - People involved
      - How to prioritize
    - - Timing and frequency
      - Process to gain approvals
      - What to be approved
      - Who will approve