Your SlideShare is downloading. ×
11 peer review tips for software development projects
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

11 peer review tips for software development projects

838

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
838
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. 11 Peer Review Tips for Software Development Projects At the end of each phase of the Software Development LifeCycle, we arrange a peer review. You can use this free peer review template to get started and ensure that your team benefits for having their code, documents and deliverables checked by more experienced developers, writers and testers. Peer Reviews Format & Guidelines If you want to create a template, put the following at the top of the document: Version: Team: Team Member: Date Reviewed: Then describe the steps to be taken for the reviewers: ‘Please complete the following form. You must attach a copy of the deliverable showing your corrections. Needed revisions must be clearly specified on this copy.’ Create a checklist as follows: 1. Mistakes – Is the deliverable free of mistakes? 2. Grammar – Is the deliverable free of grammar errors? 3. Typing errors – Does the deliverable contain spelling errors? 4. Wording – Is the wording clear and concise? 5. Comprehensive – Was all feedback from previous versions evaluated? 6. Format – Was the proper format for business documents used? 7. Version – Was the version properly named? 8. Consistent – Is this deliverable consistent with other deliverables? 9. Readiness – Is the deliverable ready to be graded? 10. Tasks – Are tasks listed for each technique? 11. Root cause – Is this consistent with business need on the systems request? Include a comments section so that all evaluators can add their notes. About the Author Sharon Quinn helps companies develop Marketing Strategies and Business Plans. Sign up for her free newsletter at: http://www.softwaredevelopmenttemplates.com/peer- reivews/11-ways-to-improve-peer-reviews-for-software-development-projects/518/

×