Help everyone to understand the theoretical system of IT project management more easily: nine knowledge fields and five process groups.
Help everyone learn and master the writing method of IT project scheme.
Table of Contents What is a scheme? How to write demand analysis? How to write a scheme design principle? How to write a solution? How to write an implementation plan? How to write the maintenance service plan? How to write the training plan? How to write a typical case? The typical design scheme analysis scheme is the solution to the problem.
The scheme includes: user solution, project application scheme, feasibility report, etc.
The purpose of writing a plan is to let others know that you have the ability to complete a specific task with high efficiency, low consumption and low risk.
In the scheme, the following problems should be solved: why do you want to do what to achieve what effect, who will do it, how to do it, how to control the quality, how to ensure whether you have the corresponding ability, what is the background of the scheme, tell the social, demand and technical background related to the scheme at present, and the situation of similar schemes at home and abroad.
Generally appear in the declaration plan.
Demand analysis, that is, the problem or purpose of the scheme, explains what problem the scheme is going to solve, and the scheme has a purpose. Here is a clear purpose and a goal to solve the problem.
Explain to readers why they do this.
The significance of the scheme is highly summarized. What problems can this scheme solve and what benefits can it bring?
Generally appear in the declaration plan.
The principle of scheme design is the principle that must be followed when designing a scheme.
The so-called principle is an unbreakable scale that must be strictly observed.
In every concrete solution, predetermined principles should be embodied.
Standards to be followed, including national standards, enterprise standards and local standards. It is also a standard that cannot be broken in the design scheme.
The goal of the plan, the overall overview of solving the problem, and a high degree of generalization.
Generally appear in the declaration plan.
Solution, explain to readers how to solve the problem.
Is the main body of the solution
The plan has the following points or components: organizational structure implementation plan (schedule plan), which explains the specific steps and work routes for readers.
Service plan (service plan), explain to readers that you have specific measures to do a good job in service.
Training plan (training plan), explain to readers that you have specific measures to do a good job in training.
This paper introduces typical cases of communication plan, quality control plan, risk identification and risk control plan, workload estimation of equipment procurement plan and human resource cost budget, and proves to readers that you have the ability to realize this plan.
The accumulation of work foundation and work results further proves that you have the ability to realize this plan.
It is the basic principle to meet the needs of users and all the requirements in the bidding documents. Make a clear response to every request of users and bidding documents, clearly and accurately understand users' wishes, and do not contradict or object at will.
We should strive to embody our characteristics (especially those that our main competitors don't have) in the scheme and give full play to our favorable resources in the scheme. The product selection of manufacturers should consider profit maximization and commercial controllability.
Demand analysis is the problem or purpose of the scheme, explaining what the scheme is to solve, and the scheme has a purpose. Here is a clear purpose and a goal to solve the problem.
Explain to readers why they do this.
User demand analysis is always the first part of user solutions, which mainly analyzes the needs of user projects, users' concerns and interests, users' current resources and existing problems.
User demand analysis is the key setting part of the whole scheme, which lays the foundation for why we provide the scheme setting argument described later.
At the same time, the in-place demand analysis also provides a basis for us to formulate the design objectives of the scheme.
As the opening part of the scheme, if the analysis is in place, especially the analysis of users' concerns and interests, it will immediately arouse users' voices, attract users quickly, and make it easier for users to understand what is behind us.
Proper demand analysis is half of a good plan.
On the other hand, if you can't fully grasp the needs of users, the scheme you come up with will not be targeted and users will not be interested.
To do a good job in demand analysis, it is necessary to conduct patient and meticulous user research, and formulate clear demand research clues and plans according to the characteristics of user projects.
The macro background, purpose and significance, organizational structure, current it construction, adopted technology requirements, software function requirements, software performance requirements (quality requirements), platform environment requirements, safety requirements, project risk identification, users' concerns and detailed analysis. Each part can be further classified and described as required.
For a comprehensive IT application solution, such as financial and insurance projects, the demand analysis should include the following aspects. It should be noted that users' needs are various. When analyzing and describing requirements, the classification of each part should be clear, and the content composition of each part should be balanced, clear, accurate, comprehensive, in place and focused.
Remember, the description of each part here will be clues and arguments for the corresponding content.
User demand analysis is often the most easily overlooked part of the scheme writer. Many people just pieced together some content, even some irrelevant content.
The consequence of this is that we don't pay attention to it, we can't really grasp the needs and expectations of users, and the written plan is not targeted.
The principle of scheme design is an indispensable part of every scheme, and it is also the most despised part of many scheme writers. Many people's method is to copy the principle part of another scheme casually and deal with it.
This reflects that they don't know what the principle is and what its function is.
The design principle of the scheme is a programmatic description of the design idea by the designer, a high abstraction and generalization of the requirements, and the most basic guiding principle of the scheme design.
Is a principle that must be followed when designing a solution.
The so-called principle is an unbreakable scale that must be strictly observed.
In every concrete solution, predetermined principles should be embodied.
In the principle of scheme design, it is necessary to show what problems should be considered in scheme design, highlight the countermeasures for users' concerns and interests, and closely echo the relevant contents of demand analysis.
The compilation of scheme design principles can be divided into two categories, one is the basic principle, and the other is the principle of responding to the special needs of users.
The basic principles of scheme design can be found in every scheme, such as: advanced and mature principle, advanced and protected investment principle, safety principle, functional integrity principle, flexibility principle, maintainability principle and expansibility principle.
Basic design principles Let's take the maintainability principle as an example to analyze the meaning of "principle". Maintainability means that the system developed according to the scheme we provide has the characteristics of convenient maintenance.
In other words, when designing the development plan, we should fully consider the convenience and feasibility of future maintenance.
Even though these basic principles may exist in many schemes, we should fully understand the expectations of users.
If the user's project funds are abundant, it may be necessary to highlight the principle of advance.
On the contrary, it may be necessary to fully consider the reuse of the original equipment and protect the original investment.
The principle of users' special needs should be carefully studied, which directly reflects whether we attach importance to users' ideas and really understand users' needs. To do a good job in this area, we must be very clear about the needs, concerns and interests of users.
Generally speaking, when introducing the scheme, the principle part will have a strong influence, especially those principles formulated to meet the special needs of users.
To put it bluntly, it means telling users what you care about, and then what we will pay attention to, solve and realize in the scheme.
This part of the solution is the main part and the heaviest part of the solution.
The demand analysis part is about why to design such a scheme, what problems to solve and what is the significance.
The principle part of scheme design is about the principles that we should follow when designing this scheme, or the problems that should be focused on and considered.
The standard specification part is about the standard specification that the scheme design should follow.
This part introduces the results of our design.
Whether it meets the demand, whether it can solve the user's problems, whether it follows the principles and whether it meets the corresponding standards and norms, all these should be reflected in this part.
Solution In order to make it easy for everyone to understand, I will introduce it here with an example of scheme design that everyone is familiar with and easy to associate. This example is a design scheme of a building.
Designing a building is a very complicated task. It is necessary to consider the functional requirements, appearance, space, room layout, strong current lines, weak current lines, water supply lines, heating lines, sewage pipes and various materials of each floor. Mechanical analysis and structural analysis are carried out. It can be said that designing a building is a huge system design work.
I will introduce the matters needing attention in writing this part later.
First of all, please remember that the design scheme we are talking about here is our communication scheme with users.
The purpose is to let users know that we have the ability, measures and guarantees to meet their needs, so that users can establish confidence in cooperating with us, but it is not a specific development plan.
Therefore, we should highlight the key points without covering everything, don't or never get caught up in specific details, and try our best to ensure the balance of all parts.
One of the key points of the design scheme is that there should be an overall description of the scheme at the front of the scheme description part, which can be called the overall design scheme.
Or become the blueprint of the scheme, which is the overall goal of the project. This part is a highly general introduction to your design scheme.
In order to let users know the whole picture of your scheme, you need to introduce complex design projects from different angles and levels, such as the appearance of buildings. From the front, you can't see the whole picture. Even if you introduce all the appearances clearly, it will be difficult for others to understand the building without introducing others.
Therefore, it is necessary to learn that the decomposition of angles and levels can be divided into categories and functions. The purpose of division is to introduce your scheme to you more comprehensively, clearly and easily.
Usually, an IT project plan includes: technical architecture, network architecture, security architecture, functional architecture and performance indicators.
The third key point in writing design scheme is that when you decompose and describe your scheme, you should fully consider the content of the previous demand analysis.
The requirements and problems mentioned in the requirements analysis should have corresponding solutions in the scheme description. Why do you want to do it in front and how to achieve it here.
It echoes the demand analysis, and it is also the reference for the decomposition of the scheme.
Whether the scheme responds to the demand is whether the scheme deduces the topic.
There are many schemes that can't be done in this respect. If you put pressure on this project or another, it will be a big joke.
Strong purpose! The fourth point of design scheme writing is that some users' concerns and needs, as well as the problems with high complexity found through analysis, should also be decomposed and explained separately. First of all, it shows that we fully respond to the needs of users. Second, it shows that we have a deep understanding of the demand. Although some problems are complicated, we have feasible solutions.
Thereby enhancing the confidence of users.
The fifth point of the design scheme should echo the previous design principles. In the description of the plan, it should be reflected that we strictly abide by the principles formulated earlier.
Similarly, we should also respond to the standards and norms we follow.
As we all know, no matter how well written, the things in the text are always abstract, and readers must associate them to understand the meaning of your description.
For example, the appearance of the building, if described in words, is likely to write a lot of lengthy, others still can't understand.
In the form of drawings, it may only take three or two pictures to show the appearance of the building clearly.
The function of the chart is intuitive.
Graph is a high generalization and abstraction of the scheme.
Make a good map, based on your complete understanding and mastery of the plan, as well as your accumulation of knowledge and experience.
A really good scheme description is illustrated, and the key parts in the diagram are explained by words.
The seventh point in writing a design plan is to learn to describe it in tables. Like charts, tables are also a very good way to describe schemes.
The function of tables is conciseness, conciseness and clarity, which makes it easier for readers to understand what you are saying.
For some content that contains a lot of numbers or has repeated descriptions, it can be described in tabular form.
The eighth key point of designing scheme is that some important indicators or indicators that users care about need to be analyzed based on your scheme. Use reasonable analysis models and data to prove that your scheme can reach the indicators expected by users, such as equipment configuration, type selection and design, etc., and take the analyzed indicators as the basis. The ninth key point of the design scheme is that for some projects that need to be integrated with other manufacturers' products, you should explain the reasons for your choice and the functions of these products, and introduce the main products you choose from the perspective of function and performance.
In order to highlight what we expect to impress users, the tenth key point of design scheme writing is
You can make a summary in the last part of the scheme description, and you can use the sentences introduced by the scheme characteristics.
In the function introduction, we should highlight our own uniqueness (to a certain extent, users will find the relevant content of our competitors).
In order to highlight the problems that users care about (echo demand analysis), we need to pay attention to the fact that features must be "special"
Well-organized scheme functions will also have a strong impact on users.
The eleventh key point of design scheme writing, especially when writing this part of the scheme, remember never to collect materials. This is a taboo to write a plan. If you need to extract some materials, you must fully grasp the contents of these materials to ensure that it is helpful to solve specific problems.
The twelfth point of design scheme writing: the development and implementation plan, also known as the overall progress plan, is the organic integration of all related plans, also known as the overall plan.
The master plan covers development plan, implementation plan, procurement plan, quality control plan, risk control plan, project team building plan, acceptance plan, service plan and training plan.
Project development and implementation plan (plan or work route) We often say that to accomplish one thing, it needs to be planned, organized, measured and guaranteed.
After our design scheme is completed, we will introduce to users how to realize it. This is an embodiment.
The preparation of the implementation plan needs to be based on the idea of project management and elaborated according to the planned, organized, measured and guaranteed clues.
There is a requirement for everyone here, that is, before you write this implementation plan, you really understand how to do this project well.
If you don't know how to do it, you have to ask whether the so-called implementation scheme is feasible.
This problem is a common mistake many people make when writing implementation plans.
We need to describe the development implementation scheme based on project management ideas.
First of all, we need to be clear about the objectives of the project.
In fact, the scheme is determined, and the overall goal is also very clear, that is, to develop the system according to the user's needs and deploy and implement it according to the user's time agreement.
But if you just say that, it just falls on the slogan of the overall goal.
In order to come up with a truly feasible plan, it is necessary to decompose the goal into phased goals or milestones. This decomposition should be as accurate and detailed as possible. The clearer and more specific the goal, the easier it is to find the implementation plan.
It is necessary to reflect on whether the overall goal can be well completed and achieved if the phased goals are achieved. If so, your decomposition is basically reasonable.
When the goal decomposition is completed, there may be a time series relationship between sub-goals and other related relationships. In order to complete each sub-goal, it needs some time and human resources to support it, and some complicated work may need some methods to guide it (work plan)
For each sub-goal, describe these related things clearly, and then arrange them in chronological order, and the implementation plan of the project will come out
The description of the implementation plan needs to be adjusted, generally in the form of a table.
Target decomposition is generally carried out in a top-down way. Specifically, it is to first decompose the overall goal into several major stages, then each stage is further decomposed into smaller stages, and finally it is implemented on the goal of each task.
In the implementation, it is also important to meet the time requirements of the user's construction period.
No matter how the goal is set and the plan is made, one thing is certain, that is, someone must achieve the goal one by one according to the plan.
As a good implementation plan, it is necessary to organize and divide the work among the teams and personnel who undertake this work.
The clue to describe this part of the content can be like this
Define the roles in the project implementation process, classify the people involved in the project according to the roles according to the needs of the implementation plan, and define the responsibilities of the roles.
Analyze the types of personnel involved in the realization of each sub-goal of this project. These personnel are related to our department.
Design the management structure of the project team, which is related to the implementation plan, work classification and role division, and should have the role of project leader with clear responsibilities.
If the team is large and involves many departments, the project leader needs to have strong resource coordination ability, and make clear the general project leader and the person in charge of different types of work.
Select clear project members according to the needs of the plan.
A good implementation plan should not only tell users clearly how to do it, but also introduce that your method is feasible and has little risk, which is the safeguard measure of the implementation plan.
Generally speaking, it should include the following contents: communication and coordination measures should be guaranteed by a clear communication and coordination mechanism, and the project needs us to cooperate with users, manufacturers and supervisors, so there must be good communication.
Quality requirements and quality control measures
Risk analysis and measures to avoid risks
Budget (cost plan), including equipment procurement plan and human resource cost budget.
Some complicated work plans should let users know that we have the means and ability to complete these tasks and enhance their confidence.
Acceptance plan This is a responsible agreement between both parties. The acceptance plan should be scientific and reasonable, and it should be operable.
For some specific projects, we need to make statistics on the manpower and workload we have invested.
First of all, you should classify the users who participate in the training. Different types of personnel need different training, which can be classified from the perspective of system management and system use.
Such as system administrator (further subdivided into application system administrator, system environment administrator, etc. ), system users (or user business personnel, including those who use the system at all levels), etc.
One of the key points of the training plan is the classification of training objects. Design training courses from the perspective of good management and use. In each training course, it is necessary to clarify the name of the training course, the training purpose and the expected goal (what level or ability the trainees can reach after training). The technical basis of the trainees requires the training form (centralized class and computer practice). Training materials (there must be clear training materials. In addition to the materials prepared or purchased, you can choose more materials provided when the project is delivered.
The second point of the training plan is that the training course is designed according to the overall implementation plan of the project. The time, place, training objects and courses should be clearly defined in the design schedule, because the overall progress should be considered, and the time and place restrictions of participants should be considered. The course arrangement must be reasonable and feasible.
The third point of the training plan, the training course, can finally introduce the situation of the teachers who undertake the training work and introduce the resumes of several main training teachers. In addition, for some training that requires special conditions, introduce our safeguard measures.
The fourth point of the training plan is to train teachers to introduce users' expectations for maintenance services: through effective management and monitoring, the failure probability can be reduced as much as possible, and problems can be solved with the highest efficiency. This is also the basic principle and goal when we design the maintenance service plan.
Analyze the service demand of maintenance service plan, and analyze the service demand of users in detail from the aspects of main service items and characteristics, response time and expectation.
One of the key points of the maintenance service plan is the service demand analysis organization management system, which tells users which departments and personnel in our company participate in the maintenance service in what roles and what the responsibilities of each role are.
Introduce the core members of the service organization.
The second focus of the maintenance service plan is to define the service project of the organization management system, respond to users' service needs, and tell users what services we can provide around this project and what the significance of each service work is.
For example, what services can we provide to reduce failures and solve problems?
The third key point of maintaining service plan is the definition of service items. This part introduces what measures we must ensure in order to complete the services we provide.
For example, what measures do we take to realize the service we provide to reduce failures?
Service items and service measures are closely related, and * * * is used to indicate what services we can provide to users and how to provide them.
The definition of response time, which is a mutually beneficial agreement, introduces our time response measures in different situations.
The fourth point of maintenance service plan, the definition of service measures and means, introduces our work and management process from service request to service end.
Further let users know that we have a strict service system that can meet the service needs of users.
If necessary, the management tools required by the service process can be introduced.
The fifth point of maintenance service plan is the introduction of service process. After introducing the service organization, service measures and service process of our service system,
Finally, we should respond to users' specific service needs for this project.
Design a service plan to meet the service needs of users.
This part requires a point-to-point response to the service requirements of users or bidding documents, and must clearly promise that it is being met.