example document release of software

The CIO and others initially assumed that the path to improved productivity would be an outcome of matching forecasted demand for service and forecasted supply (essentially of programming and QA staff), enabled by capturing a lot of size and capacity metrics, personal vacations, hours spent on work in progress, etc. In simple terms, each change request would be estimated (repeatedly) for hours of remaining effort from each source group or individual, run through a number cruncher that was time-sensitive, and out would come a resource-balanced schedule of releases with their associated change requests.