top of page

BA Word of the Day - Out of scope (OOS)

3 hours ago
2 min read

Out of scope (OOS) meaning that it's not included in the current scope. Or in current timelines. Or in the current release or launch.


Why Out of Scope Matters for BAs


Understanding what's out of scope is probably as important for any BA as understanding what is in scope.


Unfortunately, it's very often that we see BAs don't capture explicitly what is not in scope. That leads to all sorts of ambiguity and misunderstanding.


Remember, it is always better to be clear and precise and very upfront with what is out of scope. Do not be afraid to put it on paper, in writing, and confirm it with the client.


So how do you do it?


Next time you put together functional requirements documentation or a Confluence page for a certain module - let's say it's checkout - or even a user story, think (or ask an AI model): what is it that's relevant, but not included? Could be certain validation that's not here, or an additional section on the page, or the order details that are not to be included in the invoice form.


Then add a section. Just call it exactly: Out of scope. And list out things that are not included. Then verify it with your technical team and with the stakeholders, so that everybody's clear what's included and what's not.


Example of an Out of scope section in a Jira user story

And don't be afraid of being seen as strict, or harsh, or even negative. Your job is to ensure that there's no ambiguity.


How to Use Out of Scope in a BA Interview


In a job interview, bring up a story where the client was bringing up ideas and requirements that were absolutely valid - however, they were out of scope. And how you worked with your stakeholders and the delivery team to find the common ground.


When was the last time you actually wrote an Out of scope section, instead of only listing what's in scope?



Before you go, my friend, I invite you to join my free BA Promotion Roadmap: From Junior to Lead. There I go through the various steps and stages of business analysis roles - from junior, to mid-level, to senior, to lead and beyond - and what it takes to build a career in business analysis. More specifically I teach how you focus on a 3-step career development cycle - Deliver great results, Tell people about your achievements, Repeat and stay consistent.


BA Promotion Roadmap: From Junior to Lead - free training for IT business analysts

Talk soon, Sergey

 
 
 

Comments


bottom of page