Chapter 8th, 9 and 10 of the Law of construction, and summary of the sprint

The 8th chapter: mainly introduces the types of software requirements, stakeholders, the common methods and steps to obtain user demand analysis, the framework NABCD of competitive demand analysis, the four-quadrant method, and the project planning and estimating techniques.

1, software Requirements: People in order to solve the real social and life of various problems and have to seek software

2, and as a software team, accurate and comprehensive to find these requirements the main steps are:

(1) Acquisition and guidance required (3) Verification requirements

(2) Analyzing and defining Requirements (4) managing requirements in the SOFTWARE PRODUCT lifecycle

3, users of the software requirements are divided into: the demand for product functionality, the product development process requirements, non-functional requirements, and comprehensive requirements. Therefore, the software team and the customer representative in the demand phase must define these issues clearly, otherwise the product will be made to customer requirements do not meet the trouble.

4, access to user needs-user survey specifically includes:

Focus group, in-depth interview (in-depth interview), card classification (cards sorting), user survey (Users Survey), user log Research (users Diary Study), Ethnography/Anthropology survey (Ethnograpic strudy), Eye tracking Research (ophthalmic Tracking), rapid prototyping (quick Prototype), A/B testing (A/B testing)

The 9th chapter mainly introduces the division of roles, the origin and requirements of project managers, the differences between project managers and other managers, the risk and risk management in software projects, and the professional ability of PM.

1, to become a qualified pm, need to have a certain capacity: observation, understanding and rapid learning ability, analytical management skills, a certain degree of professional ability, self-examination ability.

2, as a PM, its mission is:

(1) Lead the team to form the goal/vision of the team, and translate the abstract goal into an executable, concrete and graceful design;

(2) The life cycle of the specific function of the management software;

(3) To create and maintain the specification of the software, so that it becomes the development/testing personnel timely and accurate guidance, rather than obstacles;

(4) on behalf of the interests of customers and users, proactively collect user feedback, anticipating the new needs of users. Coordinate and determine priorities for each requirement;

(5) Analyze and lead other members to agree on defects/change requirements and ensure their implementation;

(6) Lead other members to ensure that the project maintains a reasonable balance of function/time/resources, track the progress of the project and ensure that the team releases the software that satisfies the customer;

(7) Collect all kinds of data of team project management and software engineering, objectively analyze the advantages and disadvantages of the project implementation process, and promote the continuous improvement of project members, thereby boosting morale.

The 10th chapter mainly introduces the typical user (Persona) and Scene (Scenario), the SOFTWARE function specification (functional SPEC) and the Technical Specification (design DOC), the function-driven designing (FDD) and the use cases.

1. Typical users can include: Name, age, income, the proportion and importance of the users on the market, the typical use of the software , the use of the Software/service environment, Life /work status, knowledge level and ability, user motivation, user preferences.

2, the main steps of the function-driven design are:

(1) Construction of the overall model (Develop an Overall models);

(2) Construction function list (build a Feature list);

(3) Development plan (plan by Feature);

(4) Functional design phase (designed by Feature);

(5) Implement specific functions (Build by Feature).

Sprint Summary: Teamwork is good, teammates are very strong, in the process I learned a lot, also got a lot. Hope we can continue to persist, team or project, good business will always have a harvest.

　　　　　

Chapter 8th, 9 and 10 of the Law of construction, and summary of the sprint