An application starts with a need and ends with orderly retirement. Tasks, data, users and technical conditions change in between. Lifecycle management connects these changes with decisions so that development and operation fit together.
Six connected phases
The Grassroot framework begins with describing the need and assessing value and alternatives. It continues through development or adoption, testing and introduction, operation and improvement, and retirement. Each phase establishes an outcome, owner, required decision and suitable evidence.
The phases include feedback. An incident or new business requirement can trigger reassessment and development. An adopted standard solution still needs suitable testing, introduction and responsible operation.
Carry responsibilities and criteria through
Organisational value and compliance apply throughout. Before a change, examine whether benefits justify added effort and which controls are affected. Before retirement, establish what will happen to data and dependent activities.
Microsoft also describes lifecycle management covering development, governance and maintenance. The six-phase arrangement here is Grassroot IT’s own tool-independent structure.