Extreme Programming is a software development blueprint that is designed to improve the quality of software and the software's ability to properly adapt to the always-changing needs of the client or customer. Very similar to other Agile Methods of software development.
Extreme Programming's main focus is to provide iterative and regular small releases throughout the entire project, which allows both the team members and customers to properly look through and review the projects progress through the entire Software Development Life Cycle (SLDC).
It is an agile software development framework whose main aim is to produce a higher quality of software, and a higher quality of life for the development team.
Extreme Programming includes the following: Programming in pairs or carrying out very extensive review of each other code, unit testing of all the code in the codebase, avoiding writing code for features until they are actually needed, a flat management structure, code simplicity and easily understandable code, Extreme Programming allows you to always be prepared for changes in customers requirements from time to time.
Extreme Programming takes its name from the general idea that the more advantageous parts of traditional software engineering practices are taken to "Extreme levels". As an example, code reviews seem like a beneficial practice, when taken to Extreme, code is then reviewed continuously, i.e. the practice of pair programming.
Extreme Programming encourages beginning with the simplest of solutions and refactoring to much better ones. The difference between this method and more regular software development methods is the emphasis on building and coding for the needs of the present instead of those of the future. Lovers of extreme programming have accepted the disadvantage that this can sometimes mean more effort in the future to change the system. Their theory is that this is more than compensated for by the advantages of not investing in future needs that might change before they become useful. Coding and building for uncertain future requirements imply the risk of spending resources on something that might not be of use.
Software development back then in the 1990s was formed by two major concepts:
1. On the inside, object-oriented programming replaced procedural programming as the main programming structure liked by people in the industry;
2. On the outside, the coming of the Internet and the dot-com boom focused on speed-to-market and company-growth as very competitive business factors. Fast-changing requirements needed shorter product life-cycles and were frequently incompatible with the traditional techniques of software development.
More Information about the principles and techniques behind extreme programming was shared with the wider world through various conversations on the WikiWikiWeb. Various contributors discussed and increased upon the ideas, and some spin-off methods formed. Also, extreme programming concepts have been explained, for several years, using a hypertext system map on the extreme programming website.
Below are some of the Features and Characteristics Of Extreme Programming:
1. Coding: Code is the software instructions that a computer can understand and interpret. Coding is seen as the most important process of the software development process because without coding, there is no working product. Coding is used to figure out the solution that best fits the problem. In Extreme Programming, a programmer for example who is struggling with a very complex Programming problem, or finding it hard to explain the solution to fellow programmers, might code it in a simplified manner, and use the code to explain what he or she means.
2. Testing: Testing is the main part of Extreme Programming. An extreme programming approach to testing is that if a small amount of testing can eliminate a few flaws, a lot of testing can eliminate a lot of flaws.
3. Listening: Programmers must listen to what the customer needs the software to do and what the business logic needs to do. They must understand these very well enough to give the customer feedback about how the technical aspect of the problem can be solved.
4. Designing: From the point of view of simplicity, we could say that software development doesn't need more than coding, testing and listening but this logic surely wouldn't work because, in the process of developing, one could get lost in the little detail that he would forget to see the bigger picture. One can overcome this problem by creating a design structure that organizes the logic in the system.
5. Communication: While building software systems, the developers need to communicate the system requirements to whoever wants to use it. In regular software development, this task is carried through documentation. Extreme programming techniques can be viewed as the methods for quickly developing and distributing institutional knowledge among the members of a development team. The goal is to give all developers a distributed view of the system that matches the view held by the users of the system.
6. Feedback: Extreme Programming has a way by which the customer can communicate with the developer when working in this way, the developer would keep updating the features based on how the client responds to the current stage.
1. It is an attempt to bring together humanity and productivity.
2. A mechanism for social change by lowering its cost.
3. A path to improvement.
4. A style of development.
5. A software development discipline.
Below are some of the benefits of Extreme Programming:
1. It saves costs and time.
2. It reduces risks.
3. It enforces simplicity.
4. It requires constant feedback from the client to the developer hence improving communication between both parties
5. It makes working on software faster.
6. It enforces teamwork.
Extreme programing has 12 best practices, derived from the best practices of software engineering.
They are as follows:
1. Pair Programming.
2. Planning Game.
3. Test-Driven Development (TDD).
4. Whole Team.
5. Continuous Integration (CI).
6. Design Improvement.
7. Small Releases.
8. Coding Standards.
9. Collective Code Ownership
10. System Metaphor
11. Simple Design
12. Sustainable Pace.
Extreme programming remains a suitable and sensible choice for certain projects. Projects that are suited for Extreme Programming are those that:
1. Involve new or prototype technology, where the requirements change very fast and rapidly, or some development that is required to discover unforeseen implementation problems.
2. As we research projects, where the end work is not the software product itself, but domain knowledge.
3. Are small and more easily managed through informal methods.
1. Extreme Programming ensures that you produce an iterative and recurrent software release throughout the project
2. Extreme Programing ensures that you are able to collaborate with teams
3. Collective ownership of Codes is ensured
4. Job Opportunity and Career Advancement.
5. Entrepreneurship Opportunity and Consultancy.
Extreme Programming - Introduction
Extreme Programming - Values and Principles
Extreme Programming - Practices
Extreme Programming - Supporting Practices
Extreme Programming - Evolving Practices
Extreme Programming - Process Cycle
Extreme Programming - Pair Programming
Extreme Programming - Roles
Extreme Programming - Activities and Artifacts
Extreme Programming - Rules
Extreme Programming - Additional Features
Extreme Programming - Scrum + Extreme Programming
Extreme Programming - Tools
Extreme Programming - Exams And Certification
Login & Study At Your Pace
500+ Relevant Tech Courses
300,000+ Enrolled Students
Don't have an account? Create your account to Start Learning!
The Scholarship offer is a discount program to take our Course Programs and Certification valued at $70 USD for a reduced fee of $7 USD. - Offer Closes Soon!!
Copyrights © 2020. SIIT - Scholars International Institute of Technology. A Subsidiary of Scholars Global Tech. All Rights Reserved.
Don't have an account? Create your account to Start Learning!