| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Nov | Jan » | |||||
| 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 (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
More on what makes for a successful project
As the cost of any software implementation project is high, it is critical for an organization to make the project a success and start deriving benefits out of it as far as possible. But what is it that makes an implementation project successful?
- A well-defined project organization structure that details the project planning, execution and monitoring mechanism
- An attitude that stresses on business transformation instead of process automation
- An approach that brings about the proper integration of people, process and technology through effective management of change
Companies need a well thought out, comprehensive process to help plan, guide and control the entire software implementation effort. Before the entity-gritty of software selection begins, management should know how current strategy, process and supporting system work and if any changes should be made before the new information system is introduced. The pre-implementation stage is the time to re-consider the way you do business and to make a detailed analysis of the requirements and the expectations of the new information system.
Optimization of business process rather than technical innovation should stand in the focus of an implementation project. Start defining software needs by examining current process that govern your flow of information and material throughout the order-to-delivery process and ultimately the entire supply chain. There is a common tendency to shortcut this very important activity but you will pay - sometimes dearly - in time and money for avoiding this essential step.
Take the time to evaluate your software plan before you commit to software acquisition and installation. Doing it right the first time is the only way to go. There are many people out there who wish they had taken a brief pause to evaluate their direction.
Leave a Reply
You must be logged in to post a comment.