Sunday, 30 May 2010 00:00

Outsourcing: Being the System Integrator

Rate this item
(0 votes)

The system integrator is the magical troupe that works with the customer and the software vendor to deliver a project's desired functionality. They cut through the vendor's promises while controlling the customer's expectations to create a successful deployment. Mike Krigsman refers to this triad as the Devil's Triangle; all three parties are culpable in the failure and share in the success. However, the system integrator is responsible for holding the three together to achieve successful delivery. The cornerstone to this relationship is a thoughtfully built contract.

Understanding The Reason

The customer is hiring the system integrator because they are lacking the resources to build the product or they desire to offload the risk. Resources can be people, knowledge, time, or other such item required to build the product. They are replacing this with a financial investment. The reasons must be understood. For instance, offloading risk will increase the price. On the other hand, if they are lacking knowledge or the people to complete the work, the system integrator should understand how the product is going to be maintained after it is released. Understanding these constraints dictates each party's work and may point to gaps in the responsibilities.

Completion Criteria

The contact must clearly define completion criteria for the project. The system integrator must insure:

  1. The deliverables are inside their capabilities. Bidding a contract beyond their skill-set ultimately leads to failure. The integrator must be honest to themselves and others about their capabilities.
  2. The deliverables for the product are sensible. It is the customer's responsibility for defining the deliverables; however, the system integrator has to validate their clarity. (Deliverable definition will be discussed in the future article "Hiring a System Integrator.")

Failing to have this basic starting point is bound to lead to frustration and failure.

Throughout the project, the system integrator must keep the project within scope. Unfortunately, there are many times when a customer wants to continue to haggle over a deliverable's state. This can drag the project into what seems like an interminable state. The customer has the leverage of withholding payment. Luckily, failing to pay for the product also means it cannot be used in production. If it is production worthy, it must be acceptable. The system integrator should always make sure the contract contains a clause that if the product is used in production there is defacto acceptance. All payments are due and any additional work must be conducted under a change order.

Force Majure

The system integrator should make certain the contract contains a force majure clause. A force majure clause is put in place to account for catastrophic actions that are outside the realm of the project. These include acts of God, such as earthquakes, flood, and fire, but should also include bankruptcies, foreclosures, and other situations outside the project's control. This clause allows for project termination without holding either party responsible. A fair force majure turns all work performed on future payment milestones into time and materials.

The Customer Relationship

Too often, the customer knows what they want, not what they need. The system integrator is their partner in creating the solution that meets the customer's needs. Transitioning the customer toward their needs requires that the system integrator gain the trust of the customer. If trust cannot be built between these two parties, the endeavor should not be undertaken.

Critical in this is understanding everyone's roles and responsibilities. Ultimately, a failed delivery affects the customer more than anyone else. They will be left with the unsatisfied business initiative, the excess cost, and the missed opportunity. The pain for the system integrator will be financial; however, in most cases progress payments will lessen the blow. In rare cases, when a system integrator over promises their capabilities, the only retribution is a lawsuit. No one wins in litigation.

Work Breakdown Structure

To help with this, the statement of work (SOW) should have a high-level work breakdown schedule (WBS). This provides two functions. First, it provides a picture of the how the work will proceed and second, it shows who has the responsibilities for certain tasks. This goes a long way in setting expectations.

Setting Expectations

As a system integrator, it is paramount that customer expectations continually be monitored and maintained. This starts prior to the contract. In many sales cycles, claims of what can be done get confused with what is actually contracted. The contract, and its accompanying statement of work, must provide clear expectations on what will be delivered and each party's responsibilities. As mentioned above, a work breakdown structure is the best method to address this. This is often considered an early deliverable of the project. PMI's PMBOK® includes this as part of the Scope Planning and uses requirements as an input. However, waiting to that stage of the project is too late. Other definition material that should be included in the contract or SOW that are often delivered in the project-planning phase are the roles and responsibilities matrix and a communications plan. Including high-level versions of these, sets the tenor for how the relationship will work.

Working With Vendors

Vendors supply products that are integrated into the project deliverable. Contractually, managing the vendor could be the responsibility of the integrator or the customer. Both have their advantages and disadvantages. The party that has the responsibility has greater risk, however not all the risk. For instance, if the customer has the responsibly for the vendor, the system integrator must work through the vendor to escalate vendor problems. Lack of customer action can reflect on the system integrator and cause significant strain on the relationship. The contract and SOW should clearly define this responsibilities and escalation path.

Note: This is the first in a series of articles on outsourcing that will appear over the summer of 2010. If you are interested in an in-depth study of the subject, Todd will be teaching a class at various universities and colleges. For more information check out the course description and find a college or university near you.
Read 9026 times

Related items

  • Kill The White Knight

    There is a reason we do not teach classes on fixing failing projects. Many a cynic feels that we simply do not want to teach our trade, however, our reason is far nobler—we should be teaching prevention rather trying to create white knights to save the day. It is the same philosophy as building a fence at the cliff's edge rather than an emergency room at its base. Our language is replete with idioms telling us to look past the symptom and address problems at their root cause. 'An ounce of prevention versus a pound of cure' or 'a stitch in time saves nine.' Please, feel free to supply your own in the comments. Unfortunately, most of our businesses loathe this philosophy, waiting to address an issue until it is irrefutably broken.

  • Tales of an Expert Witness: Sex, Lies, and Video Tape (Part II)

    Trust relationships, certifications, and standards sound like such a safe harbor. These sound like such great words in a proposal or statement of work. How could you possibly go wrong building a trusted relationship with a customer by committing to follow a standard? In fact, this can burn you… in court.

    No one ever starts a project with the goal of ending up in court. In fact, litigation may never cross your mind; after all, you have built a trusted partner relationship. Taking a few cautionary steps, however, will make your life easier if you end up in that ill-fated litigious position. Your best chances for success come long before you enter the courtroom—even before the project starts.

  • Alignment: Using the Balanced Scorecard to Create Corporate Synergies
    Alignment: Using the Balanced Scorecard to Create Corporate Synergies

    Add To Cart

    Author:Robert S. Kaplan, David P. Norton
    Publisher: Harvard Business Review Press
    Released: April 2006
    Type: Hardcover
    Pages: 320
    ISBN:978-0201835953

    Projects build capabilities to met corporate goals. If you are a CEO, you need to make sure your employees and vendors know what those goals are and how they fit in to the plan. If you are a project manager, you need to know the bounds of you project. If you are anywhere in-between, you need to understand how all the pieces fit together and keep it all aligned.

    Most organizations consist of multiple business and support units, each populated by highly trained, experienced executives. But often the efforts of individual units are not coordinated, resulting in conflicts, lost opportunities, and diminished performance.

  • ADKAR: A Model for Change in Business, Government and our Community
    ADKAR: A Model for Change in Business, Government and our Community

    Add To Cart

    Author: Jeffrey M. Hiatt
    Publisher: Prosci Learning Center Publications
    Released: August 2006
    Type: Softcover
    Pages: 146
    ISBN:978-0201835953

    This book is currently under review, more details will be added when available

    Tired of hearing about change and how your project is implementing it, but have no idea how to make it happen? ADKAR is the gold standard process to follow to help make that happen. This, and a little leadership, will get you ahead of the pack.

    Why do some changes fail while others succeed?

    How can you make sense of the many tools and approaches for managing change?

    How can you lead change successfully, both in your personal life and professional career?

  • The Next Evolution - Enhancing and Unifying Project and Change Management: The Emergence One Method for Total Project Success
    The Next Evolution - Enhancing and Unifying Project and Change Management: The Emergence One Method for Total Project Success

    Add To Cart

    Author:Thomas Luke Jarocki
    Publisher: Brown & Williams Publishing
    Released: June 2011
    Type: Hardcover
    Pages: 326
    ISBN:978-0201835953

    Still confused on how projects and change management fit together? If so, read this book. It gives a great history of both and outlines a process that may work for your company. If nothing else, the process described will help you understand how your company can fold the two disciplines together. The only detractor is the author's contniual reference to "his" methodology. However, this does give you a good example of its implementation.

    Just about every project professional agrees that "success" today is not just about being "on time, within budget, and according to scope" but one in which there is successful organizational change and the broad organizational adoption of project outputs and deliverables. However, because the project management and organizational/behavioral change management disciplines are often practiced as separate entities, the road to success often becomes divided, leading to poor outcomes for both the project manager and stakeholders throughout the organization.

Leave a comment

More Info on Project Recovery

Tell me More!

Please send me more information
on fixing a failing project.

Rescue The Problem Project

Internationally acclaimed

Image of RPP

For a signed and personalized copy in the US visit the our eCommerce website.

Amazon logo
Buy it in the United States Buy it in Canada Buy it in the United Kingdom
Buy it in Ireland Buy it in Germany Buy it in France
Buy it in Italy Buy it in the PRC
Buy it in Japan
Book sellers worldwide.

Upcoming Events

Other's References

Sitemap