Comparar métodos
Revisa los métodos seleccionados uno junto a otro; las filas que difieren aparecen resaltadas.
| Seguimiento de la Velocidad Ágil× | Análisis de cobertura de código× | |
|---|---|---|
| Campo | Ingeniería de software | Ingeniería de software |
| Familia | Process / pipeline | Process / pipeline |
| Año de origen≠ | 2002 | 1988 |
| Autor original≠ | Ken Schwaber and Mike Cohn | Test Coverage Community |
| Tipo≠ | measurement metric | measurement and analysis |
| Fuente seminal≠ | Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall. link ↗ | Zhu, H., Hall, P. A. V., & May, J. H. R. (1997). Software unit test coverage and adequacy. ACM Computing Surveys, 29(4), 366–427. DOI ↗ |
| Alias | sprint velocity, team capacity planning, burndown analysis | coverage metrics, test coverage, instrumentation-based 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. | Code coverage analysis measures the extent to which source code is executed by a test suite, quantifying which lines, branches, or paths are exercised. Tools instrument code to track execution, reporting coverage percentages and identifying untested regions. Coverage analysis guides test creation, detects dead code, and validates test adequacy in quality assurance processes. |
| ScholarGateConjunto de datos ↗ |
|
|