Sometimes called (XP), it is one of the most used forms of agile programming.

The XP Process

Planning – also called the planning game, begins with listening, to build user stories of what the user expects to do (what output will be generated, features, and functionality).

The user develops these stories and then assigns each one a point value of how important this is. Customers and developers work together to determine which features go into the next release.

Design – following the KIS (Keep it Simple) process. XP likes OOP ideas and uses CRC cards which we’ll look at later.

Coding – Develop Unit Tests first to ensure what is coded is correct.

XP likes Pair Programming where two people work together to help overcome issues and review each other’s code.

Testing – Unit test should have already been run. Now other testing takes place.

Extreme Programming was originally found on Access 2 Learn

Assistant Professor

Walter Wimberly is an Assistant Professor at a regional college in Tennessee, teaching Computer Science in the Software Engineering track. He works as a student advisor, oversees curriculum changes, develops new courses, and manages the advisory panel.
Walter taught full time for about 7 years, before going back into “industry” as a full stack Software Developer for a dozen years. There he focused on web based projects coding in JavaScript/jQuery and utilizing the Bootstrap CSS Framework on the front-end, and coding in PHP, ASP/ASP.Net, SQL on the back-end.

Since he loves teaching, he taught as an adjunct web and digital media classes for eight (8) years, while working in industry, and has since returned to teaching full time.

He has been married for over 25 years, and is father to several special needs boys. As such, he is working on some projects to help others who have special needs to be self-sufficient, and support the care givers of those with special needs. Check out his Autism blog for more info.

Similar Posts

Construction Principles – Coding, Validating, and Testing

ByWalter Wimberly

Constructions (the Software Coding or Development Phase) can be broken down into several small phases. While Coding is only one part of Software Engineering, it is a large part, and part of being an engineer is being able to write good code! Preparation Make sure you understand the problem. Understand the basic design principles and…

Security and Privacy

ByWalter Wimberly

With today’s interconnected apps, security and privacy is on the forefront of people’s minds, especially with several noticeable breaches. “Relying on the government to protect your privacy is like asking a peeping tom to install your window blinds.” John Perry Barlow However, security and privacy have to be weighed both with and against the need…

Introduction to Software Engineering

ByWalter Wimberly

Software Engineering isn’t an “Advanced form of Programming”. Rather it is the idea and processes of how to properly design, develop, and deliver a software product. Without proper guidelines and processes, software project can be delivered late, without all the features, over cost, or a combination of those options. Software is found everywhere in our…

Process Assessment and Improvement

ByWalter Wimberly

The existence of a process is no guarantee that the software will be delivered on time, meet the needs of the customer, or be of long-term quality. Process patterns must be coupled with Software Engineering practice (Part 2 of the textbook) There are several methods to assess software: Standard CMMI Assessment Method for Process Improvement…

Component Level Design

ByWalter Wimberly

Component-level design occurs after the first iteration of architectural design has been completed. At this stage, the overall data and program structure of the software has been established. A component is defined in UML as: “a modular, deployable, and replaceable part of a system that encapsulates implementation and exposes a set of interfaces.” However, different…