1.
In any case, the change is absolute, the constant is relative, we don't complain about the occurrence of changes, it is important to have the ability to cope with changes. But then it is absolutely not to change from others, but the changes in the adaptive situation.
2.
Four variables: cost, time, quality, range
3.
Four principles: communication, simple, feedback, courage
4.
All practices:
a)
Planning game
i.
Business people need to decide:
1.
range
2.
priority
3.
Version composition
4.
Date of release
II.
The content determined by the technician:
1.
Estimate
2.
as a result of
3.
process
4.
Detailed schedule plan
b)
Small version
Contains the most valuable business needs.
c)
metaphor
Each XP software project is guided by a comprehensive metaphor.
d)
Simple design At any time, the correct software design has the following characteristics:
i.
Ability to run all tests
II.
No logic
III.
State up each of the important intentions for programmers.
IV.
Have as few categories and methods
e)
test
Test helps to enhance the confidence of programmers; only write test code for methods that may be wrong.
f)
Reconstruct
g)
Pair programming
One person thinks about the best way to achieve this method, and the other should be more focused on strategic perspective.
h)
Collective ownership
Only the official owner of the code can change the code
i)
Continuous integration
Take a computer to integrate
j)
Working 40 hours a week
Sign of serious problems in overtime
K)
On-site customer
Refers to people who really use the system after systemic production
l)
Coding standard
The standard should emphasize communication and must be voluntarily adopted by the entire team.
5.
The environment may be the last considered thing, but it is often very important.
6.
Be sure to ensure that a group is not interfered at work, otherwise you can't really concentrate on work.
7.
Business people should choose:
a)
Published range or time
b)
Relative priority of the function
c)
The exact range of the function is proposed.
8.
Development organization must determine:
a)
Time estimation required to achieve various functions
b)
The consequences of various optional technical solutions
c)
Suitable for their individuality, business environment and company culture development process.
d)
Which set of time is used to start, that is, what kind of process is used to evaluate the effects of practice and testing changes.
9.
The purpose of the plan:
a)
Unity and organize development team
b)
Decisive scope and priority
c)
Estimated costs and schedules
d)
Let everyone have a hundred times to the system's success confidence
e)
Provide a baseline for feedback
10.
Principles of planning:
a)
Only the plan needed in the next phase (plan to do not stop it)
b)
Responsibility for acceptance (responsibility can only be accepted, but can not be strong)
c)
The person responsible for the estimation
d)
Ignore the dependencies between parts
e)
Compare the priority plan and to develop plan - the purpose of the plan
11.
The primary problem is how to deal with the relationship between good people and people. If everyone can do their embassies and responsibilities, and live in harmony, then a good team must have a good team.
12.
The business side and the developer must do mutual trust and respect each other.
13.
If you can do a job like everyone, most people will be happy to do, and very happy.
14.
Pairing programming is a very worth trying, it may always like this way once it is used.
15.
Best Design: The easiest design of all test cases can be run
16.
The simplest four constraints:
a)
The system must be able to communicate any content you want to communicate
b)
The system cannot contain duplicate code
c)
The system has as few classes as possible
d)
The system has as little as possible
17.
Software design is impossible to change, how we have to do and process these changes. In extreme programming, we will rework for changes, but that is like modifying an article, it is a pleasing thing. 18.
The way to test the test seems to be similar to the process of making web pages. In the process of making web pages, we will continue to preview, check out the actual effect, and all the pages are completed during continuous integration. of.
19.
Testing first does not mean that we must write tests under what circumstances, and write code. In Eclipse, if there is no code, the test program is not possible, and what is correct and correct. Moreover, after the basic class, use the automated tool to generate a test program, to a certain extent, can improve the efficiency of work, why not?
20.
When a person written in a program, it does not mean that he has not paid attention to the test, most of why he has not mastered the test method and tool. I don't know how to test, how can I do it?
twenty one.
When saving items, if you use extreme programming, you should not only save the source code of the project, but also save all test cases. And when writing comments, not only in the source code of the program, this should be done in the code of the test case.
