Read the 8th, 9 and 10 chapters of the Law of construction

8th Chapter Requirements Analysis

Software Requirements

Users need a variety of requirements, as a software team to accurately and comprehensively obtain these requirements are mainly the following four steps:

1. Get and boot requirements. This step is also called "demand capture". Software teams need to think for the user, put themselves in, and guide the needs of users.
2. Analyze and define requirements. The demand from all aspects is structured, and the connotation of definition needs to be demanded from all angles.
3. Verify the requirements. The software team communicates with stakeholders to verify the software team's understanding of these requirements in the form of analysis reports, technical prototypes, user surveys, or presentations.
4. Manage requirements in the life cycle of software products.

Framework for competitive demand analysis: 1. N (demand) 2.A (procedure) 3.B (advantage) 4.C (competition) 5.D (promotion)

So I personally think that to be successful, you have to do a good job of demand analysis of this module. Because demand analysis is like a beacon in the dark, we pass it, we can quickly find the right way forward,

Do not let us go too many detours, so as not to waste unnecessary time and energy, can let us better and faster to seize the opportunity, quick one step.

9th Chapter Project Manager

PM's ability is important. PM is a good pm that has the ability and is approved by everyone. The "spanking" of self-reflection is the most annoying thing I hate, but it's possible that everyone has such an impulse. --"Oh, I can't do it, I don't do it." You have to play it yourself. "There may be a moment in this mentality, but when you are brave enough to face these difficulties and learn how to beat it, you are a good person." You will be full of pride when you defeat difficulties. This feeling is much better than giving up the "pat-and-go" feeling. Furthermore, it is important to be supported by everyone. A PM that cannot be supported by a team member is probably not supported by the leader.

So I think that PM is the key role that promotes a team to work quickly, efficiently, and is the core of the team.

10th. Typical users and scenarios

1. It is not enough to look at the user's surface language and actions, so we need to find the motivation behind the user. Otherwise the implementation of the function is always unable to obtain the user's satisfaction. So that the product may have to be "reworked" several times. "Rework" not only tests the software development team, but also tests the user's patience. Perhaps the user feels that the software purchased in your company is so troublesome that next time he will consider changing a company for
2. Our software is not for everyone. Everyone wants to make their own software more users, but in the software, we can not consider too many kinds of people. It is important to consider the typical users who use our software primarily, and some people who do not actually intersect with our software are not counted as typical users. We need to have a clear goal, certainly can not take care of everyone, then we should be the satisfaction of our real users.

Read the 8th, 9 and 10 chapters of the Law of construction