השוואת שיטות
סקרו את השיטות שבחרתם זו לצד זו; שורות שבהן יש הבדל מודגשות.
| ניתוח נקודות פונקציה× | מעקב אחר מהירות זרימה× | |
|---|---|---|
| תחום | הנדסת תוכנה | הנדסת תוכנה |
| משפחה | Process / pipeline | Process / pipeline |
| שנת המקור≠ | 1979 | 2002 |
| הוגה השיטה≠ | Allan Albrecht | Ken Schwaber and Mike Cohn |
| סוג≠ | quantitative measurement | measurement metric |
| מקור מכונן≠ | Albrecht, A. J. (1979). Measuring application development productivity. In Proceedings of the IBM Applications Development Symposium (pp. 83–92). link ↗ | Schwaber, K., & Beedle, M. (2002). Agile Software Development with Scrum. Prentice Hall. link ↗ |
| כינויים | FPA, function points, IFPUG sizing | sprint velocity, team capacity planning, burndown analysis |
| קשורות | 4 | 4 |
| תקציר≠ | Function point analysis (FPA) quantifies software size by counting business functions and user interactions independent of technology or programming language. Introduced by Albrecht (1979), FPA measures delivered functionality, enabling effort estimation, productivity benchmarking, and software value assessment. Organizations use FPA for project contracts, vendor comparison, and portfolio management. | 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. |
| ScholarGateמערך נתונים ↗ |
|
|