Through the 6th chapter of the study, we understand the term "agile process", he has 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.
In the 9th chapter, we understand the definition of PM: PM means: 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.
The 10th chapter focuses on typical users and scenarios, what is a typical user? Here are roughly divided into three categories: a (self-employed), your project for such people is only a "tool", the current need, but not necessarily in the future; B (Big Class), really understand your project, and have a stable demand for the project products. C (unrelated classes), using the product for improper purposes.
Analysis of typical users can be based on several attributes: gender/age, occupation, income, knowledge level and ability, motivation/purpose/difficulty, life/work situation, etc.
For the scene, my understanding is that I put myself in the identity of the user, experience to complete a goal of all the necessary process, which makes up a story is the scene.
The scenario enables team members to better update, maintain, etc. of the project.
In the demand analysis to drive the process-PM management-and finally, in the context of the maintenance of the scenario, a part of the basic process framework of a project is presented.
Construction of the fourth operation of the Law (6,9,10 chapter)