Enterprise analysis | COEPD

1
Enterprise analysis
(Professional Business Analyst Training
organisation)
2

• Enterprise analysis is conducted using primary
  research and secondary research using various
  techniques to assess and identify the current
  business challenges.
• Once the enterprise analysis is conducted, it
  will help us address those challenges and to keep
  the future process competitive proof.
• Enterprise analysis helps us to frame strategy
  and gain edge over competitive forces, such as
  advanced technologies, products or other
  enterprises.

3

• Usually enterprise analysis is conducted to
  address structural/hierarchical changes in the
  organization, process changes in the
  organization, business process re-engineering, or
  transiting from legacy applications to modern
  applications.
• Conducting enterprise analysis has become
  essential element in todays industrious world,
  due to high competitiveness, business innovation
  and disruption and advanced technologies.

Traditional BA (Waterfall) Agile BA
Requirements are documented in Use Cases,Business Requirements, Functional requirements, UI Specifications, Business Rules. Requirements are documented in Epics, User Stories and optionally Business (or Essential) Use cases.
   
Focuses on completeness of requirement and spends time in ensuring the requirement is unambiguous and has all the details. Focuses on understanding the problem and being the domain expert so that s/he can answer questions from the development team swiftly and decisively.
Focuses on getting a sign off on the requirements. Focuses on ensuring the requirements meet the currentbusiness needs, even if it requires updating them.
Often there is a wall between the BA/Business and the Development team. Agile BA (Often called as Product Owner) is part of the team.
Tends to dictate solutions. Has to remain in the problem domain, leaving the development team space to explore different solutions.
Long turnaround. Quick turnaround.
Focus on what the requirements document said. In other words, output (Artifact) is a well written thorough requirements document. Focus on the functionality of the developed software. In other words, output (Artifact) is the software that meets thebusiness needs.
   
4

• Enterprise analysis is conducted using SWOT
  analysis, GAP analysis, Porters five force
  analysis, root cause analysis, Ishikawa diagram
  or Fishbone diagram, PEST or PESTLE analysis.
• SWOT Strength, Weakness, Opportunities,
  Threats.
• Porter five forces - power of suppliers, power of
  customers, threat of substitutes, threat of new
  entrants, rivalry within industry.
• GAP analysis no proper methodology, it is
  basically a GAP that needs achievement between
  current state and desired state

Traditional BA (Waterfall) Agile BA
Requirements are documented in Use Cases,Business Requirements, Functional requirements, UI Specifications, Business Rules. Requirements are documented in Epics, User Stories and optionally Business (or Essential) Use cases.
   
Focuses on completeness of requirement and spends time in ensuring the requirement is unambiguous and has all the details. Focuses on understanding the problem and being the domain expert so that s/he can answer questions from the development team swiftly and decisively.
Focuses on getting a sign off on the requirements. Focuses on ensuring the requirements meet the currentbusiness needs, even if it requires updating them.
Often there is a wall between the BA/Business and the Development team. Agile BA (Often called as Product Owner) is part of the team.
Tends to dictate solutions. Has to remain in the problem domain, leaving the development team space to explore different solutions.
Long turnaround. Quick turnaround.
Focus on what the requirements document said. In other words, output (Artifact) is a well written thorough requirements document. Focus on the functionality of the developed software. In other words, output (Artifact) is the software that meets thebusiness needs.
   
5

• PEST(LE) influencing factors - Political,
  economic, social, technological, legal,
  environmental.
• Enterprise analysis is sometimes referred as
  market research and business research in some
  contexts esp. value chain analysis, consumer
  analysis, surveys, market size/segmentation,
  regression analysis, forecasting, financial
  research etc..,
• Quantitative data used in Enterprise analysis is
  processed through various reporting and data
  visualizations tools and softwares such as MS
  Excel VBA, SAS, SPSS, SRSS, Tableau, Power BI, BI
  tools.

Traditional BA (Waterfall) Agile BA
Requirements are documented in Use Cases,Business Requirements, Functional requirements, UI Specifications, Business Rules. Requirements are documented in Epics, User Stories and optionally Business (or Essential) Use cases.
   
Focuses on completeness of requirement and spends time in ensuring the requirement is unambiguous and has all the details. Focuses on understanding the problem and being the domain expert so that s/he can answer questions from the development team swiftly and decisively.
Focuses on getting a sign off on the requirements. Focuses on ensuring the requirements meet the currentbusiness needs, even if it requires updating them.
Often there is a wall between the BA/Business and the Development team. Agile BA (Often called as Product Owner) is part of the team.
Tends to dictate solutions. Has to remain in the problem domain, leaving the development team space to explore different solutions.
Long turnaround. Quick turnaround.
Focus on what the requirements document said. In other words, output (Artifact) is a well written thorough requirements document. Focus on the functionality of the developed software. In other words, output (Artifact) is the software that meets thebusiness needs.
   
6
(No Transcript)