Agile development One Thousand and One question Series 21: How to Write Design? (Educational Software case)

This is the first article in The One Thousand and One Q & A series of agile development. (Here, I would like to ask, one, two, three, and the General Directory of the question)

Problem

This problem comes from the QQ token record.

Early conversations are roughly as follows:

Q: 12:50:06
Agile development advocates simple design, right?
Does it weaken the design document?
Chen Yong-consulting-Beijing (139107533) 12:54:06
The weakening design is relative, and agile has only one purpose: to strengthen the final available products.
For teams that have been designed too much, they need to weaken the design to save time to strengthen the product. For teams that have not written the design documents, they need to strengthen the design to avoid rework to strengthen the product.
Most companies may be overdesigned, so the design is weakened.
Q: 12:56:52
So the design documents must be properly improved, right?

Analysis

This common"None"Scenario, that is, people expect that there is more than other methods, as long as you learn this method, the development process will be fine. In fact,Due to different environments, the "best method" is constantly changing and must be analyzed based on specific conditions..

Of course, there is another extreme opposite. I think that any method is not a good method, so I would rather follow the stream or talk about it later than pursue the universal value in this case. This will cause a lot of waste and mistakes, because when the "specific scenario" comes, without prior thinking and accumulation, I often feel unable to start. Therefore,For a specific environment, we should first consider and summarize feasible "best" methods, and conduct changes and improvements based on these methods.

The following is a detailed case study later.

Case

This is a later conversation in actual scenarios (the order has been adjusted): Chen Yong-consulting-Beijing (139107533) 13:03:22
What industry and product are you? Are you creating your own products or projects?
If you cannot answer these three questions, it is troublesome to find agile answers.
Q: 13: 09: 33
Educational Software Development and projects

Chen Yong-consulting-Beijing (139107533) 13:10:56
Okay, till now, It should be better designed in advance, and you do not need to do too much, but there must be. Better than none.
Projects generally involve a larger flow of people, because the long-term return is low.
In addition, because of the low individual output, the staff's salary and level will be lower.
Therefore, we should have a backbone staff to help you confirm the needs and design of the entire project, rather than making everyone feel free to use it.
Otherwise, everyone would be at a low level. If they fail to take full advantage of the game, they will be very busy.
However, educational software is not a product of critical life or major property. Therefore, we do not need to make too many rigorous designs to guide everyone.
...... Agile development does not have to do anything, but needs to find a suitable method for a specific scenario.

Analysis

In most cases, people seldom work across industries, especially some people who have been working in a company for a long time. Therefore, it is hard to realize that their own industries, projects, and teams have "characteristics, therefore, we often think that there must be a universal method to solve common problems, but this is not the case.

But then again,For the answer to a question, the most important thing is not the answer itself, but the ideas in the process.. In most cases, the person who asks a question actually understands the actual environment better than the person who answers the question, no matter how correct the "thinking in the analysis process" is, if it is based on an "unrealistic environment hypothesis", we can only launch an "inappropriate answer ".

Therefore, people who ask questions should learn how to analyze the process and refine the answers on their own, instead of sticking to the answer itself.

This is in the Martian proverb.The person who asks the question is responsible for finding the answer.