विधियों की तुलना करें

	एजाइल वेलोसिटी ट्रैकिंग	सॉफ्टवेयर जटिलता मेट्रिक्स
क्षेत्र	सॉफ्टवेयर इंजीनियरिंग	सॉफ्टवेयर इंजीनियरिंग
परिवार	Process / pipeline	Process / pipeline
उद्भव वर्ष	2002	1976
प्रवर्तक	Ken Schwaber and Mike Cohn	Thomas J. McCabe
प्रकार	measurement metric	quantitative measurement
मौलिक स्रोत	Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall.	McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320.
उपनाम	sprint velocity, team capacity planning, burndown analysis	code complexity analysis, complexity measurement
संबंधित	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.	Software complexity metrics quantify the structural and operational difficulty of code through numerical measurements. Introduced by Thomas McCabe in 1976, cyclomatic complexity became the foundational approach. These metrics assess maintainability, testability, and defect risk, enabling teams to identify problematic code regions and guide refactoring efforts.