Introduction to Business Analysis
The role and techniques needed for a Business Analyst
Ratings 4.65 / 5.00
What You Will Learn!
- Understanding of the software development lifecycle (SDLC)
- Understanding the role of a Business Analyst (BA) within the SDLC
- Techniques for eliciting requirments
- Techniques for documenting requirements
- An overview of how a BAs role changes in an Agile vs. Waterfall environment
Description
This class is designed for anyone involved in software development, with a focus on new developers. At DT Group, we believe application development is about more then just code. The more all members of an application development team understand the other roles, the more effect each member of the team will become.
In this class, we will walk through the role of a Business Analyst
Review the SDLC and roles, to see where the Business Analyst fits into the whole
A review of several types of projects where I was a Business Analyst to see the diverse types of situations these skills can be applied
A review of the most effective elicitation techniques and formats
A review of the types of documentation often required in both a Waterfall and Agile project
The most common types of documentation and documentation formats
Throughout the class, I will discuss the need to stay curious. The most valuable skill a Business Analyst has is curiosity. What does the user really need? Why do they need it? How will the help them?
This class will help you understand that curiosity mindset and give you different techniques to explore these questions more deeply.
I hope you enjoy!
Who Should Attend!
- Anyone new to software development
- Anyone looking to learn or improve their skills in eliciting or documenting requirements
- Citizen Developers who need to help gather their own requirements