In actual projects, there are always some common problems. Combining my own experience, I will sort out the following problems and response ideas for reference only
| Types of | description | priority | Suggested solution | Affect stakeholders | Remarks |
| range | Non-standard requirements change, no change control process | p1 | Develop a change control process and establish a CCB (Quadruple Key Stakeholders) 1. Change application submission 2. Change impact assessment 3. CCB approval (approval or rejection) 4. Implement the change 5. Verify the change |
ALL | Changes through the CCB are considered to be formal changes. The change log will be synchronized and updated, and all relevant parties will be notified . The scope and progress caused by the change will be adjusted accordingly. |
| quality | General design, omission or error in details | p1 | 1. Strengthen review quality (clear access and exit standards) 2. Strengthen version control (ensure effective control of changes) 3. Special emphasis is placed on detailed business processing procedures that require SA confirmation 4. Safety and performance indicators may require SA confirmation |
SA, design, development, testing | SA ensures that it communicates with other parties or customers for confirmation (through formal communication channels), and needs to report to the PM. SA needs to report to the PM for changes or uncertain issues. |
| Code logic does not conform to actual business Code implementation is unreasonable (security, performance risk, etc.) |
p1 | Beforehand: (coding access) 1. Responsible for specific development and participation in detailed design or partial participation (clear functional business background, timing interaction, business processing flow branch, abnormal situation handling, safety, performance requirements, etc.). 2. Make sure that the development can fully understand the detailed design before writing the code. In the matter: (control deviation) 1. The main process strengthens the team member code review or cross-review 2. The developer is required to actively and timely feedback the problems encountered, the risk 3. The development should perform the smoke test (self-test), the focus is on the run test case (testers provide) 4. strengthen developed to control a quasi-standard (identify defective, semi-failed) included in the performance assessment (primary and secondary drive joint liability) afterwards :( summary optimization) timely recovery disk, sharing lessons learned To form a knowledge base |
Design, develop, test | If you don’t meet the access conditions, don’t code, test, and finally rework is useless ( no credit for hard work ) | |
| Code is not up to specification | p2 | 1. Establish standards and code merger access 2. Strengthen Review (self-inspection and cross-review) 3. Existing problems are rectified at one time, and incremental problems are rectified on the same day 4. Continuous tracking of incremental problems- included in performance appraisal |
|||
| Single test coverage | p2 | 1. Develop standards 2. Supplement in time according to the scan report (self-check and cross-review) |
|||
| schedule | Demand confirmation is behind schedule | p1 | 1. Clarify the requirement confirmation mechanism and unify the docking person 2. Assess the scope of influence, identify risks, and formulate response plans 3. Follow the change control process (scope changes, schedule changes and other related changes) |
ALL | Reasonable workload, high-quality design, high-quality coding, and reasonable delivery rhythm |
| Design progress is behind | p1 | After the event: 1. Assess the scope of influence, identify risks, qualitatively and quantitatively analyze 2. Develop a response plan (rush to work, reduce the scope of delivery) 3. Follow the change control process (scope change, schedule change and other related changes) Beforehand : 1. Research and develop each Links, rationally evaluate the workload (based on resource conditions, seeking truth from facts), such as development time evaluation should fully consider including writing test, self-test, codereview, emergency buffer time) 2. Optimize resource allocation, solve bottleneck resources, and improve resources to be optimized 3 . Set up reasonable access and exit standards and mechanisms (requirement review confirmation, design review confirmation, development completion confirmation, test access, quality clearance) for each link flow, and a certain responsibility boundary (to prevent one mistake and another mistake) , Snowball) During the matter: strengthen monitoring, and correct deviations in time if deviations are found |
Design, develop, test | ||
| The development progress is behind | p1 | Development, testing | |||
| Testing progress is behind | p1 | All | |||
| communication | Poor communication, not timely, inefficient, and ineffective | p1 | 1. Develop a communication management plan (clear communication objectives, time, content, communication objects, communication effect tracking) 2. Unified problem escalation mechanism (top-down, bottom-up, designated docking person) 3. Timely follow the communication tracking effect Optimize the relevant communication process mechanism 4. Actively create a smooth, open, equal and transparent communication atmosphere. |
All | Unified communication channel Unified docking person (person in charge) communication and feedback timeliness (problem escalation) |
| risk | Recognition is not timely and response is delayed | p1 | 1. 建立问题日志，问题处理跟踪机制（第一负责人制度） 2. 鼓励动员全员参与，营造问题风险意识 3. 定期回顾，避免重复踩坑，形成知识库（组织过程资产） |
All | 风险清单 风险应对 风险升级 风险解除 |
| 资源 | 资源瓶颈，不足 | p1 | 1. 审查资源缺口（需求），补充优化并举 2. 合理搭配资源（ 1+1 》2 ） 3. 关键角色设置AB岗 |
把最优秀的人放在一线 打造精益团队（优化） |
|
| 团队建设 | 士气不足，绩效差 | p1 | 1. 制定合理的团队激励制度 2. 收集每一个团队成员的问题，逐一分析，找出共性，逐一解决 3. 明确绩效考核标准，公开，公平，公正三原则（按贡献度，有效价值落地为指导） 4. 提升团队成员对目标认同感，合理处理客户，公司，团队和个人利益关系。 5. 提升团队成员的存在参与感，积极鼓励主动沟通，主动反馈，及时肯定表扬，尤其是新入职员工。积极营造扁平化沟通氛围。 |
All | 直面问题，全员参与，解决问题，目标对齐，力出一孔（人心齐泰山移）。 作为主管或负责人，要做到身先士卒，能上能下。 充分授权，信任。 |
| 客户管理 | 客户满意度低 | p1 | 1. 合理管理客户期望（降低期望） 2. 重视客户反馈问题，及时跟进，引导客户走正式沟通流程，问题处理流程。 3. 主动，提前反馈可能出现的风险和应对计划。 4. 持续改进待优化处理问题（MVP交付），态度重视，行动积极，及时反馈。 5. 适当的时候寻求客户帮助，承认自己不足和敢于承担责任（实事求是） |
All | 换位思考 服务意识 有效沟通 效率效果 |