1. How to achieve a small team counterattack?
The transformation path of a large team is completely different from the improvement path of a small team. It is more effective for large teams to start with the overall structure, while for small teams, since they have fewer resources and less impact on decision-making, they should pay more attention to continuous improvement within the team.
Guiding ideology: Goal-driven, start with simple problems, and continue to improve.
2. When a product project enters the research and development preparation period, what preparations do you need to make before development?
demand split
architecture design
Requirement Dependency Identification
Workload Estimation
Schedule
3. Many development colleagues are "novices". In order to allow everyone to quickly understand the system architecture and use the ready-made system development framework proficiently and correctly, so as to ensure code quality and reduce rework with too many defects in the later stage, it is necessary to define each "Completion" criteria for each stage.
To be developed -> Design: The acceptance conditions (or test cases) must be written and reviewed by product personnel, developers and testers without objection.
Design -> Development: The update of the design document is completed, and the design review is completed.
Development -> Test: Write corresponding automated unit tests to ensure that all unit test cases pass successfully and complete code review.
Test -> Complete: All test cases pass and all defects are fixed.
Briefly describe the workflow of the "design -> development" phase:
After the developer gets a requirement, he makes a preliminary design by himself. No need to write a Word document, just draw a picture on the white paper with a pen.
Developers invite relevant colleagues to come to the whiteboard together, draw on the whiteboard and talk to everyone (usually only about 5 minutes).
Everyone directly gives feedback and suggestions for improvement.
Based on the discussion results, developers write design documents.
Submit the document and complete the design.
4. As more and more functions are added to the system, more regression content needs to be tested than in the early stage of the project. In addition, after the development is completed, the number of defects detected by acceptance has also increased. Although the team can repair these defects in a relatively short period of time, but the team has only one tester, and it is too late to verify these repaired defects, what should I do?
Emphasize the developer's self-test activities to enhance the completeness of test cases.
During the daily stand-up meeting, the testers will evaluate whether they can complete the test acceptance of all requirements in the test state before 4 pm that day. If it can be completed, then everything works normally. If it cannot be completed, the technical team leader will designate the developer who completed the requirements development on the same day not to receive new requirements, but to work with the testers to assist them in the requirements acceptance work until the test Personnel evaluation can complete the acceptance work of all requirements before 4 o'clock.
This is equivalent to the "test" link, we limit the maximum bandwidth, once the productivity of the testers is exceeded, then stop the production of the previous development link and expand the production capacity of the "test" link.
Learn more: https://t.zsxq.com/092gzRlhS
recommended reading
join readers circle
