Stopping The Unending Creep Of The Unspecified Scope
Tags: data, analytics, dataanalysis, bi
Published: 2018-11-20 16:18:57

---
title: Stopping The Unending Creep Of The Unspecified Scope
published: true
description: Stopping the inevitable scope creep on analytics and BI projects.
tags: #data #analytics #dataanalysis #bi
canonical_url: https://alanhylands.com/the-unending-creep-of-the-unspecified-scope/
cover_image: https://simpleanalytical.com/wp-content/uploads/2018/05/columbo.jpg
series: Frustrations Of The Data Analyst Life
---

<h2><strong>So who are we dealing with here?</strong></h2>

I call them the <strong>Lieutenant Columbo</strong>’s. The folks who, when they get exactly what they asked for, always find “<strong>just one more thing</strong>” to stick onto the request.

The cheeky little addition with a wink emoji on the email.

Room for a little one? ROFL. LOL. Cheers mate.

Just a “<em><strong>quick easy one that won’t take you too long</strong></em>” as they completely revise the whole thing you and the team have spent a week working on and they had never mentioned at any stage of the requirements gathering process.
<h1><strong>AAAAAAGGGGGGHHHHHHH!!!!!!!!</strong></h1>
&nbsp;

**As a species we always want more.**

We’re hardwired to it and just as entrenched in the general corporate drone’s DNA is the complete inability to cover off every eventuality for what they actually need at the point when they are supposed to ask for it.
<h2><strong>Can I learn how to put a stop to scope creep?</strong></h2>
I’ve read countless articles from freelancing and consulting experts who set out specific ways to gather requirements, set milestones and project plan using Agile or Lean methodologies.

Anything to ensure scope creep doesn’t derail the profitability of an assignment or a project.

In my own experience, building a robust work request and requirements gathering process is one of the main tasks for an analytics manager if they want to reduce scope creep.

Discovery is everything.

Making sure it works equally well for both the business stakeholders and the analytics team is the difficult part.
<h2>Wearing many hats</h2>
Leading that process will see you become, interchangeably, at a moment’s notice:
<ul>
 	<li>The font of all business knowledge (even for the requestor’s own business area)</li>
 	<li>Their therapist (like Dr. Frasier Crane, you’ll be listening and spill their guts they shall)</li>
 	<li>Their priest (see the therapist but now you offer absolution and penance, lots and lots of penance)</li>
 	<li>Their prophet (seeing into the short, medium and long term future for any possible changes that can derail your whole plan).</li>
</ul>
It’s not a job for the faint of heart but by doing it properly you’ll deliver one of the main gifts you can bestow on your analyst team:
<h3>The gift of effective air support against unnecessary internal attack <strong><em>PLUS</em></strong> a well specced out, signed off set of requirements to work to.</h3>
If you half ass it at this point it will keep biting your own ass and that of your team potentially for weeks or months ahead.

Pay it forward to yourself. Future You thanks you kindly.
<h2><strong>What Do You Do If The Inevitable Creep Happens Though?</strong></h2>
I quoted Rob Collie and Avichal Singh in [Frustration #1](https://simpleanalytical.com/veruca-salt-and-the-just-give-me-everything-routine/) and am considering getting their line tattooed across my front, Tupac-style, just so it’s always close at hand:
<blockquote>“Human beings do not know what they need until they have seen what they asked for”.</blockquote>
No exaggerating but that is the quote I’ve been waiting for my whole working life when it comes to dealing with business users in a service capacity.

The hardest part is overcoming your natural hatred of their guts for derailing your whole perfectly planned process and having to go back a few steps before you can go forward.
<h2><strong>How do we deal with it though if it’s pretty much inevitable?</strong></h2>
Best I can say is to prepare yourself for a Phase 2 to every request and view it as a necessary iterative step to getting your customer to the place they really need to go.

We all want a successful outcome, sometimes it just takes a little longer to work our meandering way there than we might want.

This applies doubly if you’re in a team which is under the cosh constantly in terms of fending off an inordinate amount of MI requests.

Sometimes we can be victims of our own success but it’s no reason to half-ass a job just to get it cleared off the stack early.
<h2>One step at a time</h2>
If you view the first initial customer-led request as the first draft and the analyst-led discovery stage as the second, there is no reason not to take a third pass once the analysis has been completed and see what we have learned and can further dig into.

Write it up as a new request by all means to bump your numbers if it makes you feel better but don’t shy away from it – provided you did your job correctly in the requirements gathering phase.

If you didn’t, **you really have no-one to blame but yourself**.