||Oracle Tips by Burleson
Does the employee work for the good of the team?
Is the workload shared among co-workers? Is the employee willing to
assist others, when needed, in fixing problems and just answering
questions? Is assistance provided willingly during normal business
hours and off-hours? Does the employee participate in team-building
events? Are standards and decisions willingly accepted and
implemented to improve support across all team members?
There are usually a few from any IT staff who do
not fit into the group, and usually it is of their own accord. They do
not willingly work towards a common goal to accomplish the work
objectives and in many cases work alone. Their focus is on their work
and not the group objectives. The little corner of the world that they
see as significant and solely their own masterpiece is what counts in
their minds. This thought process excludes cooperation and hurts the
team. The group will be less cohesive and members will be less likely
to assist others or willing to work together.
Not a Team Player Story
A computer programmer in an organization was not a
team-player. His time was allocated only to his own work. He rarely
assisted others, and over time people just avoided him. Whenever the
call came for someone to cover on-call for another team member, he
never volunteered. When people had problems to solve, he never helped
out. He also did not always abide by team standards, so his code was
harder to debug and document. This behavior was documented. When this
programmer did not work out, he was fired.
Download your Oracle scripts now:
definitive Oracle Script collection for every Oracle professional DBA