Once you have a product vision that is clear, you can create the product scope.  This is different than the project scope, and sometimes the project scope does include the product scope.  Sometimes it is documented before a BA joins that team, but it may or may not have the information that a BA needs from a scope perspective to start analysis work.  You will need the product scope that outlines the user interaction scope point of view.  Sometimes a product scope is already documented but is a list of technical outputs or tasks, and this will not help you.  So, again, you may need to do some “playing with words” on this to not step on toes and get this scoping done when others think it already is completed.  Not doing this step will create issues down the road in your analysis!

Here is a Scoping Checklist to get you started on scoping, and a video on creating a Scope Model (also called a Context Diagram) as well!

Scope Model & Context Diagram Video:


Since your product vision and scoping activities should be agnostic of the exact solution, next you can do a Options and Alternatives Analysis and facilitate the team through possible options to meet the scope at a high level.  Here is a video to tell you more:


If all of this seems like a lot of work and there is no time for this due to pressure to “just get requirements done”, rest assured, you can do this quite quickly and while you are working on requirements.  You will need this information to do requirements correctly and without it, your work will slow down dramatically!

Lesson Content