PDF Archive

Easily share your PDF documents with your contacts, on the Web and Social Networks.

Share a file Manage my documents Convert Recover PDF Search Help Contact



Enteprise analysis .pdf



Original filename: Enteprise analysis.pdf
Title: Slide 1
Author: admin

This PDF 1.5 document has been generated by Microsoft® PowerPoint® 2016, and has been sent on pdf-archive.com on 25/10/2016 at 08:33, from IP address 183.82.x.x. The current document download page has been viewed 172 times.
File size: 922 KB (6 pages).
Privacy: public file




Download original PDF file









Document preview


Enterprise analysis
(Professional Business Analyst Training organisation)

 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.

 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.
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
Agile BA (Often called as Product Owner) is part of the team.
team.

 Conducting enterprise analysis has become essential
element in today’s industrious world, due to high
competitiveness, business innovation and disruption
and advanced technologies.
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,
Focus on the functionality of the developed software. In other words,
output (Artifact) is a well written thorough requirements document. output (Artifact) is the software that meets thebusiness needs.

 Enterprise analysis is conducted using SWOT analysis,
GAP analysis, Porter’s 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
Agile BA (Often called as Product Owner) is part of the team.
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,
Focus on the functionality of the developed software. In other words,
output (Artifact) is a well written thorough requirements document. output (Artifact) is the software that meets thebusiness needs.

 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 software’s 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
Agile BA (Often called as Product Owner) is part of the team.
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,
Focus on the functionality of the developed software. In other words,
output (Artifact) is a well written thorough requirements document. output (Artifact) is the software that meets thebusiness needs.


Related documents


enteprise analysis
agile qa tester smita bhangre
1system com au aug 16
data integration solution 2
how to get the maximum benefits of your perceptive software
best software development companis in usa


Related keywords