How to accept a project from completed to maintain

Question

0.00/5 (No votes)

See more:

Well it's a long story, but im going to keep it short.
The business I work for started a new .net (c#, sql, web) project and decided they wanted to outsource the project instead of using the in-house development team (dont ask).

Four months into the the project I was asked to carry out a 'design review', I reported back tp the directors of the business with my findings, I advised them that the project costs were $150k spent to date and so far was the code itself was a complete shambles, they dismissed my findings and decided the way to solve it was to throw more outsourced developers and money at the problem (another story)

Anyway, they continued on this path and delivered the first phase of the project 3 months later costing so far $400k.
The project's main features are about to be completed and they want to hand the project over to my team, however I have no experience of handling a project from "Development" to "Maintenance" and ive been asked to produce a sign off process,
So my question is what should I be looking at and agree on when the project can be handed over to my team that will continue to develop it, Suggestions?

DW

Posted 9-Jul-14 5:44am

ziwez0

Add a Solution

Comments

[no name] 9-Jul-14 11:50am

Personally, I would not sign off on accepting maintenance of a project that was not "development complete" AND in a maintainable state.

ziwez0 9-Jul-14 12:11pm

LOL, I totally agree, the project was shipped 3 months late, and they had to strip it back as well, so technically its 5 months late and counting.

Unfortunately the directors will never admit they are wrong and that they should of listened. I just need to ensure that I protect myself\team from taking on a piece of **** project as much as possible.

[no name] 9-Jul-14 12:25pm

If I was you, I would document the #$@#% out of the code base detailing as much of the problems that I could and give a fair but brutal estimate for what it would take to fix the code. Then present that to your management.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2014-07-09T08:47:00

Do you have any specification documents on what needs to be working before you accept the project? Are all of these items complete and verified working by your internal testing team?

If not, there is no hand off.

Also, this list is not a short "this form does this" paragraph with a couple of sentences in it. It's a very detailed list of what every form does, what every control does, what every piece of business logic does and how it relates to other pieces. Without this, how did the outsource copmany even know what they were writing for?

I'm not trying to bash you on these statements, but what you're talking about is a LEGAL proceeding, not a technical one. The question you need to answer is "did the vendor deliver what was agreed upon?"

There has to be some kind of agreement in place that speels out in explicit detail exactly what your requirements are, what you findings with the product are, and what the vendor is going to do to fix them and on what schedule.

Without this stuff, your company is spending large sums of money with no accountability at all and that's bad for business, pisses off investors and drives lawyers ape-sh*t.