- product manager (4)
- projects (36)
- resourcing (3)
- software selection (1)
- tax billing software (30)
- vendors (42)
- water billing software (32)
- 8. June 2010: More on project success
- 6. June 2010: Project success
- 3. April 2010: Screwing up
- 2. April 2010: When things go wrong
- 31. March 2010: Do projects ever end?
- 29. March 2010: Project costs
- 7. March 2010: Implementing the software wisely
- 21. February 2010: Dealing with regulation
- 18. February 2010: Effective project management: the client perspective
- 14. February 2010: When projects go bad
When projects go bad
The stoush between SAP and Waste Management as reported by PC World highlights the issues at the heart of vendor selection:
SAP used "fake" and "rigged" software demonstrations to convince Waste Management its products were a good fit, according to the trash hauler. But after years of work and great expense, the product did not work satisfactorily, Waste Management claims.
But SAP has denied any wrongdoing and counters that Waste Management breached its contracts with SAP by failing to "timely and accurately define its business requirements" and provide "sufficient, knowledgeable, decision-empowered users and managers" to work on the implementation.
First: identify your business requirements. Setting out a checklist of essential functionality might sound like overkill, but incorporating the checklist and the vendor’s responses into the contract may help give clarity later. Checklist availability can be found on our main site and at Public Sector Assets
Second: be in control of the selection process. Define the script of what you want the vendor to demonstrate. Home in on the key aspects. Ask who else uses the software in that way
Leave a Reply
You must be logged in to post a comment.