There is always more work to be done than people to do it.

 

This principle summarizes the reality of virtually all organizations and activities, not just Information Systems  delivery. It implies that a group within an organization charged with delivery of end results will a have a back-log of work not yet done. The existence of such a back-log is in itself not a problem, it reflects the desire of an organization to solve new problems and proactively improve itself; the problem arises when it grows perceptively in size from management’s perspective, and the length of time a change item sits on the back-log increases such that it can be measured in numbers of months or years.

 

So, we must accept that there will be a backlog; fully eliminating it would mean that the delivery group (like IT) becomes redundant, or that the overall organization has stagnated. What must be done is to embrace the back-log; it is IT’s input material and should be managed as such.

 Question for Readers: How big is your backlog? Is it considered a problem? How do you select what to pick from the backlog to do next?

 

 David Wright


Related Download
IBM Reference Architecture for Genomics Sponsor: IBM
IBM Reference Architecture for Genomics

Register Now
Uncategorized