1. Too many systems integrators (SIs) - if, like economic theory, we assume free trade benefits all parties then maintaining open exchange of ideas and expertise is crucial; recognising the enterprise programme will benefit only through collaboration amongst dependent parties. Theoretically many SIs on a project should compete away differences to leave an implementation of the greatest benefit to the client, but this has long been disproved by the 'power elite' theory. Most often SIs seek absolute power advantage over one another in their relationship with the client. Projects suffer, not just economically, where the client is unclear with SIs over division of roles...
2. Off-shoring tasks on the critical path in a development lifecycle - this can work, but importantly the offshore team should have some understanding of the business area for whom they are developing, the stronger the better. As a programme management team the answers to the following questions about the capabilities of your off-shoring team are helpful to clarify:
- If using an SI off-shore, are their goals suitably aligned with the programme?
- Where difficult development challenges arise, can the offshore team think critically to resolve them?
- Are their solutions of genuine benefit to the client?
- Are you getting them for the right price?
- Even if you've answered 'Yes' to these questions, ask yourself 'Does all this sound too good to be true?'
An offshore strategy can become increasingly difficult to justify...
3. Hand-offs between competing SIs engaged in the release and testing process - competing systems integrators were engaged to separately handle release and configuration management, where initially there had been one. These ITIL aspects of any programme are so closely related, introducing a hand-off in this area mostly adds time, without bringing efficiency; while the use of competing SIs here brings an unnecessary period of professional 'sabre-rattling' as all parties are encouraged to get along well for the benefit of the client. Keep it simple here; there are hidden costs in too many hand-offs!
4. When the going gets tough, which team members stand up - under time pressure, or faced with challenging tasks is the client still able to rely on all the team members to continue getting the job done? It's under these circumstances the quality of staff is revealed:
- Do they look for the right answer, or the quick answer? These are often not the same.
- Can they produce suitable quality despite added pressure?
- Is the work well documented and
- Can they still transfer the knowledge to others?
- Despite the sales pitch, does the individual consultant have the basic skills required?
- How well do the consultants interpret the information provided to them?
- When confronted with a challenge would the consultant choose the 'quick fix' or the 'best fix'?
Finally, question if the client has the right skills to competently assess the quality of the consultant. Without that, your programme will be in trouble.
Its important to remember that Adam Smith's view of capitalism - where the individual rises above their self-interest for the benefit of others - does not apply here. You'd do we'll to get an unbiased view when starting your programme.
I write a blog under the pseudonym DR. OBI. Feel free to get in touch with me about your programme. You can find me here Justin Townsend.