Agile development-Principles model and practice (1)

Agile development-Principle model and practice

This is really a good book for developers, and for US developers, researchers, it presents a new value for development (for me), and even life is instructive. Need to read carefully.

The book summarizes the agile development of the example, it is really more enough to feel that the completion of the project is of great benefit, a kind of feeling of late reading hate. Think of their own development before the state, think of their mentors to arrange the company project situation, is the low efficiency, is pediatrics, is the book criticism of irony, this is the developer of the more than 10 years of wisdom, the experience of predecessors, the wisdom of predecessors, inspired me to read the thrill, I get the knowledge of the excitement, inspired my sense of accomplishment.

Two days before reading (combining mind mapping)

Agile development alliances: Development teams need values and principles that have the ability to work quickly and change accordingly.

Agile processes, and most importantly, extreme programming.

Extreme Programming (Extreme Programming): one suitable for small and medium-sized teams in situations where demand is unclear or rapidly changing. (Reference: http://www.docin.com/p-752508108.html)

Learn the term:

Project Stakeholders: All people involved in a product or project, including: Customers , users, demand analysts , developers , testers, documentation staff, project managers , Legal personnel, production personnel, marketing, technical support and other personnel dealing with products and customers.

user footage : Items require related cards, including estimated cost, priority

Project Iterations : Every two weeks to meet the needs of some stakeholders, each iteration completes, will demonstrate the iterative generation of the system, to obtain feedback.

Pair Programming : Pair programmer, complete code on the same computer.

Release Schedule : It takes about 3 months for a single release, or about 6 iterations.

QA Department : Quality Assurance, Quality Assurance department.

UML figure: the Unified Modeling Language is a language used to visualize software - Intensive Systems for modeling .

Refactoring : Refactoring ( refactoring ) is by adjusting program The code improves the quality and performance of the software, making its programs Design Patterns and architecture to improve the scalability and maintainability of the software.

Agile development-Principles model and practice (1)