The 45 habits of agile development

The first sentence begins: Continuous development,not episodic.

1 work in an iterative way:

Lack of a plan for a small time to finish them on time.

2 Attitude decides everything

A accusation does not resolve the bug

b Haste makes waste: Ordinary code farmers do not understand the code, as long as they can work well, either directly copied, or directly called. A good programmer will dig deep to see what impact it will have.

(preventive measure, don't try to fix it quickly)

(Do not isolate code, implement code review)

(Use unit tests, each can be tested quickly)

c to the wrong person (negative stifle innovation team arbitration mechanism)

D Overcome all odds (how to maintain someone else's code.)  or reconstruct it yourself. Correct habits are refactoring, if someone else's code maintenance costs are high)

3 Learning

A updated self (always with new technology) 1 iterative learning (new Daily Record) 2 participate in technical forums and events

b Investing in the team

C Know how to discard (learn something new, you will lose the old habit of preventing you from moving forward)

D Break the casserole and ask the end.

E set me up for rhythm (God invented the time to prevent all things from happening at once)

4 deliver the software the user wants

A let the customer make a decision

b Let the design guide rather than manipulate the development

C don't develop anything that can be downloaded.

D Keep it posted and always have the results (no finished products can be done in a day.) Remember. ）

5 Agile Feedback

6 Agile Code

7 Agile Commissioning

8 Agile Collaboration

The 45 habits of agile development