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

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:
Responding to change over following a plan.
Responding to change over following a plan.


== Why do estimation ==
= Why do estimation =
== Traditional vs Agile approach ==
Planning is a very important aspect even for Agile projects. According to Stellman Greene ,  some say that estimation is a “Black Art”. What it means is that, the time required  to finish a certain task varies from person to person. A certain individual might take a day to do a task that might only take a few hours of another’s time. Any estimate that is not close to the actual time required is a bad estimate. But  a good formal estimation  of cost and schedule improves the accuracy of the results and  increases the likelihood of the project being delivered on time.
= Traditional vs Agile approach =
 
= References =  
= References =  
*[http://agilemanifesto.org/]
*[http://agilemanifesto.org/]

Revision as of 04:46, 17 November 2010

Introduction

Agile software development is a conceptual framework for undertaking software engineering projects. Agile methods try to overcome the weakness found in Classic software development methodologies such as the waterfall model by using an iterative and incremental development approach. Most of the agile methods try to minimize the risk involved by developing the software in smaller time frames also known as iterations. Each iteration lasts for around one – four weeks. The characteristics of Agile manifesto published in 2001, by a bunch of software engineers can be summarized as follows: ( link) Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan.

Why do estimation

Planning is a very important aspect even for Agile projects. According to Stellman Greene , some say that estimation is a “Black Art”. What it means is that, the time required to finish a certain task varies from person to person. A certain individual might take a day to do a task that might only take a few hours of another’s time. Any estimate that is not close to the actual time required is a bad estimate. But a good formal estimation of cost and schedule improves the accuracy of the results and increases the likelihood of the project being delivered on time.

Traditional vs Agile approach

References