6.1.1
Agile development Principles
1. Early and continuous delivery of valuable software to satisfy customer needs
2. Agile processes welcome the need to change and use this transformation to improve the user's competitive advantage (this need to be heard that the program can't stand it?)
3. Often the software is available, and the interval can be short from a few thoughtful months
4. The business people and the developers should work together every day in the project development process
5. With the core of the people who have the heart, fully support trusting them (in fact, those are Daniel.
6. Within the team, face-to-face communication is ultimately the most effective way to communicate (geographical terms).
7. The available software is the primary indicator for measuring the progress of the item
8. Agile processes should be able to maintain sustainable development. Leaders, teams, and clients should be able to continue to cooperate in accordance with current
9. Only the technology and design can be more and more agile
10. Keep it simple-the technology that can simplify the workload-is extremely important
11. Only self-managing teams can create better structures, needs and designs
12. How to improve team efficiency and pay for action
6.1.2
Agile processes
Step one: Find out what you need to do to complete the product--product Backlog
Step two: Determine what the previous conflict needs to resolve--sprint Backlog
Part III: conflict (Sprint)
Fourth step: Get the software increment
7.2
The basic principles of MSF
1. Push information sharing and communication
2. Work for a common remote view
3. Full rights and trust
4. Each division is responsible for the project
5. Value of delivery increment
6. Stay agile, anticipate and adapt
7. Investment Quality
8. Learn all the experiences
9. Working with customers
20150417 Job 4 Read the Law of Construction Section 5.5 6th 7th Chapter