Σύγκριση μεθόδων

	Παρακολούθηση Ταχύτητας Agile	Μέτρηση Τεχνικού Χρέους
Πεδίο	Τεχνολογία Λογισμικού	Τεχνολογία Λογισμικού
Οικογένεια	Process / pipeline	Process / pipeline
Έτος προέλευσης	2002	1992
Δημιουργός	Ken Schwaber and Mike Cohn	Ward Cunningham
Τύπος	measurement metric	quantitative assessment
Θεμελιώδης πηγή	Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall.	Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report.
Εναλλακτικές ονομασίες	sprint velocity, team capacity planning, burndown analysis	debt metrics, code health scoring, maintenance burden assessment
Συναφείς	4	4
Σύνοψη	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.