Read "project hundred States-deep understanding of software project behavior patterns" microblog Article 1

This blog is a blog that I usually read "hundred projects-deep understanding of the behavior patterns of Software Projects" and posted my thoughts on Weibo. I feel that it is necessary to organize it. I am making an advertisement here. I just opened Weibo at http://weibo.com/u/1904155902 and asked for help!

 

 

"Hundred states of Projects" is really a book worth reading. Many of them are problems in real projects. They provide good answers to how to avoid and prevent them. After all, the author is a master!

 

[Hundred projects-eye contact]:Currently, project Distributed Cooperative Development is popular, but there is a long distance between the project team and it is difficult for both parties to trust the project. Because many electronic information communication, there is a lack of language nuances and voice. Therefore, one-location collaboration is a huge advantage. I personally experienced this problem in a project I was responsible for last year. The customers were Guizhou, Nanjing, and Chongqing, and the two teams were working in different regions. That was a bitter problem!

 

[Project hundred forms-rental Soul],It cannot be bound by the inherent technologies that you have mastered. Sometimes, leasing soul assessment and selecting a solution that fits the project can make the project more dynamic to the team!

 

[Full-scale project-clear "bench"]:Sometimes, when building a project team, the personnel cost is always the first consideration, so the project is always completed with the minimum number of people. However, how can we grasp the project risks when key personnel leave the company? Therefore, if there is time for key bench personnel, it seems that the cost is exceeded, but it can also ensure the smooth completion of the project! Time, an eternal topic of cost! Haha

 

[Hundred projects-endless group meetings]:There will always be different solutions for the problem in the project. Everyone does not agree with the other party's point of view and always focuses on trying to persuade the other party, which leads to a waste of time. In this case, the Project Manager or meeting owner should be able to stand up and decide or specify a decision-making process. If the result is displayed, everyone must abide by it!

 

[Project Status-movie reviewer]:If you think of a project as a film, the film critic and the producer usually exist in the project team, and the difference between the two is that the film critic points out the project problems at the end of the project, and the responsibility has nothing to do with yourself. The producer gives feedback in a timely manner at the initial stage of the project or when there is a problem. If the project fails in a timely manner, at least he is striving for the success of the project, and his goal is consistent.

 

[Project hundred-Style]:The functional requirement is a rough room, and the non-functional requirement is the interior decoration. the structure and function of the House are determined during house viewing and house selection. The decoration quality directly affects the comfort of the house. However, the impact of these non-functional requirements on the final acceptance of the product by the customer is no less than the functional requirements.

 

[Hundred states of the project-natural power]:Authority and power are two different concepts. Nowadays, many teams are always leaders in decision making, and power plays a major role. The Authority is the one who can give the answer to the real question. Therefore, no matter whether authoritative people hold power or not, they should make every decision. The leader is responsible for supervising the actual implementation of decision-making, rather than making his own decisions.

 

[Project-All-in-One Office]:The office atmosphere can directly reflect the current status of the team. It was so quiet that the team had lost its vitality.

 

[All-in-One Project-agree upon silence]:This often happens when the project team allocates tasks and communicates progress. Generally, when a superior arranges tasks for a lower-level employee, silence occurs when the lower-level employee is difficult or fails to complete the task as expected. Generally, the higher-level employee agrees to accept the task. I think this is what both upper and lower levels need to consider and face, rather than one side can solve it.

 

[Project Layout-Scarecrow]:The scarecrow is similar to the prototype method in software engineering. I agree with the two sentence in the book: "The Philosophy of 'scarecrow 'is to make mistakes as early as possible and make mistakes frequently, in this way, you will get the correct results as soon as possible." "The best scarecrow model may even include some intentional errors"