0527Sprint Summary, reading notes and questions

The eighth chapter of the main software team how to accurately and comprehensively find people for the software a variety of requirements, mainly the following several steps:

1. Acquiring and guiding requirements

2. Analyze and define Requirements

3. Verification Requirements

4, in the SOFTWARE Product lifecycle management requirements.

Next, the SOFTWARE product stakeholders, but also useful to obtain the user needs of the nine user survey methods. Once the requirements are taken, the software team will consider the positioning and prioritization of the functions, followed by plans and estimates to make better demand analysis. This chapter teaches us how to better standardize and conduct software requirements analysis in an orderly manner. Divide Break down large tasks into smaller tasks to help you estimate them more accurately and ensure more accurate and detailed status tracking. Then let the different people responsible, also, PM to follow up the progress of these small tasks, to ensure that the project high-speed and normal.

The Nineth chapter introduces the project manager, then the second section tells the origin of Microsoft PM, as well as PM to do everything except development and testing, and then PM to manage the code outside, there are risks. In general, PM is to lead the team to achieve the most important goals, and maintain the balance of the team. It is also noteworthy that PM steward regardless of people, after all, we advocate equal work. PM does not do development and testing things, after all, PM to be responsible for too many things, there should be little time to participate in development. Finally, the PM's ability requirements and tasks are described in detail. PM capacity requirements and Tasks, the book lists some of the ability of PM, have, observation, understanding, rapid learning ability, analytical management ability, a certain degree of professional ability, introspection ability. This chapter introduces us to the important role of the software team-the project manager.

The tenth chapter first describes how to define the typical user and scene, as well as the typical user's value, template, the template of the scene, and then there is a "use case" this requirement analysis tool, the following specification introduces the functional specifications and templates and technical specifications, and finally said the function-driven design. Typical users and typical scenarios. Probably is the non-professional programmer, the professional programmer, the project manager these three kinds of people! A big role for a typical user is to let the programmer think about the problem from the user's point of view. After defining a typical user, we also communicate and understand them with representatives of typical users. From a typical user to a typical scenario, write a typical scenario for a typical user, from the scene to the task, and finally the story template. Use case, is the requirement analysis tool. Convey information by telling simple stories. But it's difficult to tell a story, it's hard to be handy. Specification sheet. There are software function manuals and software technical manuals. Functional specifications are described from the user's perspective and do not involve internal details of the software. The technical specification is a design document that describes how the developer implements the function, which is useful for joining members of the team halfway. Function-driven design. is to turn the user's needs into a team development effort, and then continue to implement these requirements. It involves constructing the overall model, constructing the function list, developing the development plan, the function design phase, and realizing the specific functions. This chapter teaches us to lock down a typical user group, which helps us to find better users.

Questions:

1 What does the software life cycle specifically refer to? How to determine the length of the software life cycle?

2. So many roles in the software team, why choose the project manager to tell a separate chapter?

3. If you want to find a typical user, how to find?

Sprint Summary:

Before our group discussion of the time is not intense, always desolate, there is a communication problem, in recent discussions each member is very intense, say their opinion, Sprint the first sprint cycle completed successfully, are in every member of the positive cooperation completed, and we do not understand will go to consult others or read , online search information, product owners at the beginning of the product requirements will be listed very clearly.

0527Sprint Summary, reading notes and questions