The method of construction read Note 03

Read the 5th, Chapter 6 of the Law of construction

Today I read the 5th, 6 chapters of the Law of construction, and here are some of the gains I have gained from it.

The 5th chapter is about the team and the process, as well as the team's development model and development process. First he introduced us to the difference between a team and a non-team. The rabble, like Qu, is not a team. A team should have these features: 1. The team has a consistent collective goal, and the team will accomplish the goal together. 2. The team members have their own division of labor, mutual reliance on cooperation to complete the task. The next step is to talk about several different software team models. Among them are: Attending physician mode, star mode, community mode, amateur troupe mode, Secret Team mode, Spy team mode, Symphony mode, jazz mode, functional team mode, bureaucratic mode, etc. These software team models are formed during the development and maturation of the team and are suitable for different types of software development. Then, we learned the development process. The first is to write "write in the change mode", this model for those: "Only once the program, see the program, some not practical demo program", and then the second is the waterfall model, this model product mostly follow: analysis--------- Once the product is mass produced in this model, it is very difficult to go back and modify it. The Unified Process (RUP), which integrates all phases of software development into a unified framework. Its workflow is as follows: business model, requirements, analysis and design, implementation, testing, test deployment, configuration and change management project management. There is also the boss-driven process, which gets orders not by technology, but by the boss's personal relationships or covert operations. This model has a strong demand for the ability of the boss, and if the boss's ability is not strong, then the team will be greatly constrained. Progressive delivery process, main process: development-"Release-" Listen to feedback-"based on feedback to improve. In this process, there is the MVP method, that is, the smallest feasible product, is the core function of the product with the minimum cost to achieve, and then quickly solicit the user's opinion. and MBP production ideas, is the strongest and most beautiful product strategy.

The 6th chapter mainly tells us the agile development process. An overview of the agile development process begins with the first step: finding out what needs to be done to complete the product--prouduct Backlog. Step two: Decide what you need to solve for your current sprint. Step three: Sprint, Sprint, you need to open a daily standing memories, report on the daily tasks. During this time, you need to be aware of Burndown charts and Kanban drawing. The fourth step, get a version, released to the user. Then we introduce some problems and methods of agile process. As in the first step: there are complex dependencies between the various requirements and tasks, and we need to consider each other's dependencies in addition to the priority levels. In the second step, a task is gradually refined from the product-level description to the technical implementation level, requiring technical capability and good communication skills. The third step of daily meetings cannot be a mere formality. One way to solve this problem is to define what the task is. What it means to accomplish a task. In addition, we should also pay attention to the summary of the sprint. If a team is going to be transformed into an agile team, pay attention to the following: 1. Self-Organization 2. Multi-functional and he shared some lessons from agile development, such as: Scrum Master is not an official, but a communicator without executive power, like Microsoft PM, He also has to do specific work in the team. In a complex project, make a decision for a team member.

The method of construction read Note 03