lecture8_2up - 5. Testing continually write unit tests,...

Info iconThis preview shows pages 1–17. Sign up to view the full content.

View Full Document Right Arrow Icon
January 02, 2009 O b j e c t O r i e n t e d S o f t w a r e E n g i n e e r i n g 448 XP extreme programming Lecture 8
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 2
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 4
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
January 02, 2009 O b j e c t O r i e n t e d S o f t w a r e E n g i n e e r i n g 459 The 12 XP principles 1. Rapid feedback 2. Assume simplicity 3. Incremental change 4. Embracing change 5. Quality work 6. Small initial investment 7. Concrete experiments 8. Open, honest communication 9. Accepted responsibility 10. Local adaptation 11. Travel light 12. Honest measurements
Background image of page 6
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 8
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 10
January 02, 2009 O b j e c t O r i e n t e d S o f t w a r e E n g i n e e r i n g 468 The 12 XP practices 1. The Planning Game quickly determine scope of next release 2. Small releases put a simple system in production quickly then release new version on a short cycle 3. Metaphor guide development with a simple shared story 4. Simple design system should be as simple as possible, complexity should be removed if at all possible
Background image of page 11

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 12
Background image of page 13

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 14
Background image of page 15

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Background image of page 16
Background image of page 17
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: 5. Testing continually write unit tests, customers write functional tests 6. Refactoring restructure the system without changing behavior 7. Pair programming all code written with 2 programmer at 1 machine 8. Collective ownership anyone can change code anywhere anytime 9. Continuous integration integrate and build many times a day 10. 40-hour week work no more than 40h/wk as a rule 11. On-site customer include a real, live user on the team full time 12. Coding standards code in accord. to rules emphasizing communication January 02, 2009 O b j e c t O r i e n t e d S o f t w a r e E n g i n e e r i n g 480 The 12 XP practices On-Site Customer Planning Game 40 hour week Metaphor Simple design Refactoring Short releases Testing Pair programming Coding standards Continuous integration Collective ownership...
View Full Document

This note was uploaded on 02/23/2012 for the course CS 307 taught by Professor Staff during the Summer '08 term at Purdue University-West Lafayette.

Page1 / 17

lecture8_2up - 5. Testing continually write unit tests,...

This preview shows document pages 1 - 17. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online