Sammenlign metoder
Gjennomgå de valgte metodene side om side; rader som avviker, er uthevet.
| Agile Velocity Tracking× | Måling av teknisk gjeld× | |
|---|---|---|
| Fagfelt | Programvareteknikk | Programvareteknikk |
| Familie | Process / pipeline | Process / pipeline |
| Opprinnelsesår≠ | 2002 | 1992 |
| Opphavsperson≠ | Ken Schwaber and Mike Cohn | Ward Cunningham |
| Type≠ | measurement metric | quantitative assessment |
| Opprinnelig kilde≠ | Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall. link ↗ | Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report. link ↗ |
| Alias | sprint velocity, team capacity planning, burndown analysis | debt metrics, code health scoring, maintenance burden assessment |
| Relaterte | 4 | 4 |
| Sammendrag≠ | Velocity tracking measures the amount of work (typically story points or tasks) a team completes in a sprint, enabling capacity planning, release forecasting, and identification of process improvements. Introduced in Scrum methodology by Schwaber (2002), velocity provides empirical data for realistic sprint planning and project timeline prediction. Teams use velocity trends to identify bottlenecks and validate process improvements. | Technical debt represents accumulated shortcuts, deferred maintenance, and design compromises that incur future costs through slower development, higher defect rates, and deployment difficulty. Introduced by Ward Cunningham (1992), technical debt measurement quantifies these burdens using metrics like code complexity, duplication, test coverage gaps, and maintainability indices. Organizations use debt measurement to balance immediate delivery with long-term sustainability. |
| ScholarGateDatasett ↗ |
|
|