This course can be tailored to your needs for private, onsite delivery at your location.
ASPE is an IIBA Endorsed Education Provider of business analysis training. Select Project Delivery courses offer IIBA continuing development units (CDU) in accordance with IIBA standards.
This course offers 28.00 IIBA CDUs.
NASBA continuing professional education credits (CPE) assist Certified Public Accountants in reaching their continuing education requirements.
This course offers 33.00 NASBA CPEs.
Select courses offer Leadership (PDU-L), Strategic (PDU-S) and Technical PMI professional development units that vary according to certification. Technical PDUs are available in the following types: ACP, PBA, PfMP, PMP/PgMP, RMP, and SP.
This course offers:
14.00 PMP/PgMP Technical PDUs
14.00 PMI-PBA Technical PDUs
1.00 PMI-ACP Technical PDUs
1.00 PMI-RMP Technical PDUs
3.00 PMI-SP Technical PDUs
7.00 PMI Strategic PDUs
7.00 PMI Leadership PDUs
*This course has been updated, improved and expanded to be consistent with the Business Analyst Body of Knowledge Version 3.0, with additional references to the PMI-PBA certification, as well as Agile techniques.
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.
Delays, cancellations, and defects in systems development projects stem in large part from our inability to understand project requirements and the environment in which they exist, as well as our inability to communicate those requirements clearly enough to enlist the collaboration and commitment of all core project stakeholders. The accumulating evidence is unequivocal: most serious problems associated with projects are related directly to requirements. This course solidifies the foundations of business analysis and equips business analysts with the critical thinking, analytical skills, and necessary people skills to attack the problem of project failures by addressing their root causes: incomplete, poorly defined, and/or changing requirements.
*Please note, if you are taking this class as part of the St. Louis University Certificate requirements, there is a $500 fee to claim your certificate once you have completed ALL requirements.
- Upcoming Dates and Locations
All Live Online times are listed in Eastern Time Guaranteed To Run
- Course Outline
I. The Business Analysis Profession
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.
- IIBA® and the BABOK®
- What is Business Analysis?
- Business and Solution Domains—how they relate
- Key roles in requirements development in SDLC and Agile projects
- The competencies of the Business Analyst
- Distinguishing novice and expert Business Analysts
- Effective communication
- Six important BA skills
- Business analysis definition
- Competencies of a business analyst
II. The Business Case for Good Requirements
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.
- What is a good requirement?
- Requirements attributes—who needs them?
- Key practices that promote excellent requirements
- The cost of requirements errors
- Requirements engineering overview
- Characteristics of good requirements
- Explore the differences between requirements and design
- Evaluate requirements for effectiveness
- Factors to improve project success
III. Foundations of Requirements Development
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.
- Key terms in requirements development
- A strategy for analyzing systems
- Common requirement-classification schemes
- The three levels of a system
- Levels and types of requirements
- The importance of traceability
- Understanding the business context of projects
- Define key terms
- Use a framework to drive out requirements
- Types of requirements
- Classifying stakeholders' input
- Evaluate a fictitious but realistic organization for project alignment
IV. Project Initiation: Eliciting High-level and Mid-level Requirements
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 crucial business analysis activities by demonstrating common tools for identifying and documenting project scope, for modeling current and desired states, and for stakeholder and persona identification. And because effective initiation can lay the foundation for effective use case or user story development, we'll introduce use cases and user stories by identifying 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.
- Understanding product vision and project scope
- Identifying and describing project stakeholders and personas
- Modeling the business
- Analyzing the current state and defining the future state
- Identifying systems and actors
- Determining scope
- Understanding and identifying use cases and user stories
- Taking the Agile approach: writing user stories
- Identifying and defining data
- Documenting business rules
- Finding quality attributes
- Defining and documenting the project scope
- Modeling the business
- Brainstorming and affinity mapping
- User stories
- Context diagramming
- Use case diagramming
- Activity diagrams with swimlanes
- High-level data definition
- Entity relationship diagramming
- Writing business rules and quality attributes
- Evaluate a Scope Definition Document
V. Eliciting Detailed Requirements
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.
- Overview of requirements-elicitation techniques
- Decompose processes to lowest levels
- Document analysis
- Modeling processes to generate interview questions
- Interviewing the stakeholders
- Documenting the interview and resulting requirements
- Adding detail to requirements we already have
- Refining and rewriting for clarity
- Elicitation techniques—advantages/disadvantages
- Detailed process modeling
- Generating good interview questions
- Coping with challenging situations
- Interview simulations
- Writing new requirements and refining existing requirements
- Roles and Permissions matrix, CRUD matrix, and CRUD functional requirements
VI. Improving Requirements Quality
After we've elicited the detailed requirements for our project, we want to analyze and refine the requirements. 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 scope creep.
- Requirements quality
- Common problems with requirements
- Analyze for ambiguity
- Requirements inspection, analysis, and improvement
- Analyze and rewrite requirements
VII. Documenting Requirements with Use Cases and User Stories
Developing use cases is fairly straightforward, but someone actually has to document the use cases and requirements discovered during the requirements elicitation process. There is also an art to writing user stories and defining acceptance criteria for the requirements. This section of the workshop focuses on how to apply the knowledge you've gained so far to writing use cases and user stories. It also examines more complex aspects of uses cases, including sub-use cases and use-case linkages in larger systems.
- Better user stories using the INVEST model
- Defining acceptance criteria
- Decomposition of user stories
- Considering use cases for decomposing user stories
- Use case basics
- Ways to identify use cases
- Use cases and requirements
- Usage narrative
- Anatomy of a fully dressed use case
- Writing effective use case narratives
- Understanding sub-use cases
- Linking use cases for larger or more complex systems
- Use case quality
- Avoiding common traps and pitfalls
- Write acceptance criteria and perform peer reviews
- Decompose user stories
- Write a usage narrative
- Write a fully dressed use case and perform peer reviews
- Check use case quality
VIII. Packaging and Presenting Requirements
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.
- Organizing and packaging requirements
- Presenting requirements for review
- Baselining the requirements
- User story backlog management
- Managing requirements changes
- Getting to consensus and approval
- Conducting formal and informal reviews
- Documenting requirements in a Requirements Specification
- Examine and evaluate a sample Requirements Specification
- Discuss strategies for presenting requirements to stakeholders
- Review how to determine impact analysis for changes to the requirements
- Create a personal action plan for success
- Who should attend
Anyone involved in business analysis would benefit from this business analyst training course. This business analyst training course is perfect for you if you are a(n)…
- Business customer, user or partner
- Business Analyst
- Business Systems Analyst
- Systems Analyst
- Project Manager or Team Leader
- Systems Architect or Designer
- IT Manager/Director
- Systems or Application Developer
- QA Professional
- Systems Tester
- Anyone wanting to enhance their business analysis skills