Construction Method Reading Notes 05-Chapter 6

Reading Notes

Chapter 6 agile Processes

Chapter 6 describes agile processes and their principles, how to choose agile development methods, and when to choose other methods.

Agile processes refer to a collection of values and methodologies. Introduced some agile development principles, such as frequent release of available software, business personnel and developers should work together on a daily basis during project development, face-to-face communication is always the most effective way of communication, constantly focusing on technology and design, keeping it concise, the team should learn to manage itself, always sum up how to improve the efficiency of the team and put it into action.

Agile process methodology-SCRUM methodology. The first step is to find out what needs to be done to complete the product, and then decide what needs to be solved in the current sprint. The third step is to start the sprint. During the sprint, a daily meeting will be held every day, we reported in sequence what we did yesterday, what we were going to do today, and what problems we encountered. At the same time, there are also charts, which can be a burned-out chart or a view of the layout. Three sections have been completed before the chart is started. Finally, an incremental version of the software is obtained for release.

Of course, there will also be some problems in the development process. For example, there is a dependency between tasks. How can we reflect the dependency in the plan? A problem occurs when a team member receives the task. The daily meeting may take effect. In this case, you need to define what the task is.

When developers say that the project is completed, they only say that the code to be written is finished, but there are still the most important 20% testing processes. Of course, they all know the 2/8 principle, the rest of the work takes the most time.

The key to successful agile processes lies in the scrum master, which cannot be selected by anyone. In fact, this is the position of a project manager. A team needs to implement agile processes, independent management, self-organization, and multi-function models.

Agile processes are not special. They adopt a divide-and-conquer approach, emphasize short iterations, point out the time and responsibilities invested by different people, encourage team communication, and put forward high requirements for team members.

Lessons learned from agile processes:

1. The agile Declaration shows some priorities and does not need to be argued as a decree or dogma.

2. The SCRUM master is not an officer, but a communicator without administrative power, just like Microsoft's PM. He/she also needs to do specific work in the team. The original "manager" is directly converted into a scrum master, and most of them won't work.

3. Some projects require a lot of dark box operations and political corner forces to deal with them, and SCRUM will put these contradictions at the bottom. This is both beneficial and risky.

4. In complex projects, first-line team members should make decisions.

5. Entrepreneurial teams often run in the scrum model (but everyone is too busy to prove how scrum they actually have ).

6. The SCRUM plan phase is not estimated to be a "contract", and leaders should not regard it as a contract. It is always inaccurate. Stick to short-term sprints, so that even inaccurate estimates will not cause major damage.

7. Do not talk to the management about "processes". They only care about "results ".

8. In large teams, cross-regional teams, or complex projects, scrum has no perfect answer, and the founder of scrum acknowledges this.

Agile processes are built on a number of effective best practices instead of just one click. Agility has its own applicability, not all situations apply. Agile processes are required, but there is no need for a hasty or messy development process.

?

Past views:

To develop a software, you only need to write code and complete the function.

Why is this not good:

If you do not perform the test, it may only work on your own device, but it may cause a major problem on other devices. If you do not pay attention to the methods in the development process, it can only be a mess.

Solution:

After the development is complete, perform more tests to minimize bugs. When I finish writing the code into a software program, the most important test is to be done, which takes more time, there are also many methods in the development process, which should be a more appropriate one.

?

?

?

?

Construction Method Reading Notes 05-Chapter 6