It was painful. I picked up the phone and slowly punched in the ten digits.
Seconds seemed to turn into hours as I crossed my fingers in hopes for the sweet muffled tones of his voicemail; but of course, I wasn’t that lucky.
“Jared, what could I possibly do for you today?” the jovial voice exclaimed.
I quickly cleared the frog that danced in my throat and began to think through the different ways this conversation could go.
Before we dive any further, I want to point out that the experience I am referencing was prior to my time with Brilliance. The conversation I was about to have still remains one of the most frustrating and disappointing positions I’ve ever been in.
Just a few months prior, I had sold the customer on the idea of launching a completed product at a specific price. Now I was approaching that same customer about busting open the checkbook so that we could continue working on the project, which had run through its budget and still wasn’t ready. I wish I could tell you that this request for additional funding only took place one time, but unfortunately, that was not the case.
After returning to the well numerous times, adding dozens of features, scope creeps that would make a fleet of project managers cry and we finally had reached launch day. Only, launch day was 1.5 years later and the project costs had risen an additional 90%.
A quick Google search and a few articles later, it became very apparent that IT projects commonly fall victim to delays and increased costs. According to the Harvard Business Review, one in six IT projects has an average overrun of 200% and a schedule overrun of 70% (1).
To take it a step further, these IT projects end up delivering 56% less value than expected (2).
There was copious data supporting failed IT projects, but very little to be found about solutions to remedy these situations. Never wanting to find myself in that situation again, I have been on the lookout for a way to prevent project overruns.
At Brilliance Business Solutions, I found myself leading the sales team for an organization that uses a simple, yet effective way to combat failed IT projects before they even start: paid scoping projects.
I know what you’re thinking. “Isn’t that something that should be completed before the start of any IT project?” You would think that would be the case but unfortunately, it’s not.
No matter who performs your scoping project, the resulting report should include:
- Requirements: Detailed documentation uncovering every facet of the problem, as well as the accompanying solution.
- Schedule: A time frame based on the hours required to implement the chosen solution.
- Price: An itemized quote based on the defined requirements
After completing a paid scoping project, we guarantee the cost and schedule. Delivering an on-time and on-budget project requires work and commitment from both sides. If you hold up your end of the bargain, we’ll hold up ours. Period.
When an IT project fails, all parties involved lose. Eliminate the stress of the unknown and invest in the peace of mind a paid scoping project provides.
- The average large IT project runs 45% over budget, 7% over time, and delivers 56% less value than expected. (Project Management Institute: Pulse of the Profession 2015: Capturing the Value of Project Management 2015)
- One in six IT projects has an average cost overrun of 200% and a schedule overrun of 70% (Harvard Business Review: “Why Your IT Project May Be Riskier Than You Think”)
