What Is Business Analysis for Information Technology (IT)

There are 4 different types of requirements and each type expresses a different level of detail. The highest level are Business Requirements and a typical project will address very few. Business requirements spawn stakeholder requirements spawn solution requirements. Solution requirements turn the focus of the stakeholder requirements towards the solution technology. Finally, transition requirements define components of the solution that only exist to replace the current solution, as it exists today.

To learn even more about requirements, browse through the links below.

Business requirements define high-level goals and objectives of an organization as a whole and address the question, "Why is this project needed?"

Stakeholder requirements express the needs and wants of one or more stakeholders and how they will interact with a solution.

Solution requirements describe specific characteristics of a solution that meet business and stakeholder requirements and come in two flavors.

Functional Solution Requirements define what the solution has to do or know.

Non-Functional Solution Requirements define characteristics that any solution must exhibit for it to be acceptable.

Transition Requirements describe capabilities needed to integrate the proposed solution into the existing environment.

This lecture will address the different business analysis techniques that are used in Strategic, Tactical, and Operational Business Analysis.

The Requirements Solutions Group (RSG) surveyed over 1700 individuals with many different job titles, all of whom wore the business analysis hat at some level of detail. They were asked to identify the tools they most commonly needed. Theses are the results.

How do you do business analysis? For an answer to that question, we offer first off a survey from the International Institute of Business Analysis (IIBA^®). The IIBA^® is an organization dedicated to defining standards and practices for the business analyst community. A 2008 survey of around 1200 business analysts asked what specific techniques business analysts needed to do their job. This lecture contains the results.

This lecture shows how current Software Development Methodologies (SDM) impact your business analysis activities.

This lecture defines business analysis within traditional waterfall (structured) system development approaches.

Defining business analysis within traditional iterative system development approaches such as RUP.

In the Agile development methodology, the person wearing the business analysis hat (whom we call THE BA, whether or not that individual has that job title) does business analysis strictly on an as-needed basis. This lecture explains how business analysis fits within Agile software development approaches such as SCRUM and SCRUM/XP hybrids.

Thank you for buying this course. We hope you enjoyed it.

Questions answered in this lecture:

• Where do we see business analysis going?
• How could that affect you?
• How could it affect the education system?

This bonus lecture lists other Udemy courses we offer for aspiring and practicing business analysts to improve your skills in a wide variety of areas you need to round out your toolkit.