Get the App
SLTechnology News&Howtos  ›  Internet Technology  › 

Interpretation of Agile 3-interpretation of Agile practice pair Review

Shulou Source: shulou.com Published: 2022-06-03 06:06:01 10月03日 Update

Programmer A meets programmer B. "Scrum sucks," programmer A said. "Why? I heard that Scrum is very good, and our company is also preparing to implement Scrum." Programmer B replied, "Don't, you'll regret it."are you implementing a real Scrum?"of course, we have all three roles, four meetings and three products in Scrum."

Agility is very simple, but extremely difficult. Agile methodology consists of a series of agile practices, but when people implement Agile, they are eager to implement the whole methodology at once. They value the simple form of agile practice, but do not understand or do not want to understand the meaning behind any agile practice, so that no agile practice can be done and can not enjoy the corresponding benefits. In the end, I found that the investment was so big, the expectation was so high, but the harvest was so little. Agile implementation only brings endless pain, so we have no choice but to bid farewell to Agile. "who says I can't see? I just focus my eyesight on one point to change my previous view of things."-- Zhou Xingchi, A Chinese Odyssey. Let's focus on a single agile practice and see if we can change our previous view of the world. The conclusion of agile practice is Review 1. This is done by twinning Review in a way that two developers work together to code Review. It happens after one of the developers has completed a piece of code functionality. The division of labor between the two developers is the code writer and the Review. Review users complete the pairing of Review through face-to-face communication with the code writer. The Review asked the code writer six questions in turn: "what does this code do?"Why do you want to do this?"what is the design idea?"does it fit the architecture?"does the code conform to the code specification?"Let's see if the code corresponds to the first five questions you answer." (not limited to, there can also be security performance and other issues. It is best to pair Review for no more than 30 minutes at a time, and the code of Review should be the code of the last 1-2 days. Can be simply described as 2 people, 1 piece of code, 6 questions, 30 minutes. two。 Can be used for

Tags: Code Agile Enterprise problems teams methods work Design knowledge capabilities people newcomers Development Learning Management practice effectiveness Software methods that is Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno Microsoft Redmi OPPO Reno Docker Apple