Exam software project management

The most recent work is to create a prototype design for a company's products. During this period, we mainly use agile scrum development methods. In general explanations, we think that in every "sprint" process, the most important thing is to deliver an available product. The only thing That Scrum can sacrifice in balancing processing time, resources, and functions is functionality. At this point, I think scrum is especially like a test process.

1: We will make full preparations, analysis, and exercises before the exam.

2: During the examination, if it is required to be 45 minutes, you must submit it at the time of the test. No delay is allowed.

3: During the Q & A process, we will first select the ones with the most scores and the most skilled ones to answer questions, so that our scores can be higher.

4: During the Q & A process, we will constantly adjust our Q & A strategies based on time, accidents, and other factors.

5: after each test process, we will adjust the learning direction based on the scores and exam analysis we get to prepare for the next test.

6: Multiple exam processes run through the entire one-litre learning process.

7: The results of Multiple tests can be directly quantified, evaluated, and tracked in each stage of our learning process.

In scrum, what I feel most deeply is that "it must be delivered at the point and there is no delay allowed .", In scrum, I feel that if I want to do well, I must: Be positive, active, choose, don't stop, keep moving forward, and respond to risks.