CSC/ECE 517 Fall 2010/ch6 6c AW: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
Line 7: Line 7:


==Purpose of Estimation==
==Purpose of Estimation==
The agile development methodology with respect to estimation centers around a few key concepts: a brief process, one that allows for adaptation and ambiguity, and yet one that provides accurate and useful information and progress [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch6_6c_AW#References].
Estimation is an essential element of any and every software development process. It can not only be utilized with respect to internal development and determining how to proceed on the programming side, but also with respect to interacting in a professional and honest manner with a customer.
The agile development methodology with respect to estimation centers around a few key concepts: a brief process, one that allows for adaptation and ambiguity, and yet one that provides accurate and useful information and progress [http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC/ECE_517_Fall_2010/ch6_6c_AW#References].  
On the


==Types of Estimation==
==Types of Estimation==

Revision as of 18:11, 17 November 2010

Estimation in Agile Projects

Introduction

Purpose of Estimation

Estimation is an essential element of any and every software development process. It can not only be utilized with respect to internal development and determining how to proceed on the programming side, but also with respect to interacting in a professional and honest manner with a customer. The agile development methodology with respect to estimation centers around a few key concepts: a brief process, one that allows for adaptation and ambiguity, and yet one that provides accurate and useful information and progress [1]. On the

Types of Estimation

Based on Size

Based on Velocity

Estimation Techniques

Planning Poker

Burn-down Charts

Re-estimation

Comparison

General

Formal models

Summary

References

[1] Cohn, M. User Stories Applied: For Agile Software Development, Addison-Wesley Professional, 2004.