Your Cart Is Empty
Professional Development Skills >
Business Analysis >
Business Analyst Boot Camp
This course gives you hands-on experience with the latest proven techniques for identifying a project's scope, developing and discovering requirements cases, and documenting them expertly.
This 4-day Certified Business Analyst Boot Camp 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. In the Business Analyst Boot Camp, you will 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.
Lesson objectives help you become comfortable with the course, and also provide a means to evaluate learning. In the Business Analyst Boot Camp, you will learn how to:• Identify the essential skills of a Business Analyst• Analyze the business environment in which your project occurs• Improve your requirements elicitation, development, and documentation• Enhance business analysis techniques to reduce project cost• Practice eliciting and validating information from project stakeholders• Develop business model components such as a context diagram, activity diagram, and use case model• Work as a team to analyze business artifacts and documents to discover the functional requirements needed• Write user stories and acceptance criteria• Produce well-written use case diagrams and narratives• Generate a plan for bringing these methods back to your organization
The Business Analysis ProfessionIt'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.1. IIBA® and the BABOK®2. What is Business Analysis?3. Business and Solution Domains—how they relate4. Key roles in requirements development5. The competencies of the Business Analyst6. Distinguishing novice and expert Business Analysts7. Effective communication8. Six important BA skillsPractice sessions:• Business analysis definition• Competencies of a business analyst• First look: generating good questionsII. The Business Case for Good RequirementsIT 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.1. What is a good requirement?2. Requirements attributes—who needs them?3. Key practices that promote excellent requirements4. The cost of requirements errors5. Requirements engineering overviewPractice sessions:• Requirements definition• Characteristics of good requirements• Evaluate requirements for effectiveness• Factors to improve successIII. Foundations of Requirements DevelopmentIn 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.1. Key terms in requirements development2. A strategy for analyzing systems3. Common requirement-classification schemes4. The three parts of a system5. Levels and types of requirements6. The importance of traceability7. Understanding the business context of projectsPractice sessions:• Define key terms• Use a framework to drive out requirements• Types of requirements• Classifying stakeholders' input• Evaluate a mythical but realistic organization for project alignmentIV. Project Initiation: Eliciting High-level and Mid-level RequirementsWhat 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.1. Understanding product vision and project scope2. Identifying and describing project stakeholders3. Modeling the business4. Identifying systems and actors5. Determining scope6. Understanding and identifying use cases7. Taking the Agile approach: writing user stories8. Identifying and defining data9. Documenting business rulesPractice sessions:• Modeling the business• Actor/goal identification• User stories• Context diagramming• Use case diagramming• Activity diagramming• High-level data definition• Writing business rules and quality attributesV. Improving Requirements QualityAfter 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.2. Requirements quality3. Common problems with requirements4. Analyze for ambiguity5. Requirements inspection, analysis and improvement6. Defining and documenting the project scope
Practice sessions:• Analyze and rewrite requirements• Evaluate a Scope Definition DocumentVI. Eliciting Detailed RequirementsSavvy 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.1. Overview of requirements-elicitation techniques2. Decompose processes to lowest levels3. Document analysis4. Modeling processes to generate interview questions5. Interviewing the stakeholders6. Documenting the interview and resulting requirements7. Adding detail to requirements we already have8. Refine and rewrite for clarityPractice sessions:•Elicitation techniques—advantages/disadvantages•Detailed process modeling•Generating good interview questions•Coping with challenging situations•Interview simulations•Writing new requirements and refining existing requirements•CRUD matrix and CRUD functional requirementsVII. Documenting Requirements with Use CasesDeveloping 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.1. Use case basics2. Ways to identify use cases3. Use cases and requirements4. Usage narrative5. Anatomy of a fully dressed use case6. Writing effective use case narratives7. Understanding sub-use cases8. Linking use cases for larger or more complex systems9. Use case qualityPractice sessions:• Write a usage narrative• Write a fully dressed use case• Check use case qualityVIII. Packaging and Presenting RequirementsOnce 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.1. Organizing and packaging requirements2. Presenting requirements for review3. Baselining the requirements4. Getting to consensus and approval5. Conduct formal and informal reviews6. Documenting requirements in a Requirements SpecificationPractice sessions:• Examine and evaluate a sample Requirements Specification• Present requirements to stakeholders• Create personal action plan for success
Entry Certificate in Business Analysis (ECBA™)
There are no formal prerequisites required for this course.WHO SHOULD ATTEND• Systems, business, and requirements analysts• Developers• Software engineers• IT project managers• Project managers • Anyone who supervises business analysts and are responsible for business analysis activities, project analysts, project leaders, senior project managers, team leaders, program managers, testers, and QA specialists
Productivity Point Learning Solutions
evolved out of a desire to increase our outreach
both nationally and internationally.
Productivity Point Headquarters
1580 Sawgrass Corporate Parkway
Sunrise, Florida 33323