September 15, 2009
I.M. Wright’s post on risk management is worth reading: Software engineers do this all the time. They come up with a development schedule, unexpected issues come up, and they end up being late. Instead of informing their managers of the delay, they avoid facing conflict, rush the work, sacrifice quality, and slip the schedule, all […]
Read the full article →
September 13, 2009
Stephan Schmidt explains how doing several projects in parallel is counter-productive because of the high overhead costs involved. Projects must be tracked much longer, more documents are produced and must be tracked. All those status messages aggregate, flow upwards toward upper management, clog thinking and time. All those status messages flow to all stakeholders. Each […]
Read the full article →