# Connect the complete software lifecycle

Taiga Learning · Worksheet
https://taiga.training/en/lessons/lifecycle/

Use fictional or approved information. Do not put secrets in this worksheet.

## Learning objectives
- Explain the main decisions before and after implementation.
- Connect a requirement to verification and operational evidence.
- Distinguish a coding tool from a software delivery system.

## Exercise
Use the lifecycle explorer for the customer export. At each stage, name the owner, evidence, and decision. Find one transition where your own organization currently loses context. Describe the smallest change that would preserve it.

## Your response
- Scenario and scope:
- Assumptions and open questions:
- Proposed answer or decision, with reasons:

## Verify your response
| Claim or criterion | Evidence or test | Result or gap | Owner |
| --- | --- | --- | --- |
| | | | |
| | | | |
| | | | |

## Next action
- Action, owner, and date:
- When will you review this response?

## Principle to retain
Useful software needs a complete lifecycle. Connect user needs, implementation, verification, release, operation, and learning with clear decisions and owners.

## Sources
- [NIST: Secure Software Development Framework](https://csrc.nist.gov/pubs/sp/800/218/final)
- [Google SRE: Monitoring Distributed Systems](https://sre.google/sre-book/monitoring-distributed-systems/)

This worksheet supports learning. Completing it does not itself authorize a production change.