Job Security : Why information hiding doesn't work...
And how to really create security in your job!
(rather than faking job security)

GD and AL were talking in the cubical next to me. They were two good employees and hard workers. A conversation began about the projects that were to be developed for the company. GD started in started stating that where some very good projects currently in the queue. AL agreed the applications were to be web applications that would require systems integration, validation, and a custom databases.

So far so good…

GD and AL were the two developers assigned to a new internet project to streamline processes and cut down costs for our mid-sized company. They reasoned that they should start the discussions about the first project and how it should be coded (written).

GD, the database developer, started off well. GD stated that the [database] should be normalized, indexed, and backed up]. AL agreed and added there are way too many applications here that are a jumbled mess and very hard to report from. GL the GUI developer added that they should validate the data both on the front and back end… GL paused for a moment.

The wrong direction… “Maybe it was a left turn from Albuquerque”, Bugs Bunny

“You know this application is going to be the core of the new business model. They are going to need us for a long time. BUT, we can help ensure that we stick around for a while.” said AL.

With piqued curiously... GD asked what AL had meant. The long discussion persisted over the next few hours about how they would structure the development such that only they would know how to do things and they would keep the information in their “personal folders”, GD said pointing to his head.

The plan works…

The development of the application took several months. We had now reached the first true test of the application. The Quality Assurance phase (QA phase). The QA phase is where a group the actual users (sort of a sampling of the user population) run through the application and find any “bugs” or missing requirements.

During this phase it is inevitable that the “users” for the application see what is possible and ask for more “options” and reporting creating what has been termed [scope creep].

For AL and GD, the business partners asked for some custom reports and in return they would extend the applications deadline. “Sure no problem”, the two developers replied. AL and GD sauntered back to the cube and started in on the new reports.

The report development began. The two developers consulted each other trying to remember the [database relationships] from their “personal folders” in their heads. They collaborated through the process together working late nights, but making the deadline and satisfying the current management staff by providing much needed information that only their system could provide. Chalk one up for the dynamic duo…