Method of construction 6 9 10

The sixth chapter Agile process

In the context of software engineering, "agile Processes" are a collection of values and methodologies. There are the following principles:

1. Deliver valuable software early and consistently to meet customer needs.

2. Agile processes welcome changes in demand and take advantage of this change to improve the competitive advantage of users.

3. Often released software available, the release interval can be from a few weeks to several months, can be short or short.

4. Business people and developers should work together every day during the project development process.

5. With an enterprising view of the project core, fully support the trust of them.

6. Both inside and outside the team, face-to-face communication is always the most effective way to communicate.

7. The software available is a key indicator of the progress of the project.

8. Agile processes can maintain sustainable development. Leaders, teams and users should be able to continue to work at the current pace.

9. Only with constant attention to technology and design can we become more agile.

10. It is important to maintain jianming-the skill of minimizing the workload as much as possible.

11. Only self-managing teams can create great architectures, needs, and designs.

12. Real-time summary of how to improve team efficiency and put into action.

Step one: Find out what you need to do to complete the product--product BACKLOG.

Step two: Decide what the current sprint needs to fix--sprint BACKLOG.

Part III: Sprint.

Questions and solutions for Agile processes:

The first step: there are complex dependencies between the requirements and tasks, and we need to consider each other's dependencies in addition to the priority levels.

The second step: to gradually refine a character from the description of the product level to the technical realization level, it is very necessary technical ability and communication ability.

Step three: Define what the task is.

Nineth Chapter Project Manager

pm Definition: PM refers to : PRODUCT MANAGER.    PROJECT MANAGER. Program MANAGER.

PM is responsible for developing and testing things that are uncertain.

1: Talk with customers, organize user surveys, find user needs.

2. Understand and compare competitor's products.

3. How to make the software usable and useful.

4. How to improve the team's process.

PM requires the ability to observe, understand and learn quickly. Analytical management capabilities. A certain degree of professional competence. Ability to introspect.

Tenth. Typical users and scenarios

The first step is to define the user's role.

Method of construction 6 9 10