Comparer des méthodes
Examinez les méthodes sélectionnées côte à côte ; les lignes qui diffèrent sont mises en évidence.
| Estimation par points de cas d'utilisation× | Suivi Agile de la vélocité× | |
|---|---|---|
| Domaine | Génie logiciel | Génie logiciel |
| Famille | Process / pipeline | Process / pipeline |
| Année d'origine≠ | 1993 | 2002 |
| Auteur d'origine≠ | Gustav Karner | Ken Schwaber and Mike Cohn |
| Type≠ | quantitative estimation | measurement metric |
| Source fondatrice≠ | Karner, G. (1993). Resource estimation for objectory projects. Objective Systems SF, Inc. link ↗ | Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall. link ↗ |
| Alias | UCP, use case sizing, effort estimation | sprint velocity, team capacity planning, burndown analysis |
| Apparentées | 4 | 4 |
| Résumé≠ | Use case point (UCP) estimation quantifies software development effort by analyzing use cases and environmental factors. Introduced by Karner (1993) for Objectory methodology, UCP provides structured approach to estimate labor hours from system requirements. Organizations use UCP to forecast project duration, allocate resources, and validate high-level project plans early in development. | 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. |
| ScholarGateJeu de données ↗ |
|
|