agile.html - JethroKoch/programmingmethodologies GitHub Wiki
<title>SoftwareEngineeringMethodologies</title>
<style>
h1{color:#711797;font-size:300%;font-family:consolas}
h2{color:#711797;font-family:consolas;font-size:20px}
h3{font-family:consolas;font-size:30px}
p{font-family:consolas}
img{float:left}
span{font-family:consolas}
table{width:100%;align:center}
</style>
Agile methods are based on an agile manifesto. This is based on twelve principles; 1- Client satisfaction by early and continues delivery of valuable software, 2-Accomodate for changes in requirements even in late stages of development, 3- Working software is developed frequently, 4-Daily cooperation between businesses and developers, 5- Projects are developed by motivated individuals, 6-Use face to face communication, 7-Progress is measured on the functionality of the software, 8-The development should be sustainable, 9-attention should be paid to good design, 10-It should be simplistic, 11-Should have self-organized teams and 12-The teams should reflect on how to be more effective. From this Extreme programming has been created. It follows certain rules which are; There should be small releases, The project is divided into iterations, There is a daily stand up meeting, The customer should always be available, Requirements and development should be reconsidered whenever possible, code must be produced using pair programming, the code must be integrated often and all code must have unit tests. It is used when the requirements are always changing.
Agile methods are based on an agile manifesto. This is based on twelve principles; 1- Client satisfaction by early and continues delivery of valuable software, 2-Accomodate for changes in requirements even in late stages of development, 3- Working software is developed frequently, 4-Daily cooperation between businesses and developers, 5- Projects are developed by motivated individuals, 6-Use face to face communication, 7-Progress is measured on the functionality of the software, 8-The development should be sustainable, 9-attention should be paid to good design, 10-It should be simplistic, 11-Should have self-organized teams and 12-The teams should reflect on how to be more effective. From this Extreme programming has been created. It follows certain rules which are; There should be small releases, The project is divided into iterations, There is a daily stand up meeting, The customer should always be available, Requirements and development should be reconsidered whenever possible, code must be produced using pair programming, the code must be integrated often and all code must have unit tests. It is used when the requirements are always changing.
The quality of code is very good |
Programmers must be in the same geographic location |
Testing is always taking place |
The customer(or a representative) must be with the team at all times |