New project manager
I am in the information center of the party and government organs, now responsible for an organ OA project, now I need to help me to analyze: (1) I used to be a website construction and post-management maintenance, writing to code is not Very in the line; (2) Now the project team members will be three people, and the two other colleagues have strong technology, which can be said that this project mainly rely on him to complete, I have to participate inside. Module code writing;
Now the leaders call me responsibility, but I don't have the experience, I don't understand what I want to do, from which one is to start? I have seen the post in the forum, most is the experience of experience, I can have a big generation, some too high, I streamline the project template, I will walk according to the first phase of the template, my colleagues believe that time is tight, no time Do these work, all deny me, but my own technology is not too hard, I can only listen. I want to know when I started at the beginning of the project manager, getting a project from whereabouts, what is the technical level of the subordinate than yourself? ? ?
A 1:
Congratulations, you can have such a chance, leadership can weigh you so much, you should do it well, this work is done. If you don't understand the place, it is very normal to actively seek a solution, this is already strong than a lot of people. I believe that you must become an excellent project manager. Here I can only give you some processes for some methods that I am personalized. Now just open your problem. I hope we can discuss and have been exchanged through this post. Thus I can get some improvement. This is some suggestions for some of my personal project startup: 1. Establish project team definition team roles. First, the project manager is yourself, here I want to say, as a project manager, the work is mainly determined "what to do" (ie, what), not "how to do" (ie how). I personally think is particularly important for your current situation. (Remember) After you can establish a technical core to solve the problem of "how to" (ie). Of course, this is not necessary, team morale, atmosphere, personal technology transparency is a good way to solve the "how to do", but in the case of don't have any experience, it is still not recommended to use "culture" to solve this problem. It is best to have institutional management, so it is best to build a "technical core". This role is not necessarily people in your team now, but must be familiar with people to reduce unnecessary risks. Finally, the role duties are clear in the team, so that everyone understands that there is no upper and lower relationship. Only the role is divided. The project is successfully completed is a common goal.
II. Develop early plan first. You are a person who decides what to do, so it must be planned by you, it is recommended to use MS Project. The initial plan of establishing a project is very important, I don't know what the project is now in what stage. I can only assume that I have not started in the startup phase. Then. Establish WBS. Don't think that this is the theoretical thing, this is very good for the plan. Now that you are in a very fine of WBS, WBS's deep refinement is the process of gradually developing projects, so don't want to think, let all work packs come out, but at this stage, put the WBS Deep 2nd floor is absolutely possible. (Finally, some personal experience is provided. When developing WBS with Project, the breadth decomposition work is best based on "Working unit" rather than "working hours". For example: "Code first stage // encoding Two phases "This is based on time." Should be: "A function code // B function code". So you have planned to change, the plan is very good, and the plan is flexible) Finally, try to find it now Find out the work package and assign resources, determine the goals of the work, and find "how to do the problem" in order to control. The development plan is important to pay attention to it. In fact, in addition to the progress plan, it is best to develop a risk plan. And all is reflected in Project. About how to make a better formulation, to achieve fewer missing tasks (work packages), the most resource allocation, the shortest progress, the lowest communication cost (mainly for development types). After you first set an initial plan, we have a detailed discussion for the actual situation of your project. I wish you a successful project! !
Answer 2:
Doing prior people, this is my work experience. First of all, don't think of you in the leadership, and then you are taboo. Doing technology and doing administrative thinking slightly, different, especially as programmers with coding machines, and his first entry is particularly strong, you need to make good contacts from private feelings.
Secondly, I will talk about work. For coding, it is not your work. The focus of your job is to grasp the overall application, understand, and convey good leaders and colleagues to your IT department.
When you first lead, pay attention to the following three things 1: Grasp the quality of everyone's code, code quality is not just how beautiful their code is written, how is the algorithm and SQL complicated but format uniform, use the code Whether is unified, whether all fields can clearly indicate that the field meaning is clear, and the block is comment, etc.
2: Progress, each software company or team should have its own project management template or form, but if you can accept it, do you really affect progress, huh, this is needed to use your personality charm And the coordination of rights equilibrium progress and standardization project management. The first is the progress, don't let them have reason to push the responsibility to your head, and don't let the leaders think that your incompetence caused the project's extension.
3: Testing work, this is more important, there are a lot of tests, this doesn't need me to say, but the basic testing needs you to do, otherwise, you can easily sweep your prevailing.
I am talking about your personal opinion as an initial project manager, not as a strict accordance with the standards of the IT project manager, what is going on, one step, one step, only the understanding and support of your part, can work Ok, otherwise, a deep project management experience can not help you.
Three teams, it is difficult to manage projects in non-professional companies, from the project management system, from actual departure, the current model may wish to be extensive.
Make a clear three points: 1, ensure that authorization is reasonable, and your own posture is adjusted. 2. Fully respect the will of other technicians, under the premise of overall progress, planned to be guaranteed, more participation in the project, formulate project plans, and prepare relevant documents. 3, clear the responsibility, the relationship between performance, all the technicians know the importance of the project document, if the lack of constraint mechanism, most people will not write. You have to fight for technical staff
