You are currently browsing the Public Sector Billing Blog weblog archives for the day 23. August 2009.
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Jul | Sep » | |||||
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
| 31 | ||||||
- 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
Archive for 23. August 2009
Take ownership
23. August 2009 by admin.
One of the 10 steps to a successful implementation identified by Rob Gordy, VP, professional services at Revelwood, a provider of Business Performance Management solutions, is taking ownership. It’s a principle that applies to billing projects as well. Ownership, he says, starts at the analysis and design (A&D) sessions and progresses through the lifecycle of the project. Although there is an initial dependence on the implementation partner for knowledge of the software, application and project development, an immediate and ongoing transfer must occur while the consultants are still working on the components and phases of the project.
“The single biggest ownership issue is testing,” said Gordy. “You can’t wait until the project is completed before beginning testing. This allows you to develop a better understanding of the drivers and functions of the system.”
Posted in projects | Print | 1 Comment »