Keywords used to assist in memory agile development

Some key concepts of agile development need to be explained to others occasionally during work exchanges. If you need to clarify your understanding in a few minutes, make it concise,

I think there are two tips: one is an analogy and the other is an explanatory keyword. The following are some typical examples to help beginners remember them.

1. Invest
User story:
Independent, negotiable, valuable, estimable, small, testable.
Independent, connectable, valuable, evaluable, short, and testable.

2. Solid
Design principles:
Single Resposibility Principle (SRP, single responsibility principle );
Open/close principle (OCP, open/close principle );
Liskov substitution principle (LSP, Rys replacement principle );
Interface segregation principle (ISP, interface isolation principle );
Dependency inversion principle (DIP, dependency leading principle ).

3. Dry
Avoid repetition:
Don't repeat yourself.

4. Kiss
UNIX Design Philosophy:
Keep it simple, stupid.

5. Tell, don't ask
Procedural Code gets information then makes decisions. object-oriented code tells objects to do

Things.
-Alec sharp
That is, you shoshould endeavor to tell objects what you want them to do; Do not ask them questions about

Their state, make a demo-,and then tell them what to do.