Programming Practices
History
Release Cycle
Developer/Customer Interaction
100

Developers working in pairs, checking each other’s work and providing the support to always do a good job

Pair programming

100

What methodology overcame and surpassed extreme programming?

What is scrum?

100

Develop/integrate/test software

4th step

100

Who are all equal partners in extreme programming?

Managers, Customers and Developers

200

Enough design carried out to meet the current requirements and no more

Simple design

200

The founder of the very influential agile method extreme programming

Kent Beck

200

Select user stories for this release

1st step

200

What member of the development team is responsible for bringing system requirements to the team for implementation.

On-site customer

300

When an automated unit test framework is used to write tests for a new piece of functionality before that functionality itself is implemented

Test-first development

300

The year that extreme programming was developed

1996 or late 1990s

300

Plan release

3rd step

300

What are user(Customer) requirements expressed as?

User stories or scenarios

400

Constantly improving code to make changes easier when they have to be implemented

Refactoring

400

What project associated with Kent Beck, has been referenced as one the first to implement Extreme Programming methodology? 

Chrysler Comprehensive Compensation System project(C3)

400

Release software

5th step

400

How often are increments of the program delivered?

What is 2 weeks?

500

As soon as the work on a task is complete, it is integrated into the whole system and all the unit tests must pass. What is the name of this process?

Continuous integration 

500

Four Values that Extreme Programming is built on? 

Communication, Simplicity, Feedback, Courage/ Respect

500

Break down stories to task

2nd step

500

The development team breaks these down into implementation tasks. These tasks are the basis of schedule and cost estimates.

Task cards or cards