Hi everybody dr white here the founder of the business analysis doctor so today we're going
to be talking about change management from the business analyst perspective but before we get
started be sure to subscribe for more training on business analysis best practices and certification
also if you like the video be sure to hit that like button alright now let's get started
Ok. According to the Guide to the Business Analysis Body of Knowledge (BABOK)
Change management is the Planned activities, tools, and techniques to address the human
side of change during a change initiative, primarily addressing the needs of the people
who will be most affected by the change. In general, the key components of change
management include Identifying changes, Document changes, Decide on changes, Track changes.
Identify changes. Identifying and selecting a change item for processes or project documents.
Document changes. Documenting the change into a proper change request.
Decide on changes. Reviewing the changes; approving, rejecting, deferring, or making
any other decision about changes to the project
documents, deliverables, or baselines. Track changes. Verifying that the changes are
registered, assessed, approved, and tracked and communicating final results to stakeholders.
From a business analyst perspective, there are two main components in change management
which includes, Governance, and Information management
Information Management related to business analysis consist of all the information
business analysis practitioners use to gather and elicit requirements, create, compile, and
disseminate documents in the course of performing business analysis or project-related activities.
Information management involves Organizing Information
Planning and Maintaining Traceability Facilitating storage and access to the information
Governance related to business analysis involves defining or enforcing
organization standards regarding how decisions are made about requirements and designs
Key activities for governance related to business analysis includes
Facilitating the decision-making process Change Controls
Requirements prioritization And Requirements and Change Approvals
Now let’s look at each of these components individually!
Decision-Making Process asks
What happens when the team can’t come to an agreement
What’s the escalation process
Who reviews decision information (RACI) Who makes the final decision (RACI)
Change Control Requirements Change Process
Who can request changes? How changes are reviewed and evaluated?
Who reviews changes (change control board)?
Who performs the impact assessment (business vs delivery)?
How changes are communicated Status meetings or email updates
Prioritization
Formality of the prioritization process Generally, the more decision making stakeholders
you have the more formal it needs to be Predictive (Waterfall) vs. Change Driven (Agile)
Prioritization Criteria Benefit,
Costs, Risk, Dependencies, Urgency, or Compliance
Who will participate in prioritization (decision-makers and SMEs)
Determining the prioritization techniques
MoSCoW, Kano Analysis, Financial Analysis, Ranking, Time Boxing
Approvals
Who is responsible for approvals (RACI) Sponsors, Product Owner, Decision-makers
BA Information that requires approval BA Plans
Requirements and Designs Change Requests
Formality of approval process
Predictive (Waterfall) vs Adaptive (Agile) Organizational Standards
Organizing Information
Who needs to access the information
What do they need to do with the information How are new and changing information managed
Types of information Types of relationships amongst the information
Traceability
Formality of the traceability approach Formality increases as the number
of requirements increase Complexity of relationships
Relationships between different requirements levels and design components
Derive (backward), Allocate (forward), Depend, Validate
Documenting and communicating requirement changes Documenting and communicating approvals
Storage and Access
What repository will be used Who needs access to the information
How often it needs to be accessed
Well there you have it folks that's my overview of change management from a business
analysis perspective. If you want more in-depth business analysis training check out all of our
business analysis certification training options via the link in the description.