-Next I'm going to go over some of the XP's values - -2
-and principles that I just hinted on earlier in the lesson. - -3
-The first one, the first important value is communication. There - -4
-is no good project without good communication. And XP tries to - -5
-keep the right communication flowing and it uses several practices - -6
-to do that. It's got practices based on and require information - -7
-and in general share the information. For example, pair programming. - -8
-And we're going to say more about that. User stories, customer involvement, - -9
-all activities that help communication, - -10
-that faster communication. Another important - -11
-principle that we already saw, is simplicity. And the motto here - -12
-is live for today without worrying too much about the - -13
-future. When you have to do something, look for the simplest - -14
-thing that works. And the emphasis here is on, that - -15
-works. We want to build something simple, but not something stupid. - -16
-Feedback. That's extremely important in XP, and it occurs at - -17
-different levels, and it is used to drive changes. For example, - -18
-developers write test cases. And that's immediate feedback. If your test cases - -19
-fail, there's something wrong with the code. Or there's something that you - -20
-still haven't developed. Developers also estimate new stories right away as soon - -21
-as they get them from the customers and that's immediate feedback to - -22
-the customer. And finally, on a slightly longer time frame, customers and - -23
-tester develop together functional system test - -24
-cases to assess the overall system. - -25
-And also in this case, that's a great way to provide feedback - -26
-and by the way, also to help communication. And finally, courage, the courage - -27
-to throw away code if it doesn't work. To change it if you - -28
-find a way to improve it. To fix it if you find a problem. - -29
-To try out new things if you think that they might work better - -30
-than what you have right now. Now, that we can build and test systems - -31
-very quickly, we can be much braver than what we were before. So - -32
-how do we accomplish all that? And what are XP's practices that are going to - -33
-help us follow these principles and adhere to those values? These are some - -34
-of XP practices. There are more, but those are the ones that I'd like - -35
-to discuss in a little more depth, individually. Incremental planning, - -36
-small releases, simple design, test first, refactoring. We will actually - -37
-have a whole lesson next on refactoring. Pair programming, continuous - -38
-integration, and on-site customer. So let's start with incremental planning. -- cgit 1.4.1