WHY EVERYONE
NEEDS A BUSINESS
ANALYST ON THE
PROJECT
Business Analysis in IT
WHO IS
THE
BUSINESS
ANALYST
They also help to
streamline
requirements and
manage project
expectations.
They
BRIDGE THE
COMMUNICATION
between development teams,
business stakeholders, and quality
assurance teams.
The communication
liaison from project
inception through
final delivery.
 Define a project scope
 Elicitate and translate business
needs
 Translate technical issues
 Analyze requirements
 Model and document
requirements
 Manage requirements
BUSINESS ANALYST RESPONSIBILITIES
A REQUIREMENT IS DEFINED
TO BE:
 A condition or capability needed by a
stakeholder to solve a problem or
achieve an objective
 A condition or capability that must be
met or possessed by a solution or
solution component to satisfy a
contract
 Sound documented representation of
a condition or capability
BUSINESS
ANALYST
INTERACTION
Subject matter
Experts/Users Solution
Developers
BUSINESS
ANALYST
Project
Manager
Customer
(Product Manager/
Product Owner)
Sales
Manager
REQUIREMENT
ELICITATION AND
ANALYSIS
• User Cases
• User Stories
• Vision and Scope Document
SYSTEM
DESIGN
• Logical Design(Modeling)
• Prototypes, sketches
• mockups
IMPLEMENTATION • Software Requirement
Specification
• Backlog
TESTING
DEPLOYMENT
MAINTENANCE
• User Scenarios
• Acceptance Criteria
• Acceptance Tests
• Post-delivery
requirements
• Management support
BA ROLE IN ITERATIVE
DEVELOPMENT
CATEGORIES
OF ANALYST
ACTIVITIES
BUSINESS
DOMAIN
CUSTOMER
BUSINESS
NEEDS
REQUIREMENTS
BUSINESS
PROCESS
PROJECT
TEAM
CATEGORIES OF
ANALYST’S ACTIVITIES
Т H E
C U S T O M E R
needs a technical
interface to create
complete, detailed
requirements
Customers rarely come to the project
table with detailed requirements and if
they think that's what they have then
those requirements need to be
questioned heavily.
BUS IN ES S
AN ALYS T
provide critical
oversight during
project
implementation
When the time does come for go-live, the
Business Analyst can likely be the best
interface with the project client – working
closely with the Project Manager and the
tech team to ensure:
 the solution is rolled out smoothly to the
customer and end users,
 training needs have been identified and
addressed, and
 the proper handoff to support has been
achieved.
T H E P R O J E C T
M A N A G E R
needs to focus on
project management
tasks
 There are enough
administrative tasks on most
projects to justify a full-time
Project Manager
T H E T E C H
L E A D needs a
good liaison
heading into
design work on
the project
Having the BA in place to help translate
those business requirements into functional
requirements with and for the Tech Lead on
the project.
If you decide to save on BA position for
technical projects, then you are likely to
spend MUCH MORE on a longer planning
and design portion of the project.
BA
DELIVERABLES
1.Get Oriented
2.Discover the
Primary
Business
Objectives
Have
Backgrou
nd on All
Areas?
3.Define Scope
4. Formulate BA
Plan
Scope
Statement
BA Plan
5. Define
Detailed
Requirements
6. Support
Technical
Implementation
7. Help the
Business
Implement the
Solution
8. Assess Value
Created by the
Solution
Discover
New
Project?
End
BA Deliverables
Performance
Report
Yes
No
Yes
No
The main
artifacts of
business
analyst
 List of stakeholders
 Plan of BA activities
 Plan of communications
 V&S(Vision and Scope Document)
 Backlog
 Analysis models
 SRS(Software requirement Specification), Function
Specification
 Correlating models(accompanying) models: Use
Case diagrams, User Scenarios, State Diagrams
and Transitions Diagram, Logical Data Diagram
and etc.
 Prototypes/Sketches/Mockups
BENEFITS AT
A GLANCE
B U S I N E S
S
A N A L Y S T
provide critical
oversight during
project
implementation
Т H E
C U S T O M E
R
needs a technical
interface to create
complete, detailed
requirements
P R O J E C T
M A N A G E R
needs to focus on
project management
tasks
T E C H
L E A D
needs a good
liaison heading into
design work on the
project
Conclusion
 professional ideas for product
implementation
 usable, detailed, complete
requirements
 sound project organization
 product finished within the
budget and project schedule
 the end product will be relevant to
the business needs
 saved time
 saved money
Do you HAVE a business
analyst for full customer
experience?

Business analysis in IT

  • 1.
    WHY EVERYONE NEEDS ABUSINESS ANALYST ON THE PROJECT Business Analysis in IT
  • 2.
  • 3.
    They also helpto streamline requirements and manage project expectations. They BRIDGE THE COMMUNICATION between development teams, business stakeholders, and quality assurance teams. The communication liaison from project inception through final delivery.
  • 4.
     Define aproject scope  Elicitate and translate business needs  Translate technical issues  Analyze requirements  Model and document requirements  Manage requirements BUSINESS ANALYST RESPONSIBILITIES
  • 5.
    A REQUIREMENT ISDEFINED TO BE:  A condition or capability needed by a stakeholder to solve a problem or achieve an objective  A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract  Sound documented representation of a condition or capability
  • 6.
  • 7.
  • 9.
    REQUIREMENT ELICITATION AND ANALYSIS • UserCases • User Stories • Vision and Scope Document SYSTEM DESIGN • Logical Design(Modeling) • Prototypes, sketches • mockups IMPLEMENTATION • Software Requirement Specification • Backlog TESTING DEPLOYMENT MAINTENANCE • User Scenarios • Acceptance Criteria • Acceptance Tests • Post-delivery requirements • Management support BA ROLE IN ITERATIVE DEVELOPMENT
  • 10.
  • 11.
  • 12.
    Т H E CU S T O M E R needs a technical interface to create complete, detailed requirements Customers rarely come to the project table with detailed requirements and if they think that's what they have then those requirements need to be questioned heavily.
  • 13.
    BUS IN ESS AN ALYS T provide critical oversight during project implementation When the time does come for go-live, the Business Analyst can likely be the best interface with the project client – working closely with the Project Manager and the tech team to ensure:  the solution is rolled out smoothly to the customer and end users,  training needs have been identified and addressed, and  the proper handoff to support has been achieved.
  • 14.
    T H EP R O J E C T M A N A G E R needs to focus on project management tasks  There are enough administrative tasks on most projects to justify a full-time Project Manager
  • 15.
    T H ET E C H L E A D needs a good liaison heading into design work on the project Having the BA in place to help translate those business requirements into functional requirements with and for the Tech Lead on the project. If you decide to save on BA position for technical projects, then you are likely to spend MUCH MORE on a longer planning and design portion of the project.
  • 16.
  • 17.
    1.Get Oriented 2.Discover the Primary Business Objectives Have Backgrou ndon All Areas? 3.Define Scope 4. Formulate BA Plan Scope Statement BA Plan 5. Define Detailed Requirements 6. Support Technical Implementation 7. Help the Business Implement the Solution 8. Assess Value Created by the Solution Discover New Project? End BA Deliverables Performance Report Yes No Yes No
  • 18.
    The main artifacts of business analyst List of stakeholders  Plan of BA activities  Plan of communications  V&S(Vision and Scope Document)  Backlog  Analysis models  SRS(Software requirement Specification), Function Specification  Correlating models(accompanying) models: Use Case diagrams, User Scenarios, State Diagrams and Transitions Diagram, Logical Data Diagram and etc.  Prototypes/Sketches/Mockups
  • 19.
  • 20.
    B U SI N E S S A N A L Y S T provide critical oversight during project implementation Т H E C U S T O M E R needs a technical interface to create complete, detailed requirements P R O J E C T M A N A G E R needs to focus on project management tasks T E C H L E A D needs a good liaison heading into design work on the project Conclusion
  • 21.
     professional ideasfor product implementation  usable, detailed, complete requirements  sound project organization  product finished within the budget and project schedule  the end product will be relevant to the business needs  saved time  saved money
  • 22.
    Do you HAVEa business analyst for full customer experience?