The document outlines the 10 key roles of a business analyst in managing analytics requirements, which include extracting, anticipating, constraining, organizing, translating, safeguarding, simplifying, verifying, and managing requirements. Ensuring proper requirements management is critical for project success to avoid failures, optimize resource use, and align business objectives with technical solutions. Additionally, the document discusses the maintenance and enhancement responsibilities of the business analyst after project delivery.

1. Welcome

2. Topic
Key roles for successful analytic project

3. Key roles for successful analytic project
 Here are the business analyst’s 10 key roles in
defining and managing requirements:
1. Extract Requirements
2. Anticipate Requirements
3. Constrain Requirements
4. Organize Requirements
5. Translate Requirements
6. Safeguard Requirements
7. Simplify Requirements
8. Verify Requirements
9. Managing Requirements
10. System and operations maintenance

4. Extract Requirements
 Requirements play a key part in
engineering IT systems. Incomplete or
improper requirements usually lead to
project failure.
 A business analyst determines a project’s
requirements by extracting them from
business or government policies, as well as
from current and future users, through
interaction and research.

5. Anticipate Requirements
 Skilled business analyst know how quickly
things change in the dynamic world of IT.
 Baseline plans are subject to modification,
and anticipating requirements that will be
needed in the future or that have not yet
been considered is essential to successful
outcomes.

6. Constrain Requirements
 While complete requirements are essential
to project success, the focus must remain
on core business needed, and not user’s
personal preference, functions related to
trends or outdated processes, or other
non-essential modifications.

7. Organize Requirements
 Requirements often originate from disparate,
sometimes opposing sources.
 The business analyst must organize
requirements into related categories to
effectively managed and communicate them.
 Requirements are sorted into types according
to their source and applicability.
 Proper organization prevents project
requirements from becoming overlooked, and
leads to optimum use of time and budgets.

8. Translate Requirements
 The business analyst must be adapt at
translating business requirements to
technical requirements.
 This includes using powerful analysis and
modeling tool to match strategic business
objectives with practical technical
solutions.

9. Safeguard Requirements
 At regular intervals in the project life cycle,
the business analyst safeguards or
protected the business and user’s need by
verifying functionality, accuracy and
completeness of the requirements against
the original initiating documents.
 Safeguarding minimizes risk by ensuring
requirements are being met before
investing further in system development.

10. Simplify Requirements
 The business analyst emphasizes simplicity
and ease of use at all times, but especially
in implementation.
 Meeting business objectives in the goal of
every IT project; business analysts identify
and avoid extraneous activities that do not
solve the problem or help reach the
objective.

11. Verify Requirements
 The business analyst is most
knowledgeable about use cases; therefore
they continually verify the requirements
and reject implementations that do not
advance business objectives.
 Verifying requirements is accomplished
through analysis, test, demonstration and
inspection.

12. Managing Requirements
 Typically, a formal requirements
presentation, review and approval session
occurs, where project schedules, costs and
duration estimates are updated and the
business objectives are revisited.
 Upon approval, the business analyst
transitions into requirements management
activities for the rest of the IT solution life
cycle.

13. System and Operations
Maintenance
 Once all requirements have been met and the
IT solution delivered, the business analyst’s
role shifts to maintenance, or preventing and
correcting defects; enhancements, or making
changes to increase the value provided by the
system; and operations and maintenance, or
providing system validation procedures,
maintenance reports, deactivation plans, and
other documents, plans and reports.
 The business analyst will also play a major
role in analyzing the system to determine
when deactivation or replacement is required.

14. References
 Inspiration from Prof. Barkha Joshi and
Prof. Shrina P. Patel
 Notes of DMBI
 Textbook of DMBI
 Images from Google Images

15. Thank You