Who is Involved
No-one can survive in isolation. So it is with systems development. Collaboration and a common business intent dictate the inclusion of many individuals — whose roles are often ill-defined, who have hidden agendas or self-proclaimed goals, who may resent or actively be resistant to change. In order to minimise such discord:
- Clearly explain to staff the business purpose and need
- Discuss the merits and deficiencies of the current system
- Exhibit the benefits of the proposed system
- Rationalise all current staffing workloads and justify change
- Explain the impact of change to staff within the business
- Identify all key players: drivers, co-players, third-party, developers, in-house support and end-users, and itemise their respective involvement before, during and after development.
It is the responsibility of both client and developer to anticipate and resolve such issues. Failure to do so will detract from best goals and instil bitter aloes in all team players and system users.