I’m planning to delete several github repositories. If you want any code from them, please take it before the end of March, 2015.
This is the third of three posts dealing with aspects of management that I consider significant in choosing management techniques and metrics for software development and support:
Despite the many complexities of software work, we are always working in one of two modes:
- Discrete project
- Continuous support
By discrete project mode I mean a mode of operation in which an organization creates a special initiative that exists for a defined period of time whenever it needs to achieve a set of related objectives, such as creating a new software application or upgrading the routers on the corporate network.
In contrast, with the continuous support mode of operation, the organization maintains a stable team to support each technical asset (such as the corporate network, a business rules engine, a COTS CRM package, or an ETL product) or suite of applications (such as the suite of applications that support consumer lending in a financial institution) throughout its lifetime. The size of the team may grow or shrink depending on the level of work needed to support the asset or applications at any given time, but the organization does not start a new project for every set of objectives pertaining to the asset or applications.