Comparar métodos
Revisa los métodos seleccionados uno junto a otro; las filas que difieren aparecen resaltadas.
| Seguimiento de la Velocidad Ágil× | Métricas de Complejidad del Software× | |
|---|---|---|
| Campo | Ingeniería de software | Ingeniería de software |
| Familia | Process / pipeline | Process / pipeline |
| Año de origen≠ | 2002 | 1976 |
| Autor original≠ | Ken Schwaber and Mike Cohn | Thomas J. McCabe |
| Tipo≠ | measurement metric | quantitative measurement |
| Fuente seminal≠ | Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall. link ↗ | McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320. DOI ↗ |
| Alias≠ | sprint velocity, team capacity planning, burndown analysis | code complexity analysis, complexity measurement |
| Relacionados | 4 | 4 |
| Resumen≠ | 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. |
| ScholarGateConjunto de datos ↗ |
|
|