Session 8.1 - Putting It All Together
Capstone: Integrating TSPi Practices | Duration: 1 hr
Learning Objectives
By the end of this session, you will be able to:
- Trace the end-to-end TSPi lifecycle and artifacts
- See how roles collaborate across phases
- Follow the quality thread from requirements to postmortem
- Apply cadence and data to keep projects predictable
Introduction
Session 8 bridges all prior modules into a single, coherent flow. It shows how strategy, planning, design, implementation, testing, and postmortem connect—powered by roles, standards, and weekly cadence.
Lifecycle Walkthrough
| Phase | Key Outputs | Checks |
|---|---|---|
| Strategy | Development strategy, cycle scope | Team review; risk list |
| Plan | Estimates, schedule, buffers | Peer review; feasibility |
| Requirements | SRS, scenarios, baselined | Inspection; agreement |
| Design | SDS, integration test plan | Inspection; baseline |
| Implementation | Code, unit tests | Personal review; inspection (as needed) |
| Integration & System Test | Test results, defect logs | Defect tracking; retests |
| Postmortem | SUMP/SUMQ, lessons | Data quality check |
Roles in Flow
- Leader: cadence, issues, communication.
- Planning: estimates, schedule, variance reporting.
- Development: product quality, skill use.
- Quality/Process: data integrity, inspections, standards.
- Support: tools, CM, reuse, risks/issues.
Quality Thread
- Requirements clarity → design precision → coding to spec.
- Inspections at requirements/design/code; unit + integration + system tests.
- Defect data feeds postmortem and next-cycle estimates.
Summary
- TSPi lifecycle is a connected chain of artifacts, roles, and cadence.
- Quality is designed, reviewed, coded, and tested—not inspected in at the end.
- Data and roles keep the plan real; cadence surfaces risks early.