I call them the Lieutenant Columbo’s. The folks who, when they get exactly what they asked for, always find “just one more thing” 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 “quick easy one that won’t take you too long” 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.
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.
Can I learn how to put a stop to scope creep? permalink
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.
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.