Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "Putting together a statement of works and quote to build"
Sounds like you missed out on 200k of benefit-orientated design, engagement and business change consultancy.
Actually. I've estimated that it would take me 3/4 months on my own to develop. But of course this is a Corporate and so 'point solutions' are not in scope.
Hence a much larger cost! If it comes off though, thats me sorted for another 18 months.
If you use Agile you get 50% contingency in Feasibility and then by the time you get to foundation you should be down to 10% due to work done during these phases to refine the solution...
However why is people look at a project and the first thing they do is ask about cost...
better bet is to look at what you want the outcome of the project to be, look at what the expected benefits are (not just cash but 'soft' ones too) and then decide how much you are willing to pay for it...
Makes things some much easier
I was then asked later if they could review the solution in detail. My head went in my hands.
Last edited by MarillionFan; 20 December 2011, 18:38.
If you use Agile you get 50% contingency in Feasibility and then by the time you get to foundation you should be down to 10% due to work done during these phases to refine the solution...
However why is people look at a project and the first thing they do is ask about cost...
better bet is to look at what you want the outcome of the project to be, look at what the expected benefits are (not just cash but 'soft' ones too) and then decide how much you are willing to pay for it...
Was asked to review an SOW and the underlying project plan/costs for a new bolt on to their existing CMMS system, and so to compare to a buy/license option.
A detailed project plan was implemented. Going to each minute detail. A preliminary model designed, the resources, time involved, different costs etc and the build cost of £450k was mooted, which was high. Everyone agreed.
I then reviewed and pointed out some fundemental issues with it and that some assumptions were wrong. Reworked the whole thing over the last two weeks with the team and when completed I put in the new quote/proposals of £280k which included very generous resource plans plus a 10% contingency.
Just done the review with the stakeholders and it finished with them going. Seems a but low they said, lets call it £500k just to be sure!!! And they all agreed.
FFS!
What is the point?
Because you are confusing the technical answer with the political one.
For instance:
Building a server if left to a techie comes down to 3 days max but when you then allow for raising purchase orders, delivery to the DC, having DC access granted for your engineer, documenting the solution, signing off the installation, installing the software and so on. that three days blows up in a big way.... For instance EDS used to have an SLA with one of my previous customers that ran into a month of work to install a single 1U server....
There is also the valid point that your budget holder would like to come back to the Finance Director and say: "Hi we are all done and under budget by £2-300K" Not "Oh crap! Please can I have another 300K to finish that 200K job please?"
So asking for 500K to perform a 200K job is a very career aware way to do it
Putting together a statement of works and quote to build
Was asked to review an SOW and the underlying project plan/costs for a new bolt on to their existing CMMS system, and so to compare to a buy/license option.
A detailed project plan was implemented. Going to each minute detail. A preliminary model designed, the resources, time involved, different costs etc and the build cost of £450k was mooted, which was high. Everyone agreed.
I then reviewed and pointed out some fundemental issues with it and that some assumptions were wrong. Reworked the whole thing over the last two weeks with the team and when completed I put in the new quote/proposals of £280k which included very generous resource plans plus a 10% contingency.
Just done the review with the stakeholders and it finished with them going. Seems a but low they said, lets call it £500k just to be sure!!! And they all agreed.
Leave a comment: