As you begin your career in software development you’ll quickly realize your code or your GUI is not your own. When working on a software development team you will frequently be asked to present your code or your GUI for review. You may be showing a GUI to potential users to obtain feedback and make changes to increase their satisfaction with the final product. As part of quality assurance, you may pair off with a development team member to go through your code line by line to be sure your logic is correct and your code won’t introduce any bugs when incorporated into the product. If you’ve been given an important feature to develop you may be asked to present your logic to the team for input and feedback before you begin to code so that the final product is done well. During this role-play exercise your group will be given the opportunity to present some portion of your product’s code or some part of its GUI for review and you will also have the opportunity to review another group’s code or GUI.
As a group decide on a portion of your project to present to another group for review. The portion you present should be substantial enough to allow for valuable feedback from your reviewers but not so large that you overwhelm them. Your presentation should consist of a brief but thorough introduction to the project you are working on and the specific piece of the project you are showing for review. Depending upon what you are showing for review, this may include relevant requirements, an overview of the algorithm you have implemented, or an explanation of the logic behind what they are seeing. During the rest of the presentation your reviewers will set the pace. Record any feedback they provide and respond to any questions they may have. Remember this is your group’s chance to have a few more heads working on your project so take the opportunity to really get some good input.
Your group is part of the software development segment of a fortune 500 company. You currently have a project you are working on but a reorganization of the company has forced your group to take on a second project. As part of the transition plan the group currently working on the project is doing a series of reviews with your team. The purpose of the reviews is to bring your team up to speed on the other project and to ensure that the project is in a good working state before your team inherits it. Your team needs to be sure the logic behind the development work done is correct. You want to identify any bugs you see in the system so they can be corrected before they become your problem. You also want to be sure the code documentation is sufficient for you to understand when you take on the maintenance of the code. You also want to be sure the GUI is functional and intuitive for users. You may also want to point out ways the team could improve the algorithm or GUI design. Ideally you want to feel comfortable putting your name on it when your team inherits the project so make the most of this initial review opportunity.