The law of construction 6-7 sentiment

The sixth chapter Agile process

Read the sixth chapter to understand what an agile process is. "Agile Process" is a collection of values and methodologies in the context of software engineering. Agile is a thought, or a value, that covers several methodologies for software development.

The approximate process is as follows:

1. Step one: Find out what needs to be done-product Backlog.

2. Step two: Determine what the current sprint needs to resolve--sprint Backlog.

3. Step three: Sprint. In the sprint phase, outsiders cannot directly disturb team members. During the sprint, a daily meeting is opened every day, and daily meetings force everyone to report progress to their peers, forcing them to put the problem on the materializing. At the same time, the daily meeting of the construction started, so that everyone can see a gradual improvement of the version.

4, Fourth step: Get an incremental version of the software, released to the user. The new features and improvements of the incremental are then further planned on this basis.

Agile requirements for the team: autonomous Management, self-organization, multi-functional.

Seventh, MSF (Microsoft Solution Framework)

MFS Basic principles:

1. Promote information sharing and communication

2. Working for a common vision

3. Full Empowerment and trust

4. Co-responsible for the project

5. Value of delivery increments

6. Keep agile, anticipate and adapt to change

7. Quality of investment

8. Learn all the experience

9. Working with customers

The MSF team Model, any technical project must meet specific key quality objectives to be considered a successful project. Any role that cannot achieve its goals will endanger the entire project. Therefore, each role is considered equally important and important decisions are made together.

What is scrum?

Scrum is a framework for developing and sustaining complex products and is an incremental, iterative development process. In this framework, the entire development process consists of several short iteration cycles, a short iteration cycle called a sprint, and the recommended length for each sprint is 2-4 weeks (Internet product development can use a sprint of 1 weeks). In scrum, the product backlog is used to manage product requirements, and the product backlog is a list of requirements sorted by business value, and the form of the list entry is typically a user story. The scrum team is always first to develop requirements that are of high value to the customer. In Sprint, the scrum team picks the highest-priority requirements from the product backlog for development. The selected requirements are discussed, analyzed and estimated at the Sprint planning meeting to get a list of tasks that we call the sprint backlog. At the end of each iteration, the scrum team submits a potentially deliverable product increment. Scrum originates from software development projects, but it is suitable for any complex or innovative project.

The law of construction 6-7 sentiment