This post is the second in a series of four about estimating project hours. |
Continuing our dive into project estimating, let’s talk about two more problem areas: dependencies and project creep. These two can turn your pristine project plan into a tangled mess.
No matter the size or scope of your project – whether you have just a few dependencies or tight integration with multiple systems – you’ll be faced with sneaky requests. They may start out as good intentions but they can erode your plan, leaving your project teetering on the edge of a sinkhole.
Everything and the Kitchen Sink – Dependencies & Follow-Through
In large digital projects, the possibilities for functionality and integrations are endless – but time and money aren’t! Your team may dream of a high-end Mediterranean cruise, but the budget says you’ll be camping in the backyard this summer.
Trying to squeeze in “everything and the kitchen sink” can sink your entire project! In a client/agency relationship, this tension is real. Palpable. Clients want as much as possible, while agencies have to balance the extra work required – not just to build it, but to test and support it too. This is why many digital teams opt for MVPs (minimally viable products) and agile project management! Focus on the must-have dependencies and save the nice-to-haves for later.
Tough conversations are unavoidable – dodging them only makes things worse. Nail down expectations early. Spend the time upfront to follow-through on unresolved discussions (making sure the client feels heard) and setting realistic boundaries (ensuring the agency isn’t expected to perform miracles).
I’m a Creep – Scope Creep Management
In the immortal words of Radiohead, “But I’m a creep, I’m a weirdo. What the hell am I doin’ here? I don’t belong here.”
As a project leader, you have to be firm when a request doesn’t belong in the project scope. This is tough! Most of us are people pleasers, and no one wants to be the department of ‘no’. But we all know that “just this one little thing” can unravel an entire project. Beware of the word “just” – it’s sneaky!
This is where SOWs (statements of work) and CR (change request) forms save the day! They set clear boundaries: this is what we agreed on, and any extras will cost time or money.
I have seen new team members join after a website launch, making demands for flashy UI/UX, extreme accessibility, top-tier security features. They always make it clear that they expect all new sites to have these things. Without a well-defined scope of work, the agency is left with a black eye. But with a clear SOW it can be understood that this is what we agreed on and anything else is out of scope.
Conclusion
To keep your project on track, start by broadening early discussions to cover all possible dependencies, then narrow your final scope to avoid project creep from sabotaging your success. Perfection may not be worth the squeeze.
It’s not easy, but avoiding conversations will only cause more pain. As Abraham Lincoln said, “If I had eight hours to chop down a tree, I’d spend six sharpening my axe.” Enter every new project well prepared! It will save you time in the long run.
……
If you are looking for a partner who is well prepared, reach out to your Perficient account manager or use our contact form to begin a conversation.
This post is the second in a series of four about estimating project hours. |
