With information from elicitation in hand, business analysts must compile their findings into useful forms and leverage it to meet objectives. In this course, learn how to develop and model requirements, document solutions, and address business needs.
No matter how well information is elicited or how beneficial a solution may be, business analysis cannot succeed if requirements aren't effectively written, structured, or understood. In Conducting Business Analysis & Developing Requirements, you'll gain the ability to transform information gleaned from conversations and analysis into a plan for success. You'll learn about a variety of useful techniques for modeling scope, processes, rules, data, and interfaces. Then, you'll learn how to effectively write, document, structure, and prioritize requirements. Finally, you'll learn how to take your solutions documentation through validation and approval, so that project work can begin. When you're finished with this course, you'll know how to use models to better understand and communicate challenges and use simple rules and structures to convert those findings into a clear path forward.
Casey has experience leading projects in many fields, including healthcare, digital media, mobile app development, consumer product design, education, and event management. He's constantly in pursuit of new challenges and loves to share what he learns along the way with others.
Course Overview Hi everyone, my name is Casey Ayers and welcome to my course, Conducting Business Analysis & Developing Requirements. I'm a Project Manager and Strategic Consultant with experience in a variety of fields. I'm also the author of Pluralsight's series of PMP Prep courses, and it's my pleasure to now explore the world of business analysis with you. Business analysis is increasing vital to today's business environment. By identifying problems and opportunities, discovering and recommending solutions, and fostering a comprehensive understanding of stakeholder requirements, business analysts can help organizations choose and structure projects and initiatives more effectively. This course is the fourth in a five-series course on business analysis. Some of the major topics that we'll cover include exploring a variety of useful techniques for modeling scope, processes, rules, data and interfaces. How to effectively write, document, structure and prioritize requirements. And, how to take your solutions documentation through validation and approval so project work can begin. By the end of this course, you'll know how to transform information gleaned from conversations and analysis into a plan for success. Before beginning this course, you should have an interest in business analysis, and at least a bit of exposure to project management, or business analysis within your organization. This course, and others in the series, can help you not only learn more about business analysis, but also prepare for business analysis certifications like the CBAP, or PMI-PBA. Or, earn continuing education credit toward certifications like the PMP. I hope you'll join me on this journey to learn more about business analysis with this course on conducting business analysis and developing requirements here at Pluralsight.
Models in Business Analysis Essential to our ability to conduct analysis are the various models that we find at our disposal. In this module, we're going to take a closer look at what the purpose of models are, and how they can be effective and helpful for us. What type of models we have available at our disposal, how to choose effective models based on the type of analysis that we're undertaking, and the language of modeling. Some of the standards out there that might apply to your organization and help you more effectively both conduct analysis and create models as well as communicate those with others. Let's get started.
Exploring Scope Models Welcome back. In this module, we're going to begin diving deeper into modeling, looking at the specific types of models available to us beginning with scope models. Scope models can be helpful in organizing, understanding and communicating goals and objectives, features and functions, as well as the boundaries of where our focus should lie and on what areas we should leave out in order to ensure that our work remains efficient and aligned with the needs that we're trying to address. In this module, we're going to look at goal and business objective models followed by ecosystem maps, context diagrams, features models, and use case diagrams. We're also going to introduce an example that's going to apply for the rest of the course. We're going to use a sample business analysis case that we can apply all of these different types of models to. Let's get started.
Utilizing Process Models Welcome back. Now that we've discussed scope models, it's time to move on to process models. Process models help to spotlight and provide valuable context to the interaction of stakeholders with processes, solutions, and projects. In other words, process models help us to understand how the work of the solution gets done, how we go from A to B using the solution that we're creating. So, in this module, we're going to look at a few different types of process models, beginning with process flows, before moving on to use cases, and user stories. Then we'll look a bit more in-depth at user stories in particular, and see how we can craft particularly effective ones that can best convey what it is we're trying to accomplish, and the specific requirements necessary to meet those objectives successfully. Let's get started.
Validating, Verifying & Approving Requirements Up to this point, we discussed elicitation, analysis, modeling, and documenting. Now it's time to move onto the final portion of this step of business analysis, and that's validating. Validating helps us ensure that solutions will meet their intended needs, and that stakeholders have been effectively understood throughout the elicitation process and when speaking with them throughout analysis and modeling, as well. Ahead in this module, we're going to look at the concepts of continual confirmation, as well as requirements walkthrough, peer reviews, inspections, approving requirements, and resolving requirements conflicts. Let's get started.