The project management includes the management of product quality. of course, this can not be separated from the product market analysis and the product in all aspects of the grasp. the strengths and weaknesses of the product and the feedback from the user on the use of this type of product. for product quality management to do a good job of planning, as well as product needs to make corresponding adjustments. innovation and breakthrough in the original plan is something we need to learn.
project quality management begins by identifying what the project objectives are and what is the quality of the project before it begins, and then considers how to ensure quality and set standards to measure it.
in the process of project management, the project goal is everyone's consensus, the project progress is sometimes delayed but relatively easy to measure and controllable, and the project quality is a very important but most overlooked elements.
There are two reasons why the quality of the project is often neglected: first of all, in a broad sense, the quality of the project is not easy to identify; second, even knowing is difficult to measure and control; and it's always hard for us to manage things that we don't understand.
Therefore, the first step in project quality management is to know what the quality of the project is before a project begins, in addition to determining the project objectives, and then consider how to ensure quality and develop standards to measure quality.
Accurately identify project quality
Why do you want to accurately identify project quality? in many cases, we don't know what the quality of the project or the work is, so to manage the quality, we must first know exactly what the quality of the project is.
The project management association defines quality as "meeting needs and suitability". by this definition, quality is the ability to clearly define and meet the requirements of users and stakeholders.
Once quality is clearly defined, pay attention to the difference between project objectives and quality. here are some examples of the difference between project quality and project objectives:
1) Take the "OKR Has Something to Say" series of events organized by Worktile Marketing as an example:
2) take a research and development project (or version iteration) as an example:
3) also, take a marketing campaign as an example:
Take content marketing article as an example, a reading 2000. only 25 conversion articles and a reading 1000. 18 conversion articles, obviously the latter quality is better; of course, the judgment of content quality must not only look at the conversion rate, article opening rate, stay time, share the number of times, etc. are also factors to be considered, but if other factors are similar, the conversion rate of high articles is certainly better than the conversion rate of low articles. (it is important to note that the quality of the project is also measured on the basis of the core objectives of the project.) )
Common problems in quality management
The pace of project implementation is chaotic
A project from start-up to execution on the ground often involves multiple team linkages, each part of which is ring-linked.
Common cases a link because of subjective or objective factors delay, resulting in the whole plan was disrupted, follow-up to each link and related link expected execution time is compressed, often the compression of execution time and bring associated delay or error, into a vicious circle.
Worse, in this cycle, the priority is often to make up for the time cost by sacrificing the most important aspects of experience polishing and optimization (that is, the quality of the project).
Project landing experience deviation is not controllable
The people who operate large-scale projects have feelings, a project plan to consider the details, once scattered to a team to start implementation, the project landing deviation began.
Of course, this process may involve a double deviation between the goal and the experience (quality), but the goal is more rational than the experience, so it is easier to judge, and the project experience (quality) is more percepsive, there is no particularly clear measure, so the deviation will be basically a chain reaction and difficult to control.
The project is not effective
The stumbling project is finally on the line, and finally ushered in the actual test. then the unexpected unplanned project worked completely below expectations, watching users do nothing about the various slots.
These issues may seem unrelated to the quality of the project, but in practice each issue has a serious impact on the quality of the project. therefore, good quality management plays a role in a project landing:
The implementation of the project landing to improve the management, to ensure orderly progress effective management of the actual experience of the project to ensure consistent landing the final effect of the project to be managed in advance, to ensure that the imminent danger is not disorderly having said that, how in the end can we do a good job in project quality management?
How to do a good job of quality management
Develop a quality management plan
At the planning stage, think about how you manage quality. the project quality management plan probably includes the following:
- Roles and responsibilities in quality management
- Tools and techniques that can be applied
- What type of test environment is required?
- When and how does the team measure quality?
- What needs to be checked and tested?
How do i verify deliverables?
After the quality management plan is determined, except for some human factors, other aspects can be done with the maximum use of tools, after all, the project manager's energy is limited, not all nodes can be remembered clearly.
For example, set key metrics for tasks in software tools, and project managers can receive notification of changes in a timely manner when they change.
Regular inspections and tests
If there are regular checks and tests throughout the project life cycle, teams are more likely to find defects at the point of origin, saving a lot of time and money later.
Allocate the energy spent on quality management
The time spent on quality should match the size and complexity of the project. pay attention to the cost of quality, cost should not exceed the overall benefits.
Conduct appropriate tests
Don't be stingy about critical tests. for example, some research and development teams do a good job of testing software functionality but fail to perform stress tests. when the software is put into use, it performs well when only a few users are present. however, when thousands of users access the system at the same time, the system crashes. also, be sure to test end-to-end.
"Quality is everyone's responsibility."
Guarantee test time
Most tests occur at the end of an iteration or project. as a result, testers often get into trouble. if developers lag behind their project schedules, testers are adversely affected.
for example, shorten the test time.
Critical time node pre-set
We must apply our knowledge, experience and creativity to deliver products within the time our customers expect. however, the project manager must know when to negotiate a trade-off between schedule, scope, quality, cost, and risk.
In addition, in order to make mid-term inspection and testing play a greater role, the project milestone events should be preceded by the time node, for the project finally online to allow more error correction time.
For example, we can pre-test the product's internal test time, the project manager focuses on the internal test time rather than the on-line time, first of all, to ensure that the internal test must be completed at a specified point in time, so that more testing and improvement time can be set aside for the official launch, so as to ensure that the project finally goes live.
No comments:
Post a Comment