FLUidity

The last quarter of 2009 and the first half of 2010 is going to be interesting for software projects.  The knowledgeable lead tech person should prepare for sporadic absences caused by the H1N1 virus.  A great place to follow the spread of the contagion is the flu tracker site in Pittsburgh.   Universities are feeling the effect of the H1N1 virus and are doing all they can to make preparations.

My advice would be to make sure you have flexibility and fluidity in your assignments, insuring that all critical areas of code have a main developer and a "buddy" (Brooks' co-pilot) that is very familiar with the code.  Perhaps this is the time to begin pair programming.

This also is the time to establish a remote work program so that folks feeling ill are not tempted to come to work.  It would be worthwhile to make it clear that folks feeling ill should stay home.  It also may be a great time to experiment with Second Life as a venue for remote meetings.

Please add any other suggestions you would like to share on preparing for and coping with this pandemic.  Later!

Comments

[Juli]

Another good resource is: http://www.sans.edu/resources/leadershiplab/pandemic_watch2009.php It is designed to provide information for IT staff to brief management.

[Dennis D. Scott]

Prof.

I agree with your post of being fluid with your work activities. From a productivity stand point the ability for employees to be able to vary the work place whether home or office is very beneficial. With the ability to develop portals i.e., nexprise for instance can allow productivity to continue. If employees are sick they can log on and still work as long as not deathly ill. Better yet just solely from a productivity stand point, if an employee can work from home after hours. Time and ability to meet deadlines increase.

[Software Testing Services]

Nice post. I agree with your views that being one should be flexible and fluid in the assignments. The period was also interesting for software projects. Its was really a high time.