You are currently browsing the Public Sector Billing Blog weblog archives for the day 29. March 2010.
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Feb | Apr » | |||||
| 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 29. March 2010
Project costs
29. March 2010 by admin.
There are many variables that impact the final project price. The mistake many companies make when initially trying to estimate the cost of a project is paying attention to only the actual software license costs. However, a recent white paper outlines four elements that need to be considered in every software budget.
One of them is “implementation services”. This term can seem vague, especially if it is a company’s first large software project. The white paper includes a definition of the 8 services you are paying for. It also outlines minimum software to services ratios, 8 questions to ask to know when to add more money to the budget and a sample quote. The buyer is also given the pros and cons of the two methods of pricing software implementations: “Time and Materials” versus “Fixed Fee”.
The White Paper is a useful overview that can alert readers to potential costs they may have overlooked
Posted in projects, vendors | Print | 1 Comment »