When does class start/end?
Classes begin promptly at 9:00 am, and typically end at 5:00 pm.
This 4-day Business Analyst training course will give you hands-on experience with the latest proven techniques for identifying a project's scope, developing and discovering requirements and uses cases, and documenting them expertly. Lively lectures combined with insightful demonstrations and realistic practice exercises will provide you with the competence and confidence to improve project outcomes through better requirements elicitation and use case development. You'll gain a thorough understanding of the challenges faced in defining correct requirements, practical approaches for eliciting and documenting requirements, and strategies for managing requirements throughout the project life cycle. If you play a role in defining project scope, capturing requirements, or managing project scope, you can't afford to miss this course!
Business Analysts provide an essential function by assessing and analyzing the business environment, defining the scope of business problems, capturing project requirements, designing high-value solution approaches, and ensuring that the defined scope meets the customer's needs, goals, objectives, and expectations. This practical workshop will provide participants with fundamental analysis tools and techniques, including methods to understand the business environment, define a problem using a systematic approach, and influence and inform project stakeholders at all levels. You will gain pragmatic solutions to sustain stakeholder engagement throughout the project lifecycle, including questioning, listening, business need identification, problem solving, presentation, validation, and acceptance of the effective solution.
It's only in recent years that business analysis has begun to be recognized as a profession it its own right. While people have been performing the Business Analyst role in organizations for several decades, differing definitions of the role abound. We'll start the workshop by exploring some of them, as well as gaining a clear understanding of where the industry appears to be heading and some emerging standards for the profession.
IT projects have especially high failure rates, and evidence points to problems with defining requirements as one primary cause. This section presents an overview of the challenges inherent in projects in general, and specific problems typically encountered with IT project requirements. We also examine some common terms and concepts in requirements engineering.
In order to increase project success, we need to implement a repeatable, scalable strategy for effective business analysis. In this section, we'll explore a framework in which good business analysis occurs and we'll discuss ways to maximize project success using this framework.
What most people think of as business analysis is central to project initiation. Because of the depth of skill these activities require, most Business Analysts demand separate training to develop true mastery. This course module therefore provides an overview and introduction to three crucial business analysis activities by demonstrating common tools for identifying and documenting project scope, for modeling current and desired states, and for stakeholder identification. And because effective initiation can lay the foundation for effective use case development, we'll introduce use cases and begin to identify them in this module, too.
After we've elicited the high-level and mid-level requirements for our project, we want to check to be sure that what we have so far is a good description of the project's scope. Writing requirements is one thing—writing "good" or "effective" requirements is another matter. As we are hearing and documenting requirements from our stakeholders, we should be evaluating them for effectiveness and refining/rewriting those that are not. In this section, we'll learn to derive maximum benefit from reviews throughout the life cycle. We'll then take a closer look at the issue of requirements quality, focusing on writing effective requirements through analysis, refinement, and review. Finally, we'll discuss how to document the scope of the project to minimize rework and creep.
Savvy business analysts and project team members have a variety of techniques for finding the detailed functional and non-functional requirements on their projects. This section introduces several of the most powerful and effective analysis techniques and discusses their use in requirements elicitation. As various techniques are covered, the workshop explores how to capture and document the requirements, including effective requirements analysis and traceability.
Developing use cases is fairly straightforward, but someone actually has to document the use cases and requirements discovered during the requirements elicitation process. This section of the workshop focuses on how to apply the knowledge you've gained so far to writing a use case. It also examines more complex aspects of uses cases, including sub-use cases and use-case linkages in larger systems.
Once we've worked with stakeholders to define their functional and non-functional requirements and to document, refine, and organize the requirements, we have to package those requirements into a specification. In addition, most systems also possess a significant number of requirements that aren't necessarily associated with specific business functions. These types of non-functional requirements must also be captured and documented as part of the complete requirement specification. This portion of the Boot Camp covers how to package the requirements into a specification that can be used for system development and testing.
Classes begin promptly at 9:00 am, and typically end at 5:00 pm.
Lunch is normally an hour long and begins at noon. Coffee, tea, hot chocolate and juice are available all day in the kitchen. Fruit, muffins and bagels are served each morning. There are numerous restaurants near each of our centers, and some popular ones are indicated on the Area Map in the Student Welcome Handbooks - these can be picked up in the lobby or requested from one of our ExitCertified staff.
If someone should need to contact you while you are in class, please have them call the center telephone number and leave a message with the receptionist.
Most courses are conducted in English, unless otherwise specified. Some courses will have the word "FRENCH" marked in red beside the scheduled date(s) indicating the language of instruction.
GTR stands for Guaranteed to Run; if you see a course with this status, it means this event is confirmed to run. View our GTR page to see our full list of Guaranteed to Run courses.
We have training locations across the United States and Canada. View a full list of classroom training locations.
Yes, we provide training for groups, individuals and private on sites. View our group training page for more information.
Yes, we provide training for groups, individuals, and private on sites. View our group training page for more information.
I had a good experience with ExitCertified. I got a deeper understanding of AWS and should be able to put it to practice immediately.
need to work on your evantage digital book, you can't get to individual pages without scrolling through entire book.
Overall the course material was great and the labs were hands on, which us nice when learning new material
The course had a balanced structure with labs that helped supplement the learning material and it was incredibly beginner friendly.
The course content and the delivery by the Instructor was good. I had a good learning experience with ExitCertified. Definitely recommend it to others.
93 options available