167k views
0 votes
Kristen wants to implement code review but has a distributed team that works at various times during the day.

She also does not want to create any additional support load for her team with new development environment applications.
What type of review process will work best for her needs?
A.Pair programming
B.Pass around
C.Over-the-shoulder
D.Tool assisted

User Yakiro
by
9.1k points

1 Answer

5 votes

Final answer:

The best type of code review process for Kristen's distributed team without creating additional support load or requiring new development environment applications is Tool assisted code review process.

Step-by-step explanation:

If Kristen wants to implement code review for her distributed team without creating additional support load or requiring new development environment applications, the best option for her would be Tool assisted code review process. This type of code review process allows team members to review code asynchronously, at their own convenience, and without the need for synchronous collaboration. The use of specialized tools can help automate the review process, making it efficient and manageable for a distributed team.



Tool assisted code review involves using software tools that facilitate the code review process by providing features such as code highlighting, commenting, and tracking changes. These tools can integrate with version control systems and provide notifications for code review tasks. Examples of popular tool-assisted code review tools include Gerrit, Crucible, and Review Board.



By opting for a tool-assisted code review process, Kristen can ensure that her team can review code at their own pace and convenience, without the need for real-time collaboration. This approach allows for efficient and effective code review, even with a distributed team.

User Alex Ryan
by
8.7k points