- product manager (7)
- projects (40)
- resourcing (4)
- software selection (1)
- tax billing software (32)
- vendors (49)
- water billing software (38)
- 19. April 2011: User groups
- 19. April 2011: Detecting theft
- 13. February 2011: Automated water meter reads
- 27. January 2011: What German utility billing software would that be?
- 5. November 2010: Seven myths of billing implementations
- 24. October 2010: Comparing utility billing software
- 1. October 2010: Failing in the public sector
- 29. September 2010: Project failures
- 27. September 2010: Not the product manager
- 25. September 2010: Not the product roadmap
projects
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.