My position in process management improvement (1)

When I got to a new position, I had a long history of being picky about project management. Now I can stand up and talk without a headache.
At present, the main task is to participate in regular meetings of various projects, observe some problems and assist the project manager in process improvement:

Now I want to extract three paragraphs of my Q & A at the meeting:
Project A's current situation: the requirement of the project is provided by the boss but not complete, mainly based on the competitor's system (B/S). The background is incomplete and the demand is unstable.
Q: How to develop a project?
A:
Unclear project requirements are one of the biggest risks of the project. If important functions of the system cannot be identified, we recommend that you suspend the project.
If the boss deems that important functions have been identified and implemented in iterative mode, determine whether to suspend them after completing important functions.
This risk should be thrown to the boss, at least to the boss. The project team cannot bear this risk.
If the boss agrees to continue development, it is necessary to implement the known needs as soon as possible, instead of spending too much time on demand analysis, so the cost-effectiveness of the time is very low (the demand boundary is vague ).

Project B: The project team has eight developers, but only two testers, one of which is public.
Q: How do I deal with the shortage of test resources?

A:
(1) This is the most common condition in software projects.

(2Quality is what all members of the project team need to face. It cannot be an excuse to reduce product quality because of insufficient testers.

(3) The solution is: Developers need to take on more test tasks and move the test forward:

A)Strengthen Unit Testing

B)Enhance cross-test andCodeCheck

C)InDebugInstead of running to its own modules

D)The project manager should combine the new functions1-2System after integration once every day

C project status quo: The project enters the testing stage, but there are many bugs. The solution is to perform Code cross-check.
Q: Code cross-check is more effective, but do we still have room for improvement in code cross-check?
A:
(1) the inspection results should be recorded and summarized to the project manager for analysis and summarization to find out which are common errors and which need to be thoroughly checked again, whose code is more credible and whose code should be focused on.
(2) Organize developers to communicate with each other, improve the development capability to avoid similar errors, and improve the Code check capability.
(3) Further improve the Code check checklist.

At the beginning, I will try again later!