Project management salon 11th meeting minutes
In this gathering, I would like to give a brief overview of the project management process, and conduct a tentative in-depth discussion on the first stage. It is a pity that the number of people absent this time is too large, and the content originally intended to be discussed is relaxed. In fact, a weekly salon does not require too much burden. It should be a weekly coffee meeting. You are nervous for a whole week and relax for 90 minutes.
However, as long as you have the will, you will be able to talk about new things.
Today, we are sharing the "Dreyfus Model", the full name of which is "Dreyfus Skill Acquisition Model (Dreyfus Model of Skills Acquisition)", which is the result of two brothers' research on artificial intelligence. This model divides people's learning process into several stages: Novice, Advanced Beginner, Competent, Proficient, and Expert) master (Master ). In these six learning processes, the process from novice to competent is basically a linear process, but the subsequent process is non-linear. The advancement of each process is a qualitative leap. This can also explain why children can learn the same knowledge as adults through the course of "Young, middle, and high school.
The main features of the six phases of Dreyfus are as follows:
1. Novice.
2. Advanced Beginner: familiar with basic steps, able to complete tasks independently, and feel that you have learned a lot. The "proficient" on your resume begins at this stage. However, once the task encounters difficulties, they may be confused.
3. In competence: they can break down goals and combine a series of tasks to achieve a specific goal, but these combinations are usually not the best. They can also give some preliminary guidance and hate to be instructed by others. Most people are at this stage. Most of them do not want to invest any more energy in improving, but only want to finish their work.
4. In Proficient: solutions that give shape and cover major details. I have been able to combine knowledge and experience and began to like to talk about "Philosophy" and "methodology ". And learn more in the course of continuous learning.
5. Experts: have their own methodology for solving problems. Relying on intuition and spontaneous work, he rarely makes mistakes in his own field. I like to communicate with other experts to improve my abilities and be more modest and low-key.
Interestingly, people in their early stages tend to overestimate their abilities, while those in their later stages are more humble.
The model points out that it is difficult for most people to go beyond the "Competence" level. It can be seen that the word "proficient" in those resumes is childish and ridiculous.
We talked about how a team without consensus can gradually implement agile methods. This is a very common requirement. If you need to describe this problem in another way, it is "How To Make agile quickly take effect "? The preliminary opinion is that some common agile practices need to be implemented immediately because they can solve practical problems.
1. the most easy start is the "daily meeting", which can immediately solve the problem of poor communication between the project team, so that the project manager no longer needs to ask about the task progress, other team members do not need to enter the work log every day.
2. The second step is the preparation and evaluation of the backlog. In the initial stage, the project team can evaluate the problem freely. After the problem arises, the point evaluation and computing investment time will be gradually improved.
However, this topic is not discussed in depth, but we agree that this will be used as a discussion topic for the next party, and we will customize an implementation plan for a project team.
By the end of the year, the project team was either very busy or idle. It's easy to do, but it's hard to do it. So at this time, the project manager needs to arrange more easy tasks. The most common thing is to arrange some common learning tasks. In addition, architects should go into depth to think about architecture issues. For custom delivery projects, the architecture problem is not very prominent, and many of them already have mature architecture solutions. You can use them for reference. However, for product-type projects, the architecture is very important, and it is basically built from scratch, so design is very important. Taking EAS as an example, simple CRUD operations can be customized, but once they are customized, the results will be quite uncomfortable. Some people say that the customer slapped the table and shouted: "Will it take 10 days for you to modify a title?"
An improper design will soon become a hindrance to productivity. Many bosses focus on business-light products, which is understandable. After all, business will bring about cash flows. But have you ever wondered what a declining product can bring? Some people say that a good product can create a new market. This is really the case. For example, the first MQ product, the first ESB product, and the first database product, without exception, a new market field is created.
Because the topic is relatively free, we talked about age and time. Someone talked about his consistent point of view: his girlfriend's age = his age/2 + 7. If she had a good relationship, she would get married in 18th months, at this time, mutual understanding is enough, and the freshness is not lost. Once the time is too long, mutual dependence becomes a habit, such as those couples who have been together for 5 or 6 years, the more you get married, the lower the probability. From the perspective of project management, it is not only a waste of time, but also a significant risk.
It is shameful to waste time!
(I don't want to write anything about life or time)
References:
1. Better best practice http://www.infoq.com/cn/articles/better-best-practices
2. How to Apply http://gurudk.iteye.com/blog/324204 to Dreyfus model from AI to expert
3. Dreyfus model and best practice http://blog.sina.com.cn/s/blog_493a84550100c8vz.html