First Sprint summary and review

Summary: Through the sprint of the first sprint, we learned about the entire sprint process and how to develop a project and assign tasks in a team. Our team in the first sprint did not achieve our expected results, we also made a reflection, the reason is that our knowledge is not broad enough, the second reason is that our enthusiasm is not high. A team, need to take initiative, need to be responsible for the attitude, to better cooperation, more efficient. While the code is important, planning and communication are also important.

The 第八、九、十 of the Law of construction

The eighth chapter mainly introduces the types of software requirements, the stakeholders, the common methods and steps to obtain the user's requirements, and the framework of the competitive demand analysis. The software team accurately and comprehensively finds the required steps: 1. Acquiring and directing requirements, 2. Analyzing and defining requirements, 3. Validating requirements; 4. Managing requirements in the SOFTWARE PRODUCT lifecycle. Stakeholders in software products include customers, market analysts, regulators, and software engineers. Demand analysis is a complex process of understanding user needs, agreeing on software functions with customers, estimating software risks and assessing project costs, and ultimately forming a development plan. Software developers need to understand the needs of users in order to design a good software.

The Nineth Chapter: PM is the project manager, is the team leader, is leading the team leader, the steward regardless of people, follow up the progress of the project. As a PM, you need the ability to: 1. Observation, understanding and rapid learning ability; 2. Management capacity; 3. A certain degree of professional competence; 4. Ability to introspect. This chapter also analyzes PM and risk management situations in the form of examples, and does not make people feel boring.

The tenth chapter: mainly introduces the typical user and scene, the software function instruction and the technical specification as well as the function drive design. Typical users can include: Name, age, income, the proportion and importance of the user on the market, the typical scenario of using the software, the environment in which the software/service is used, the life/work situation, the knowledge level and ability, the user's motivation , purpose and difficulty, user preferences. Function-Driven design steps: 1. Construct the whole model, 2. Construct the function list; 3. Develop a development plan; 4. Functional design phase.

First Sprint summary and review