Discussion Locked

bad contracts, bad consulting. How to change?

0 helpful
27 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Last year, the consulting branch of a university was hired to redesign and rebuild one of our main systems (I work for the government). Deadlines were missed, but the system is now "operational", but it doesn?t get close to user needs.

I found out that the system construction started without any documented specification approved by our management. So, today it seems there is no point for arguments like "This was in the scope!". As I mentioned, it was delivered much less than needed or expected.

Do you have any suggestions on how this could be changed? Unfortunatelly it seems the consulting manageres main concern is how to get their money, instead of how to help our organization improve.

27 replies

by sullyman

I have been involved in numerous development projects, starting as a grunt and workng my way up to CPM.

My first recommendation would be to develop a series of Key Performance Indicators (KPI's) that have to met and maintained. You can then leverage that information in your next performance update/meeting. Set realistic goals and objectives, on functionaliy and downtime etc.

by bigpicturedetails

Sullyman is right. KPI's. But you need to be clearer: As part of the contract, build in the discussion points of the progress milestones as payment go/no go realities. This way you see trouble well before the contract is over. As for your current reality: be honest-tell them they system is causing you pain, try to get them back at the table and see if they have any personal passion about building a better system. Suggest the alternative is you can't help but be badmouthing them to other prospective client's based on the facts.

by avernille

It seems the major issues are placed inside the organization I work for.

A second project was contracted with the same third party. It is following the same path. The documentation and specification produced are minimal. My organization has lots to learn!

I have not much experience with KPI. I think they would be important, but first my organization must "indicate" what should be done! :-)

by dilbert-tom

Sounds like someone wanted to 'hire' that consulting group - as opposed to have a Requirement fulfilled.

What bids were taken ? Was there any Requirement Definition documented ?

Sounds like you could use a different Consultant group - theres a difference between paying too much once, and paying too much again and again. You might even do better engaging Contractors to perform under your management, rather than allowing the 'Consultants' to 'Manage themselves', even consider hiring consultants from a different company to manage the contract help - rather than simply handing over your budget to one (already demonstrated to be marginal) Consulting group.

...Consulting Branch of a University... are these Students ???

In working as a Consultant with State Medicare/Medicaid system conversions - I've seen how all too often, the same group that just failed to perform is brought back to clean up the mess - over and over - rather than just cutting losses and starting over with a different group...

Take Bids on a Requirement, get Specifications with the bids - the bidding process will define alternatives and deliverables.

by avernille

We have considered before on bringing others to evaluate the service. However, the main knowledge (with the consulting group) was centered with a consulting manager that left the organization, due to the project failure!!

As the initial written contract is also very "open", we thought any discussions would be painless and unproductive. Is there a way around for a bid? Or could we try just "in talk"?

Finall, yes. Most analysts are undergraduate studentes. But notice the internal procedures impose a set of recommended consulting organizations.

by jmschattke9

As I mentioned elsewhere, no you can't try to make a contract just "in talk". Then, is there is a disagreement, it becomes "he said/she said" and you never get satisfaction.

What do you want? You want system X to do task Y.
How do you get it? Talk to the users about how they do task Y now, and work with the consultants to describe system X. You may need to pay them hourly during this period. Once that system is described (in a Specifications document), you can request bids to Design and Implement.

How do you get bids? FAX your Specification to 3 or 4 full-service consulting houses. They will give you a bid, or tell you your spec is not clear enough to bid on.

by jimhm

There job is to make money - not help you improve your organization - unless you pay them.

First - the organization needed to develope a specification document -

Second - The organization needed to get a statement of work from the contractor and agree to it.

Third - the organization needed to document and track the project

Fourth - They got what they signed for -

Your manager must be the dumbest thing since god put stained glass in an outhouse... How do you sign an consultanting contract without a statement of work - or product specifications - or anything... They seen him coming a mile away...

by david peake

If i'm understanding this correctly you now have a system that doesn't do what it was meant to do and the reason for that is the lack of any clear direction/specification?

If this is the case then it sounds as though you're stuck between a rock and a hard place. The consultants will want their money and, no doubt, without some form of payment being made they will be unwilling to continue development. Plus, getting into legal wranglings won't help the mess you're in.

My suggestion is to offer some form of payment (as non-payment always causes friction). This will show that you're willing to help them, and so, in turn, you should expect them to show willing to help you.

Invite the consultants back and try to develop a strategy whereby you'll get a system you want and can use and they get all their money (probably a bit more too).

PS. Make sure all this is documented (even down to the number of sugar cubes they have in their coffee)

by anandak

I know you must have received many suggestions by now, but to succeed even in future, assigning a job to third party or your own guy does not ensure the success until and unless it is in safe hands and you keep a watch on it - else you will be sure to have a suprise anytime

by sharky_2003

If you or someone in your organisation has paid a consultant to come in and achieve some goal or objective they also have responsibility for the project's success. Where were the project controls to ensure success? Project Board? Program Manager? Risk and issues logs? Defined phases of work?
Without these, in my opinion, your organisation is as responsible for the project's failure as the consultant themselves. Sorry.

You have two choices. Restart negotiations with the consultants led by someone from your organisation who understands project and programme management, or, look for a new consultancy but again, someone to lead the project from your side is essential.

Good luck

by netgen

1. By allowing the consulting group to proceed with building the system without a clearly specified and documented scope of expectations, your organization showed that it didn't care about serving its own interests. It is unrealistic to expect a third party to care more about serving them.

2. The consulting group delivered something. To the extent that the work they did was approved by whatever documentation exists, they are entitled to pay for their work.

3. Recognize and accept that the system design project is over and that you have a totally new project ahead of you, sadder but wiser (hopefully) that you are. The scope of the new project could range anywhere from modification/repair of the current system to a totally new design of one that functions the way you want it to. You have to be looking ahead.

4. Realize that this new project provides your best leverage over this consulting firm, provided that they still value having you as a client. They may be willing to renegotiate a new contract based on clearly designed specifications. The best attitude that can be taken by your organization in approaching the negotiations is by taking responsibility for the results of the just-completed project. A government organization actually accepting responsibility for its own incompetence might shock your consulting firm enough into providing a favorable proposal.

by dilbert-tom

If requirements were not clear in the RFP, and especially if the construction was allowed to start before specs were approved - you really have no recourse other than to pay the Consulting bill.

However, if something was learned - it was a cheap lesson. On the other hand, if your organization is willing to repeat the mistake, the lesson will become increasingly expensive and painful (as you will still not have requirements met, as well as the money wasted).

Someone needs to Manage the Consulting.

Functional Requirements can be a deliverable from the Consultants, if they are still not clearly documented - it would be worth some Consulting time to make them clear - make sure that you are clear about requiring approvel before continuing to Technical (Deliverable) Specifications.

Again, Consultants may be used to document clear and detailed Technical Specifications (and generally should include screen mockups, report mockups, input specifications, workflow documentation). Again, be clear that these must be approved before any Construction is to start.

Then you should have a Test Plan, even prior to actual construction - exactly what criteria will define success must again be documented very clearly, perhaps even to the point of hypothetical test cases and how they should process for the system to be considered "Acceptable".

If controlling Consultants is an issue, bring in another Consulting group to handle acceptance testing (make Consultants evaluate work of other Consultants and document success and deficiencies). Most often, once the developers are aware that they are going to be evaluated by clear criteria - they will fulfill that criteria (or will also realize that the clarity is sufficient to define outcome of any disputes about developing what was required.

Best way to handle deadlines is completion bonuses based on equally clear 'milestones', such bonuses might call for lower overall compensation for Consulting (to manage your total cost to be about the same as it would have been on an 'uncontrolled' fixed bid). Bonus sounds more like a 'carrot' than a 'stick' - but can serve both functions. Make darn sure that they are not going to be 'automatic', but rather are based on clearly demonstrated completion of major sets of tasks (like screen prints from a test, for example).

Management might not like the idea of bringing in multiple Consulting groups (one to 'control' the other), but point out the savings that can be realized vs paying for an uncontrolled development that may not only fail to deliver what was required - but may actually hobble the efforts by delivering something that may require more effort to run than if it was never developed in the first place. Mis-management can be much more expensive than no management at all...

by essfour

What you could probably do is to tell the consulting team, that we will definitley pay.
However the rider clause will be that they need to cooperate with you in drawing up a revised specification agreed upon by the end users.
This exercise can be taken up on a module basis.
The key thing in this would be that users will start understanding the situation and cooperate with you and the consultants in arriving at the acceptable requirement.

by sysdev1

You have obviously realized that starting a project without a well defined (and written) project definition is doomed to failure. There is no way to recover from this problem unless you can come to an agreement (yes, in writing) as to what needs to be done by whom and by when and who will perform what tasks and who will pay who and how much. An extreme 'example' would be Build a multi billion dollar nuclear reactor from some notes scratched on a napkin. This may not be that severe, but it is certainly in the same arena. The only way to recover from this is to start over with a full (agian written) requirements statement which includes everything and defines all roles and realistic deadlines. Without this, it WILL NOT WORK.

by dpipes

Clearly there were some steps missed in the management of this project, and others have pointed them out already so I won't go into detail, but I would clearly advise the following practices when engaging a 3rd party to develop software:

- Iterative Development: Look into RUP or eRUP (or EUP) to begin a new way of looking at software development projects. It won't be obvious initially why it is a better approach for software development, but a customized version of the methodology would have prevented this from happening in the first place.

- Traceability: Define the project with milestones that are tracable back to core requirements. This way, in an iterative approach, you can look at what's being delivered and draw a direct line to the requirement that initiated the effort. If the traceability isn't there, then you can react and delve deeper into it and correct the course of the project sooner, rather than later.

- Project Dashboards: Always ask your PM (if you aren't it) to provide a dashboard that indicates the overall health of the project. It can be as simple as a spreadsheet with color indicators to track milestones and key deliverables. This way you have a short document to look at daily, weekly, or whatever interval fits your style, that reflects the overall health of the project. It doesn't take a lot of time to develop nor does it take long to update, but it conveys volumes of information quickly.

- Test Early: Adopt a practice of testing early with users. Even if the user interface isn't perfect, you can put something in front of them to start getting feedback early in the iterations before the train is completely derailed by false assumptions or incomplete requirements. Take the feedback and drive it back into the requirements via an approval process (change management) with the primary stakeholders.

Beyond that, it is water under the bridge. It is now time to figure out if you can partner with the people who developed the "wrong" software and share in the losses. If you frame it from the perspective of "win-win" for both you and the University staff, it will often lead to better discussions and easier negotiations. Partner with them to solve the problem, if it is possible, rather than point fingers. You are where you are and damage control is all you can do now.

by zaferus

By talking to the consulting managers they only want their money - which is understandable from their point of view.

While your side not approving a scope or work details is a huge oversight on your part, it is also negligence on theirs. This I think may be your only card to play.

But you cannot champion this unless you have "executive" or "chief" in you title. The top (and I mean TOP) brass on each side need to sit down here and go through the shortfalls on each side (and neither side here is without error) and if I was your President/CEO I would go through all of the functionality that was "excpected" but not delivered then sit back, let an uncomfortable silence build then ask them what they think.

Maybe a compromise can be worked out, if both sides are willing to focus on salvaging this mess...

Zaf

by philmeeks

As a consultant, I have seen similar situations. The client shares responsibility with the consultants.

Clients are responsible for approving a clearly defined spec, and list of deliverables, and for monitoring the consultant to ensure the spec is followed and the delivery timeline is met.

The consultant is responsible for producing the work to meet the spec and delivered on time.

A client who fails to meet their responsibility should not blame the consultant. Instead, admit the failure and get busy defining the spec.

Consultants expect to be paid for their work. If the consultants made a good faith effort to develop something, they should be paid for all work actually performed, even if the results are not what the client wanted.

I recommend closing the books on the original project, settle up with the consultants, and move forward, this time with a spec, on a new project to correct the deficiencies that exist.

by mick.gov

If this is a government contract, you should have a paragraph that, basically, is a "satisfaction guaranteed" clause. Meaning - if the product is no good, even if "good" is ill defined, you do not have to pay until it meets expectations. If, however, you have accepted the deliverable, warts and all, then shame on you. Own up to your mistake and develop a plan to make things acceptable to the user. FI you are obliged to use the same contractor, leverage you government purchase power to get better rates for the makeover.

by avernille

The deliverables were accepted.

There were intermediate delivers, that could block payments also. But it was all accepted and signed off.

by martin_ternouth

I suggest that this went wrong thirty seconds into the very first
phone enquiry. Never hire a consultant to redesign or rebuild a
system. Instead, you need to say "We have these business needs
that are not being fulfilled: please demonstrate how we can
meet them in future". You need to define the problem in terms
of what is missing, not in terms of what you think you will get if
a particular solution is chosen.

With the situation as it is now you have two choices. Write it off
to experience and find someone else (this may be the cheaper
option in the short term), or start a dialogue with the
consultants and use all your negotiating skills and threats and
inducements to get them to put some things right at the lowest
cost they'll do it for. You won't (from your brief description) win
a lawsuit so it is all down to what pressure and leverage you
have.

When dealing with consultants you must know more of detailed
history of their assignment than they do. Record everything on
a wallchart a metre high and several metres long - (Excel is a
good tool) and keep it updated every week, and written on every
day. Then when they come back in month six and say that they
are repeating some 10 days work for roll-out based on the 10
days work for the pilot you can swoop back across the room and
point to the promise they had forgotten that says that 10 days
instead of 5 in month one would mean 2 days instead of 10 in
each of months 6 to 9. Only with a wallchart will you retain that
sort of knowledge by glancing at it every time you go to the
watercooler.

by jmschattke9

I found out that the system construction started without any documented specification approved by our management.

Well, there's your problem in a nutshell. The Spec is your software P.O. with a consultant, and you game them a "verbal". Is it any wonder it does what the consultant felt it should?

Do you have any suggestions on how this could be changed?
1) Always get it in writing, and signed off by both sides. A professional should have NEVER ACCEPTED the job without a spec, because it leads to bad blood on both sides. But if the consultant won't finish a spec for you, you've got to do it yourself.
2) User interaction is key; get your final users involved from day 1. If the system is made to a spec which the users don't know about, it's extremely likely to not meet user needs. Workshops, brainstorming sessions, even a suggestion box help.
3) Milestones. One reason that a project comes in late is that the consultant is not sure what needs to be done by when; milestones help, and give you a sense on whether the system is on track or not. Good milestones are DB setup, GUI description, alpha test (raw code, to be run on a test system with faked data), and beta test (first run with active data and partial loading).

by wolgastd

In a nutshell, it sounds like you bought a pig in a poke.
What WAS in the contract? (a blank check maybe) First, there are several different Software Methodologies and many books have been written on them. Suggest that you eat it and pay the previous contractor if nothing in the actual contract has deliverables clearly defined. Then you should insist in any future contract that the consultant use a specific and accepted development methodology (or propose one to use if you don't have a local standard one). All of these address such issues as 1) functional requirements definition (maybe including a business process model), 2) technical specifications (including environment specifications), 3) development (including language and tool definition and adherence to local standards and policies - in writing), 4) test criteria and testing, 5) acceptance criteria, implementation, etc., and some use iterative methods. Note that separate contracts can be issued for some of the above and all should have milestones and deliverables on a timeline. If you are going to contract out the functional and technical specs, then that should be done separately because the remaining are dependent on them. You need seasoned people in your organization to manage the contract and significant participation from your functional users throughout the process. Without that there will be misunderstandings even if you have written specifications (there are always shortcomings in specifications). Remember that the only way to measure success is by comparing the result with what the specs asked for. In the government you can consider different types of contract "vehicles" as well, e.g. firm fixed price, base plus performance bonus, time and materials, task order contracts, etc. Look at the different types of contract vehicles to determine which best fits your current needs. If possible define the contract in increments of approximately 6 months duration that can be extended with contract modifications (up to a level of funding available). If you are "sole sourcing" the contract then you can use contractors that you have confidence in but that requires justification. If the contract is out for bid, then request details about the contractor and the experience levels of the staff they propose in the request for proposal to the bid (being careful not to specify specific people - just skill levels, any certifications or educational requirements, and experience) in addition to the description of the the purpose of the contract. There's actually a lot of work involved on your end as a "full participant" with the contractor "as a team". Note: If you don't feel comfortable with a contractor its a good idea to keep the contract timeframe short so you can get rid of them. If you have established a long relationship with the contractor and they have performed for you in the past, then still don't let them have free reign - control the project yourselves. Also, for custom system development, I would recommend that the contract specify that the government will provide office space, tools, equipment, and materials and the work be done "on-site" if at all possible. If you can LOOK at each other things seem to work better.

by rick

I'm very recently (lastnight) in between engagements and have a soft spot in my heart for education. Loads of experience in the situation you are now in.
Can you call me at 360 413 0575? We can talk through some actions you can take to pull out of the quagmire.
Warm regards,
Rick Walker
PMP
Faculty member, Chapman Univ. grad school, South Puget Sound Community College
Olympia, WA

by danpgov

I recommend a meeting with all affected parties / stakeholders to conduct a post mortem. The ideal chair person should be neutral. The deliverable of this meeting should be s document listing "What went wrong?", "What can be done to resolve the problems and the cost implications?" Your Consulting Partner will have to come to the party with sharing some of the costs to recitfy or resolve any identified deficiencies.

by mkhanjani

I think you should write a complete service level agreement(SLA) in detail.And make another contract for blocking more loose!

by rdbennett

If you're asking what you can do to salvage the situation, I think you've seen the right answers here already. You're going to have to renegotiate the contract, or find something in the existing contract that will provide leverage over the performers. You may want to consult your legal advisors to see if they can come up with something. After all, most universities are beholding to the government for funds, and that may be a card the legal beagles are able to play.

For the future, your organization needs to understand how to go about contracting for products and services, and that should be done -before- you renegotiate.

Your organization isn't alone in this thing, it happens a lot. Another government organization, the DoD, has some experience going down this road. In an effort to avoid this, and to achieve some significant economies, they revised the acquisition process. You can see nearly all the materials at http://dod5000.dau.mil/index.htm.

Good luck.

by ellen.walker

The Data and Analysis Center for Software (DACS), a DoD sponsored Information Analysis Center, maintains a Gold Practice website, (www.goldpractices.com)which addresses effective practices for software acquisition and development. There you will find detailed information about topics such as Acquisition Process Improvement, Managing Requirements, Testing, and other software related practices.

Many of the suggestions offered by discussion participants in this thread are included in the Gold Practice website.

Please let me know if you find this site to be useful.

This discussion is closed to new replies.