Hereinafter, for the statement, some of them use our Party B, some use us, the company, the customer's statement; some places are all involved, some are the project officers.
1.1.1.1 Starting Stage
This stage can also be refined as the preparation phase and the planning phase.
As a project manager, after the project intention, the first thing to do is:
Check the information, determine the assistant, and develop a work plan.
The information is mainly divided into two aspects:
Ø System technology implementation
Ø Business operation
The main work of assistants is complementary to project managers in technology and business.
This stage of work plan content:
Ø It is to communicate with the customer (in this project, our customers is the application maintenance personnel of the technical support)
Ø Understand the expectations of our customers and cognition of the project
Ø Understand your business
Ø Further understand related technologies.
These three areas are very important, and the information manager needs to know where the project manager needs to know the difficulties and risks of the project and starts to take measures to avoid risk. Determining the Assistant laying the foundation for the formation of a project implementation team. The purpose of the work plan is to define projects (mainly
Project range. Division of project phases and works, etc.), its role is to reach A and B all as possible, which will lay the foundation for the success of the project. If the project is not detailed, it will lead to constant changes and expansion of user needs, resulting in serious overtime. So say as much as possible to define projects, you can guarantee the normal progress of the project (even if users don't sign, we can also understand Party B, and eliminate disagreement) through email or explanation.
As a team, you must know each other. I'm thinking about how much team can do for the team, what extent, what extent, can't do, how to persuade customers, let customers understand and accept our suggestions; knowing that both, to know the customer What is the evaluation criteria?
Before designing, what you want to do is to understand the customer's business. This can pass
Obtain
-
confirm
-
Get again
-
reconfirm
...... The way is obtained. If the customer does not cooperate, you can communicate through a variety of ways and customers, or consult the company's business personnel, other companies' product introduction to the maximum range. Of course, regardless of whether the customer cooperates, we must
To identify Party A, you must focus on these people (this will have a good foundation for the work after the project.). To identify the interests of our customers, you have to find interest points, technology, and business binding points, because technicians are always a pair of contradictions, if they don't adjust these contradictions, even if the technology is good, customers will pick Various problems, leading to the failure of the project.
In short,
Communicate, communicate, and communicate.
So in addition to communicating between customers, there is an important thing, that is,
Let the company high-level attention, with this, you can try to get adequate resources and support from high-level.
One more, that is
And other projects maintain good relationships and communication, in our project, if there is no quality department and the support of the support, our project will not progress smoothly. For example, in the test phase, the support work of the support is very serious and comprehensive, think of the things that most customers think, tested, so that we can go to the customer, in addition to a small amount of new demand, almost There is no change in demand. For the support, we have obtained a lot of business knowledge and group customers from them, because they are people directly communicating in front and customers, and persuade customers to provide a lot of material. 1.1.1.2 Execution Stage
After entering this stage, the project manager and the assistant stay in and form an implementation team. The benefits of doing this are that the project information will not be lost, and through the communication of both parties, many problems and risks can be found in advance.
At this stage, a very important job is
Documentation.
Document content:
Ø
Document management specification
Ø
Project management document
Ø
Software development documentation
Through these documents,
Ensure the maximum reservation of project information.
After the above preparation and plan, the next job is:
Ø Select other members of the project group
Ø Organize project launch meeting
Inviting the project team members to informed projects and targets, and confirm the responsibility of everyone (these in successive work, it needs to be adjusted according to the actual situation).
In view of the fact that each project member is very familiar, as a project manager must play its own overall grasp of technology, always understand the business, technical familiarity of project members, and progress, and give necessary guidance and help, Finally, successfully avoids the risk of the project members in business, technology, which may be unfamiliar.
After the project starts the meeting, it is necessary to make substantive
WBS
And project plans, so that everyone understands the burden on them. When you encounter problems, you can use it as soon as possible, avoid problems and risks in the earliest stage.
After the personnel, plans, WBS, etc. are all determined, it is necessary to adjust the plan, track risks and problems according to the actual work, but it is not important. and
To see items and technologies from the perspective of business, do not just look at technology and projects from the perspective of technology.
Further, through the implementation of this project, first confirm the function, complete the development of the function, and then develop the interface, ensuring the smooth progress of the development process. Because the business is not familiar, the page is better, and the good business is realized, and the fast adjustment can be made under any form of pages. According to my past experience, don't waste valuable time on the page, although the page The show is also very important.
Our project, due to the internal development of the company, the progress is relatively smooth, but to the implementation phase, the customer's participation has greatly improved, but it also brings obvious disadvantage (good to realize this problem before departure) Because the participating customers will always file some modifications to the project group members (because we are familiar with the business, the customer's revision needs often reflect how to use it comfortable), we have a good question, and later discovered It is necessary to require it, but some requirements are very immature (okay, passing through communication, there is no way to change several times). In this case, especially with the progress of the project, the adverse effect on the project is getting bigger. For this situation, we must do the first to persuade users don't modify (nothing more than saying that if there is any impact on you, what is the impact on the system, these will eventually bring you what? If the customer is not If you want to change, you have to make a written report, we propose changes to the program as well as the duration, let customers confirm the priority of the change, let them realize that our work is much. In the process of project execution, it is necessary to have a project group for a period of time.
There are also problems between the low tide, and internal members, such as different work habits, external factors, etc., thus causing adverse effects on the work atmosphere of the project.
What is the solution?
Ø Listen
Attack, pay attention to all project members have informal communication channels, pay attention to listening to them, making their respective emotions.
Ø Regular convening example
Informing the progress, problem, new plan, etc. of the project, unified thinking.
Ø Active project atmosphere
Novan dinner, not hurting the jokes, ....
Ø trust
Establish a fair and objective working environment, seeking alone, making each member have a feeling of respect. Fully trust everyone's ability.
Communicating with the ultimate customer as soon as possible, it is possible to keep a shortcut to the relationship between A Part 1., can keep the user to correct the development direction (but we have used long-term construction of such projects, this project is only later, users enter the project).
1.1.1.3 At the end of the end
The main thing is the implementation of the project, the later maintenance and the initial priority, and the test work. For the company's future development, it is also necessary to organize documents, propose recommendations for the development of software products, for company leadership decisions, to continue to expand market preparation.
I have no thing in this project is a commendation and final party for project members. This is the recognition of member work, and on the other hand, it is to improve the sense of identity of the project, so that everyone has a kind of
"Happy, full of returned" feelings.
1.1.1.4 Summary Analysis of Project Process
I think that in any project, it will encounter a variety of questions during the implementation process. Evaluating whether a project is successful, it is not only to encounter problems, how much workload is standard, and its standard should be on time and quality. Enhance predetermined indicators.
In this project, there are also many problems, such as:
Ø The "transition participation" of Party A representatives in the initial stage of the project start phase and the implementation phase.
Ø Resource problem
Ø Member's conflict, etc.
In fact, there is also a lot of ways to solve these things. The key is to look at our attitude, whether you want to solve it, how to solve it.
For example, the first one, standing in the customer's perspective, obtain the customer's trust; so the last customer will still think about your problem for your point of view. In fact, most of the customers are reasonable, and the problem is whether we do everything we do when we implement the project.
Resource problem. Strive for leadership support, communicate with relevant departments and cooperate with our work; if the original resource cannot be in place, do not walk to black, you can find an alternative method, because each project is impossible to end from start to end from start to end.
Members conflict. Listen, communicate and trust.
Say these, all of our circulation is the communication in project management, and the communication of communication is owned, the company leaders, project members, customers. Good communication, the problem will be resolved, and the risk will also be circumvented.
