Porównaj metody
Przeglądaj wybrane metody obok siebie; wiersze, które się różnią, są wyróżnione.
| Śledzenie dynamiki postępu (Agile Velocity Tracking)× | Model przewidywania defektów× | |
|---|---|---|
| Dziedzina | Inżynieria oprogramowania | Inżynieria oprogramowania |
| Rodzina | Process / pipeline | Process / pipeline |
| Rok powstania≠ | 2002 | 2005 |
| Twórca≠ | Ken Schwaber and Mike Cohn | Thomas Ostrand, Elaine Weyuker, Robert Bell |
| Typ≠ | measurement metric | machine learning model |
| Źródło pierwotne≠ | Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall. link ↗ | Ostrand, T. J., Weyuker, E. J., & Bell, R. M. (2005). Predicting the location and number of faults in large software systems. IEEE Transactions on Software Engineering, 31(4), 340–355. DOI ↗ |
| Inne nazwy | sprint velocity, team capacity planning, burndown analysis | fault prediction, bug prediction, defect classification |
| Pokrewne | 4 | 4 |
| Podsumowanie≠ | 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. | Defect prediction models forecast the likelihood of software faults in code modules using statistical or machine learning approaches. Pioneered by Ostrand, Weyuker, and Bell (2005), these models correlate code metrics (complexity, churn, coupling) with historical defect data to identify high-risk components. Organizations use predictions to allocate testing resources, guide code review, and prioritize refactoring. |
| ScholarGateZbiór danych ↗ |
|
|