01.11.2017 Views

BABOK_Guide_v3_member_copy

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Perspectives<br />

The Information Technology Perspective<br />

architecture, software testing experience, or other technical skills. However,<br />

development-related skills or technical skills are not necessary for a business<br />

analyst to be successful within an IT environment. It is important for the business<br />

analyst to have a strong understanding of the detail required within a<br />

requirements package to support technical solutions, as well as an understanding<br />

of what is technically feasible within the constraints of an organization’s technical<br />

architecture. These skills will enable a business analyst to work with all<br />

stakeholders to design a business solution framework which will also allow the<br />

technical team the flexibility to design a technical solution.<br />

Business analysts use influencing and facilitation skills when working with<br />

stakeholders. Negotiation skills are frequently used when working with business<br />

and technical staff to come to agreements and decisions if the costs of a solution<br />

(either in budget, time, or architectural impact) conflict with the desired business<br />

outcome.<br />

Systems thinking is a crucial competency for business analysts practicing in an IT<br />

environment. Systems thinking supports the ability of the business analyst to see<br />

the larger picture including any other applications or technical aspects which may<br />

be impacted, the details of the specific need, and possible technical solutions.<br />

Systems thinking also supports the ability to identify impacts to people, processes,<br />

and software which are not necessarily directly changed as part of an IT<br />

development effort, and to analyze the risks and possible outcomes of those<br />

impacts.<br />

11.3.5 Impact on Knowledge Areas<br />

This section explains how specific business analysis practices within information<br />

technology are mapped to business analysis tasks and practices as defined by the<br />

<strong>BABOK</strong> ® <strong>Guide</strong>. It also describes how each knowledge area is applied or modified<br />

within the IT discipline.<br />

Each knowledge area lists techniques relevant to an IT perspective. Techniques<br />

used in the discipline of information technology do not deviate, to any great<br />

extent, from the <strong>BABOK</strong> ® <strong>Guide</strong> techniques. <strong>BABOK</strong> ® <strong>Guide</strong> techniques are<br />

found in the Techniques chapter of the <strong>BABOK</strong> ® <strong>Guide</strong>. This is not intended to be<br />

an exhaustive list of techniques but rather to highlight the types of techniques<br />

used by business analysts while performing the tasks within the knowledge area.<br />

Complimentary IIBA® Member Copy. Not for Distribution or Resale.<br />

.1 Business Analysis Planning and Monitoring<br />

A business analysis approach is a fundamental communication tool which can be<br />

used to identify resources required for business analysis work and ensure<br />

adequate time for the analysis effort. A well-defined business analysis plan<br />

integrates into the overall project plan and provides business analysts with the<br />

opportunity to define and schedule the business analysis activities for the project.<br />

Many organizations have some standards and processes in place, which may<br />

identify certain analysis tasks and deliverables. If these are not in place, the<br />

business analyst identifies these tasks and deliverables based on the needs of the<br />

specific initiative.<br />

401

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!