Gossip: When interviewing a PS consultant, the idler will not directly ask about the configuration technology. In the idler's view, the basic thing of configuration point does not reflect the real strength of the consultant. In project practice, if a consultant takes the configuration list and talks with the customer about the plan, the result can be imagined-let's replace it quickly. The consultant must be standing on the commanding heights of the business and communicating with customers.
Well, the gossip ends here, let's talk about the entry-level core skills of the PS module: project definition and WBS structure design.
Project definition and WBS design are questions that idlers must ask every time a PS consultant is interviewed. It can be said that the level of mastery of this skill directly determines the upgrade potential of the PS consultant. If the consultant's answer on this question is very general, there is a high probability that some PS high-level application issues will not be discussed.
1. Project definition design
Quoting the content of a PA textbook:
Although the project definition is composed of a few simple codes, the simpler the actual code is, behind it is the value of experience accumulated by an enterprise for many years.
Here are 2 examples:
TIPS:
1. The length is controlled within 10 digits! Many students may ask why the standard field is less than 10 digits and not 24 digits? Idlers give me a reminder to build a project by copying and replacing them. Let’s see what the effect of more than 10 people will be... Idlers always think that the old saying is right-eat a ditch and gain a wisdom.
2. If not necessary, do not define company code, factory and other financial accounting organization information in the project definition code. For example, in some companies, 10-digit project definitions occupy 4 of them to represent the company code. The idler indicates that this kind of operation is very generous, and when the coding resources are so precious, the 4 digits are still the company code. Why not suggest that there are often inter-company transactions or credit transfers in corporate projects, and organizational structure information is included in the code, which can be very misleading;
3. A good project definition coding design must be a group management design. As for how to design, we must first abstract the stable attributes of project coding , and the abstraction of attributes depends on the focus of business management, such as industry, nature, scale, classification, etc.
2. Project WBS structure design
Here are the structures of several types of projects
3. Project template solidification
There is no one of three, there is no standard, and ironically, it is precisely this non-standard, which is the greatest value of PS in the eyes of idlers. Use flexible project templates to form project management standards unique to project-oriented enterprises .
PS: Is the PS module really a three-no module ? There should be a clear conclusion here!
Idlers think: The standardization of the PS program is the basis for other standardization of project-based enterprises!