I just came off a B2B integration project between a major ERP vendor and a Travel partner that had some major problems, and I was wondering if anyone else has had similar experiences. The project vision was pretty cool. We were making it possible for users of the ERP system to book Airline, rental car, and hotel reservations through their browser, and have their ERP expense reports be automatically populated with their major trip costs.
The project ran into problems because it was run across corporate boundries. Neither partner wanted to give the other access to its source control system, bug tracking system, or schedule system. The net result was 1)Lack of project visibility 2)Lack of change control 3)lack of version control of shared assets (the spec, xml docs, DTDs) 4)No visible shared schedule 5) History of the project stored in emails (when people left the project, their project knowledge was lost with their deleted email accounts)
Has anyone else tried to run a B-to-B (B2B?) software project across corporate boundries? Did you experience similar problems? Most importantly, how did you solve them?
Finally, has anyone implement an "eCommerce-in-a-box" solution like Ariba Inc., Commerce One Inc.? When doing so, did you run into any cross-corporate project management issues similar to the ones I mentioned above?
Slashdot Mirror
Hi,
I just came off a B2B integration project between a major ERP vendor and a Travel partner that had some major problems, and I was wondering if anyone else has had similar experiences. The project vision was pretty cool. We were making it possible for users of the ERP system to book Airline, rental car, and hotel reservations through their browser, and have their ERP expense reports be automatically populated with their major trip costs.
The project ran into problems because it was run across corporate boundries. Neither partner wanted to give the other access to its source control system, bug tracking system, or schedule system. The net result was 1)Lack of project visibility 2)Lack of change control 3)lack of version control of shared assets (the spec, xml docs, DTDs) 4)No visible shared schedule 5) History of the project stored in emails (when people left the project, their project knowledge was lost with their deleted email accounts)
Has anyone else tried to run a B-to-B (B2B?) software project across corporate boundries? Did you experience similar problems? Most importantly, how did you solve them?
Finally, has anyone implement an "eCommerce-in-a-box" solution like Ariba Inc., Commerce One Inc.? When doing so, did you run into any cross-corporate project management issues similar to the ones I
mentioned above?