A Buddhist proverb warns, “Be mindful of intention. Intention is the seed that creates our future.” In a very real sense, this statement expresses the reason for business analysis. This discipline is really all about choosing and defining a desired future because without intention (expressed in business analysis terms, “requirements”), no future is more or less desirable than another.
In reality, every organization does some form of business analysis whether it uses the term or not. For many (especially larger organizations), it is an extremely structured, managed process while others thrive on change and only do business analysis when and as needed. The perception that business analysis is only needed to develop IT solutions is inaccurate. Actually, it is a critical component of any change initiative within an organization whether software is involved or not.Current Business Analysis Techniques and Methods
The course defines how business analysis is currently practiced. The authors provide insight into this fast-growing field by distinguishing strategic, tactical, and operational business analysis. It provides surveys of what Business Analysts really do and what business analysis techniques people use most often when they are the one “wearing the BA hat”. You will learn what “requirements” really are and what different types of requirements exist. Because many requirements define future information technology (IT) solutions, the authors share their experience on how Waterfall, Iterative, Agile, and Experimental (aka "Chaotic") Software Development methodologies impact the business analysis responsibility.
Although the field of Business Analysis offers great career opportunities for those seeking employment, some level of business analysis skill is essential for any adult in the business world today. Many of the techniques used in the field evolved from earlier lessons learned in systems analysis and have proven themselves to be useful in every walk of life. We have personally experienced how business analysis techniques help even in your private life.
We created this course for everyday people in the real world to give you a basic understanding of some core business analysis methods and concepts. If this course answers some of your questions, great. If it raises more questions than it answers (implying that it piqued your curiosity), even better. If it motivates you to learn more about this emerging and fascinating topic, it has served its purpose well.
This lecture will provide you with answers to the following questions:
If you would like additional information on business analysis, browse through the following resources.
Due to the evolution of the external and internal environments of an organization, change is a fact of life. As a result, business analysis is an on-going activity and organizations use it at 3 major levels of detail.
For additional insights into the nature of the various levels of business analysis, see the links below:
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:
Tom has been in business analysis since long before it was called business analysis. He has over 30 years experience in the fields of information technology, methodologies, and business analysis. In his writings and lectures he strives for enlightening while entertaining. As a facilitator, he achieves results through inclusion and synergistic group-building. He has taught thousands of students business and systems analysis skills since the '80's and has facilitated hundreds of requirements discovery sessions under a variety of acronyms (JAD, ASAP, JADr, JRP, etc).
Angela and Tom Hathaway (previously Hathaway & Associates, Inc. and Requirements Solutions Group, LLC) founded BA-EXPERTS in 2011. As a team, Angela and Tom have trained, consulted, mentored and coached thousands of business analysts around the world for organizations from small businesses to Fortune 100. Hundreds of current and past customers include TIAA-CREF (Financial), Cathay Pacific (Airline), Manitoba Telecom Services (Telecommunications), Starwood Hotels and Resorts (Hospitality), government agencies, and a myriad of organizations spanning all sizes and industries. Our training, consulting, and mentoring efforts have saved our customers around the world millions and can help your organization improve its business analysis practices