| Custom "In House" Software Development |
|
| |
| The data management team often includes individuals with a wide range of technical expertise. They might begin to develop scripts and tools to help them with their own jobs as well as trying to automate some of the repetitive functions to provide better service to their internal customers. It is not uncommon to automate naming conventions through the use of internally developed tools & scripts (i.e. make shot, make project, etc.) This can present an interesting dilemma for the business as they might find themselves in a the situation of developing software that is not part of their "core competency" with valuable software development resources being deployed on tasks that do not necessarily provide them with direct competitive advantage in the marketplace. |
| |
| Often, the team members who develop "in house" solutions: |
| |
- Become disinterested, changes jobs, or leave the company, resulting in "abandonware."
- Engineer themselves to be indispensable for their own job security.
|
| |
| Either way the risk to the business can be very high. |
| |
| |
| Tool Versus Product |
| |
| The development effort and functionality required for a commercial product is significantly more involved than that of an "in house" tool, click here for additional insight. |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
