 SWOT Analysis:

SWOT analysis is the most compatible technique that is used by any business analyst for
strategy analysis. It is one of the most widely used business analysis tools today. In addition, it is
simple. It is a technique for enterprise-level analysis that is not limited to business analysis. It
might be utilized at any point during the project if the unit requires it, and most people are
familiar with it.

Strengths and weaknesses are internal factors, while opportunities and threats are external
factors.
 Strengths: Strong customer base, experienced sales team.
 Weaknesses: Disjointed customer data, outdated tools.
 Opportunities: New market opportunities, advanced CRM technologies.
 Threats: Competitive pressures, data privacy regulations.
 Explanation: SWOT analysis helps identify internal and external factors that could impact the
CRM project.
 Usage for Business Analyst: A BA can use SWOT analysis to assess the feasibility of a
CRM project, identifying potential challenges and leveraging strengths to mitigate risks.
EXAMPLE
Scenario: Launching an E-commerce Platform for a Retail Company
Company: ABC Retailers, a traditional pet food shop chain, plans to launch an e-commerce
platform to expand its market reach and compete with online retail giants.
1. SWOT Analysis
Components:
 Strengths:
o Established brand reputation.
o Extensive product range.
o Loyal customer base.
 Weaknesses:
o Lack of online presence.
o Limited technical expertise.
o High operational costs.
 Opportunities:
o Growing e-commerce market.
o Technological advancements.
o Potential for global reach.
 Threats:
 o Intense competition from established e-commerce players.
o Cybersecurity risks.
o Economic downturn affecting consumer spending.
Business Analyst's Role: The BA would conduct the SWOT analysis by gathering data from
internal reports, market research, and stakeholder interviews. This analysis helps in
understanding the internal and external factors that could impact the project.

 MoSCoW (Must or Should, Could or Would)

MoSCoW analysis is a project planning technique that is used for managing requirements. The
abbreviation of MoSCoW stands for:
 Must have: Nonnegotiable product requirements that the team must have.
 Should have: Important efforts that are not necessary but bring a lot of value.
 Could have: It is nice to have projects that, if left out, will have minor influence.
 Will not have: Initiatives that are not a priority for this time frame will not be included
EXAMPLE
Components:
 Must have:
o Secure payment gateway.
o User-friendly website interface.
o Inventory management system.
 Should have:
o Customer reviews and ratings.
o Mobile app.
o Loyalty program integration.
 Could have:
o AI-driven product recommendations.
o Multi-language support.
o Augmented reality for product viewing.
 Won’t have:
o Integration with physical store POS systems (future phase).
o Advanced analytics dashboard (not in the initial release).
Business Analyst's Role: The BA would facilitate requirement gathering sessions and prioritize
the features using the MoSCoW method, ensuring the project focuses on delivering critical
functionalities first while managing stakeholder expectations.

 MOST Analysis
MOST analysis is a comprehensive business analysis framework that is widely regarded as one
of the most effective methods for determining an organization’s capability and purpose. This
method entails performing a thorough internal examination of an organization’s objectives and
how to achieve them.

The abbreviation means:

 Mission: What is the mission of an organization?
An organization’s mission should be a long-term process. The mission statement is
contributed by each department of the business. The mission establishes a general
rationale for being in business and the objectives that are to be met. The more specific a
company’s goal is, the more likely it is to succeed.
 Objectives: What are the main objectives that will assist in completing the company’s
mission?
Objectives are described as particular goals that each department must meet to fulfill the
company’s mission. For decision-making, objectives should be clever and explicit. They
must also be quantifiable and achievable.
 Strategy: What are the many alternatives for accomplishing the goals?
The activities that should be performed to achieve organizational objectives are known as
strategy. There are many different types of activities that can be undertaken to fulfill at
least one of the company’s goals or objectives. Strategy is also seen to be the safest
method to advance the company.
 Tactics: What will the organization’s tactics be for carrying out the strategy?
Tactics are used to carry out organizational strategy. They are written straightforwardly so
that anyone in the company, who is unfamiliar with MOST analysis, may understand them.
 Mission: Improve customer satisfaction.
 Objectives: Implement a CRM system.
 Strategy: Centralize data, enhance interactions.
 Tactics: Develop a plan, train staff.
 Explanation: MOST analysis ensures the CRM project aligns with strategic goals.

EXAMPLE – RETAIL SHOP in ONLINE

Components:
 Mission:
 o To become a leading e-commerce platform providing a seamless shopping experience.
 Objectives:
o Achieve 50,000 registered users in the first six months.
o Increase online sales by 20% within the first year.
o Ensure 95% customer satisfaction rate.
 Strategy:
o Develop a robust and scalable e-commerce platform.
o Implement targeted digital marketing campaigns.
o Offer competitive pricing and exclusive online deals.
 Tactics:
o Partner with a reputable e-commerce development firm.
o Launch social media advertising campaigns.
o Introduce limited-time offers and discounts.
Business Analyst's Role: The BA would work with senior management to define the mission and
objectives, and develop strategies and tactics. They would also monitor the progress and adjust
the plans as needed to ensure the objectives are met.

 CATWOE Analysis:

CATWOE analysis is business modeling analysis that is done to get a viewpoint on high-level
business operations that we would expect to see in a company that shares the stakeholders’
perspective on the world.

 Customer: Stakeholders will have various perspectives on the clients. It demonstrates the
stakeholders’ comprehension of the clients.
 Actor: These are the individuals who are in charge of the transition. They are employees
who carry out business activities for the company.
 Transformation process: This is the business system’s central business activity. This
converts input to output.
 Worldview: This is a summary of the stakeholders’ perspectives about the organization. It
explains why the organization is there and what it is supposed to do.
 Owners: This is a view of who is in charge of the organization or business process and who
has the authority to make changes.
 Environmental constraints: These are the externally imposed limitations on the
organization, which can be analyzed through PESTLE analysis.
 Customers: Sales teams, end customers.
 Actors: IT team, CRM vendor.
  Transformation: Centralized CRM system.
 Worldview: Better customer service leads to increased retention.
 Owner: Project sponsor.
 Environmental constraints: Budget, regulations.
 Explanation: CATWOE analysis provides a holistic view of the project, considering various
perspectives and constraints
EXAMPLE – RETAIL SHop
Components:
 Customers:
o Online shoppers.
o Existing store customers.
o New market segments.
 Actors:
o Development team.
o Marketing team.
o Customer support team.
 Transformation Process:
o Converting website visitors into paying customers.
 Worldview:
o The e-commerce platform will enhance customer convenience and expand market
reach.
 Owner:
o ABC Retailers’ management.
 Environmental Constraints:
o Budget limitations.
o Regulatory compliance.
o Technological infrastructure.
Business Analyst's Role: The BA would use CATWOE analysis to understand the different
elements involved in the project and ensure all perspectives are considered. This helps in
creating a comprehensive project plan that addresses the needs of all stakeholders.

 PESTLE Analysis

PESTLE analysis is one of the best analysis techniques for an environmental survey.
PESTLE stands for:
 Politics: It refers to governmental policies, financial support, and initiatives that affect a
company’s growth and success.
 Economy: It refers to economic factors such as inflation rates, labor costs, interest rates,
and energy costs.
 Social: It refers to the societal attributes that influence a company’s situation.
 Technology: It refers to the latest technologies and IT advancements that increase the
efficiency of a company.
 Legal: It refers to the regulations, governmental laws, standards, and other related aspects.
 Environment: It relates to environmental aspects such as weather, climate, and pollution.
EXAMPLE –Retail Shop
Components:
 Political:
o E-commerce regulations.
o Trade policies.
o Data protection laws.
 Economic:
o Consumer purchasing power.
o Economic stability.
o Tax policies.
 Social:
o Online shopping trends.
o Consumer behavior.
o Demographic changes.
 Technological:
o Advancements in web technologies.
o Cybersecurity measures.
o Mobile commerce growth.
 Legal:
o Compliance with e-commerce laws.
o Intellectual property rights.
o Consumer protection regulations.
 Environmental:
o Sustainable packaging.
o Environmental impact of logistics.
o Eco-friendly practices.
Business Analyst's Role: The BA would conduct the PESTLE analysis to understand the macro-
environmental factors that could affect the e-commerce platform. This helps in identifying
external opportunities and threats.

 Six Thinking Hats

Six thinking hats is a strong decision-making approach that incorporates several points of view.
It is a method for increasing the productivity of creative thinking by categorizing diverse
thinking styles into six hats.
 White Hat: Information
 Focus on data, facts, and information available. Look for gaps in knowledge and seek
additional information.
 Example for a Business Analyst:
o In a project to improve customer service, the BA gathers data on current
response times, customer satisfaction scores, and common issues reported by
customers.
 Red Hat: Emotions
 Express feelings, intuitions, and emotions. Consider the emotional impact of decisions.
 Example for a Business Analyst:
o The BA asks team members how they feel about the current customer service
process and gathers emotional responses from frontline staff about their daily
challenges.
 Black Hat: Caution
 Identify potential risks, challenges, and negative outcomes. Critically evaluate
weaknesses and potential problems.
 Example for a Business Analyst:
o The BA considers potential risks of implementing a new customer service system,
such as system downtime, staff resistance, and training requirements.
 Yellow Hat: Benefits
 Focus on the positive aspects and potential benefits. Look for opportunities and
advantages.
 Example for a Business Analyst:
o The BA highlights the benefits of the new customer service system, such as faster
response times, higher customer satisfaction, and improved efficiency.
 Green Hat: Creativity
 Encourage creative thinking and explore new ideas and alternatives. Look for innovative
solutions.
 Example for a Business Analyst:
o The BA facilitates brainstorming sessions to come up with innovative ways to
enhance customer service, such as using AI chatbots or implementing a loyalty
program.
 Blue Hat: Process
 Manage the thinking process and ensure that the Six Hats method is followed
effectively. Focus on organizing and controlling the process.
 Example for a Business Analyst:
 o The BA acts as the facilitator, ensuring that each hat is used in sequence and that
the team stays focused on the task.

 White Hat: The team gathers data on current customer service metrics, including
average response time, resolution time, and customer satisfaction scores.
 Red Hat: Team members share their feelings about the current system. Customer
service representatives express frustration with the outdated software.
 Black Hat: The team identifies potential risks of upgrading the system, such as the
cost, time required for training, and possible disruption during the transition.
 Yellow Hat: They list the potential benefits, such as increased customer satisfaction,
reduced workload for staff, and better tracking of customer issues.
 Green Hat: The team brainstorms creative solutions, such as implementing a live chat
feature on the website and creating a self-service knowledge base.
 Blue Hat: The BA ensures that the discussion stays on track and that each perspective
is thoroughly explored.

 The 5 Whys

The 5 whys is a technique used for defining problems and finding technical solutions for the
same. The 5 whys refer to the technique of asking why a scenario has occurred five times to
pinpoint the problem’s fundamental causes. It emphasizes the necessity of looking beyond the
most evident cause of the problem. The 5 whys is a simple and efficient problem-solving
strategy. Its main objective is to ask a series of why inquiries to pinpoint the specific source of a
problem. The 5 whys assist a team in concentrating on the underlying cause of any problem.

The Five Whys technique is a simple yet effective problem-solving method used to identify the
root cause of a problem by asking "why" five times (or as many times as needed).
Steps:
1. Identify the Problem:
o Clearly state the problem you are facing.
o Example for a Business Analyst:
 The BA identifies that customer complaints about delivery delays have
increased.
2. Ask Why:
o Ask why the problem is occurring and write down the answer.
o Example for a Business Analyst:
  Why are there delivery delays? Answer: Because the shipping process is
taking longer than expected.
3. Ask Why Again:
o Ask why the reason identified in the previous step is happening. Continue this
process until you reach the root cause.
o Example for a Business Analyst:
 Why is the shipping process taking longer? Answer: Because there are
delays in the warehouse.
 Why are there delays in the warehouse? Answer: Because the inventory
management system is outdated.
 Why is the inventory management system outdated? Answer: Because
the company has not invested in new technology.
 Why has the company not invested in new technology? Answer: Because
there was no budget allocated for it in the last financial year.
4. Determine the Root Cause:
o The final answer should reveal the root cause of the problem.
o Example for a Business Analyst:
 The root cause is that there was no budget allocated for upgrading the
inventory management system.
5. Address the Root Cause:
o Develop a plan to address the root cause.
o Example for a Business Analyst:
 The BA presents a business case to allocate budget for upgrading the
inventory management system to the stakeholders.
Example Scenario: A BA is investigating an increase in customer complaints about delayed
deliveries.
1. Identify the Problem: Customers are complaining about delayed deliveries.
2. Ask Why: Why are deliveries delayed? Because the shipping process is taking longer
than expected.
3. Ask Why Again: Why is the shipping process taking longer? Because there are delays in
the warehouse.
4. Ask Why Again: Why are there delays in the warehouse? Because the inventory
management system is outdated.
5. Ask Why Again: Why is the inventory management system outdated? Because the
company has not invested in new technology.
6. Ask Why Again: Why has the company not invested in new technology? Because there
was no budget allocated for it in the last financial year.
Root Cause: The root cause is that there was no budget allocated for upgrading the inventory
management system.
Solution: The BA recommends allocating budget for upgrading the inventory management
system and presents this plan to the stakeholders for approval.
 Business Analyst Tasks in Requirements Analysis (RA)
The requirements analysis phase is critical in ensuring that the project meets stakeholders'
needs and business goals. As a Business Analyst (BA), you play a vital role in gathering,
analyzing, and validating the requirements. Here's a detailed look at each task from a business
analyst's perspective:
1. Prioritize Requirements
o Definition: Determining which requirements are most important and should be
addressed first.
o Activities:
 Collaborate with stakeholders to understand the value and impact of
each requirement.
 Use prioritization techniques like MoSCoW (Must have, Should have,
Could have, Won't have) or Weighted Scoring.
o Example: In a software development project, prioritize features based on user
demand and business value.
2. Coordinating with the Product Team
o Definition: Ensuring alignment between the product vision and the
requirements.
o Activities:
 Regular meetings with the product team to discuss requirements, clarify
doubts, and ensure feasibility.
 Providing detailed requirement documentation and updates.
o Example: In a new product launch, ensure that the product features align with
market research and user feedback.
3. Confirming with the Stakeholders
o Definition: Ensuring that all stakeholders agree on the requirements and their
specifications.
o Activities:
 Organize requirement review sessions and walkthroughs.
 Obtain formal sign-offs on requirements documents.
o Example: For a banking application, confirm that security features meet
regulatory requirements and stakeholder expectations.
4. Specify the Mode of Requirements
o Definition: Determining how requirements will be documented, communicated,
and managed.
o Activities:
 Choose suitable documentation formats (user stories, use cases,
requirement specifications).
 Decide on tools for requirement management (JIRA, Confluence).
o Example: For a healthcare application, use detailed requirement specifications to
ensure compliance with health standards.
5. Define In-Scope, Out-of-Scope, and Assumptions
o Definition: Clearly defining what will be included in the project and what will
not, along with any assumptions.
o Activities:
  Create a scope document outlining all in-scope and out-of-scope items.
 List assumptions that impact requirements and project scope.
o Example: In an e-commerce project, defining in-scope features like product
search and checkout, while out-of-scope might be advanced analytics features.
6. Final Validating for Requirements
o Definition: Ensuring that all requirements are complete, consistent, and feasible
before moving to the next phase.
o Activities:
 Perform requirement validation techniques like reviews, prototyping, and
model validation.
 Ensure traceability between requirements and business objectives.
o Example: Before developing a mobile app, validate that all user interface
requirements meet usability standards.
7. Formal Documents and Mail to Stakeholders/Clients/Product Team
o Definition: Preparing and distributing formal documentation of requirements to
all relevant parties.
o Activities:
 Create comprehensive requirement documents and detailed reports.
 Distribute documents via emails or project management tools and obtain
acknowledgments.
o Example: For a CRM system, provide stakeholders with detailed requirements
documents and obtain their formal approval before development begins.
Detailed Examples
1. Prioritizing Requirements:
o Scenario: Developing a new feature for a banking app.
o Action: Use MoSCoW prioritization to classify features like "two-factor
authentication" as a must-have, while "dark mode" could be a should-have.
2. Coordinating with the Product Team:
o Scenario: Adding a new payment method to an e-commerce platform.
o Action: Regularly sync with the product team to ensure the integration meets
both technical feasibility and market demands.
3. Confirming with Stakeholders:
o Scenario: Implementing a new data analytics dashboard.
o Action: Hold review sessions with stakeholders to ensure the dashboard meets
their reporting needs and get formal sign-off.
4. Specify the Mode of Requirements:
o Scenario: Launching a mobile health tracking app.
o Action: Document requirements using user stories in JIRA and use Confluence for
detailed requirement specifications.
5. Define In-Scope, Out-of-Scope, and Assumptions:
o Scenario: Creating a customer feedback system.
o Action: In-scope includes feedback collection and basic reporting; out-of-scope
includes advanced sentiment analysis. Assume integration with existing CRM.
 6. Final Validating for Requirements:
o Scenario: Developing a new HR management system.
o Action: Validate that all HR processes are captured accurately and ensure
traceability between requirements and business goals.
7. Formal Documents and Mail to Stakeholders/Clients/Product Team:
o Scenario: Building a new ticketing system for customer support.
o Action: Compile all requirements into a formal document, distribute it to
stakeholders and product team, and get their formal approval.
By performing these tasks effectively, a Business Analyst ensures that the project stays on track,
meets the stakeholders' needs, and delivers value to the business.