TeamReview Wiki & Documentation Rss Feed

Updated Wiki: Home

JBBrown — Thu, 03 Jun 2010 20:22:53 GMT

The most complete solution for TFS Code Reviews

The most complete solution for Team System Code Reviews: a specific work item type and a Visual Studio add-in for a completely in IDE code review experience. TeamReview exploits the advantages of Team System and VSX to reduce waste and surface new business value from code reviews

TeamReview Work Flow Overview poster (full version of below) - low and high res available
TeamReview Advantages
TeamReview Introduction / How-To Video (6 minutes 39 seconds)
TeamReview By Example
What other people think about TeamReview
More on the business value of TeamReview

Poster created by Willy-Peter Schaub, VSTS MVP and hosted by the Developer Readiness Program community server and the South Africa Architect community server

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

(top)

TeamReview by Example

Jane Coder submits a request to review code by entering a new Task and assigning it to Joe CodeReviewer

Then in the IDE Joe CodeReviewer right clicks and uses the TeamReview menu

In the New Code Review Response form Joe selects a Team Query to find Jane's request and then fills out the information and assigns the new Code Review Response to Jane. Note here that the Title is pre-filled by TeamReview

Joe finds another contentious point and uses TeamReview again. This time TeamReview pre-populates the "Query From", "Associate With", and "Assign To" values using the information from the last time.

When Joe is done submitting feedback he re-assigns the original review request from Jane back to her (not shown). Now the review is over and the original code author, Jane, wants to see what feedback was given. She uses the "Code Review Replay" option of TeamReview

The Code Review Replay window comes up and Jane chooses a Team Query to identify her original review request.

Jane starts replaying Joe's feedback by selecting each row in the grid one-by-one, and as she does TeamReview re-opens and re-highlights the section of code Joe originally noted as having an issue.

Jane fixes the code from Joe's feedback and then wants to close the Code Review Response, so she double-clicks in the Code Review Replay Window to open the Work Item.

Of course all of this works because TFS is being used in the background. Here's what Jane's original request looks like with the linked Code Review Response items.

And here is what the Code Details tab of one of those items, Joe's feedback, looks like - with all the code heuristic details available for querying and reporting by TFS or SQL Reporting Services.

(top)

Updated Wiki: Home

JBBrown — Sat, 19 Dec 2009 22:22:28 GMT

The most complete solution for Team System Code Reviews

TeamReview Work Flow Overview poster (full version of below) - low and high res available
TeamReview Advantages
TeamReview Introduction / How-To Video (6 minutes 39 seconds)
TeamReview By Example
What other people think about TeamReview
More on the business value of TeamReview

Poster created by Willy-Peter Schaub, VSTS MVP and hosted by the Developer Readiness Program community server and the South Africa Architect community server

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

(top)

TeamReview by Example

Updated Wiki: Home

JBBrown — Tue, 26 May 2009 05:11:23 GMT

The most complete solution for Team System Code Reviews

TeamReview Work Flow Overview poster (full version of below) - PDF (low-medium quality), JPG (high quality)
TeamReview Advantages
TeamReview Introduction / How-To Video (6 minutes 39 seconds)
TeamReview By Example
What other people think about TeamReview
More on the business value of TeamReview

Poster created by Willy-Peter Schaub, VSTS MVP and hosted by the Developer Readiness Program community server and the South Africa Architect community server

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

(top)

TeamReview by Example

Updated Wiki: Home

JBBrown — Mon, 25 May 2009 22:41:56 GMT

The most complete solution for Team System Code Reviews

TeamReview Work Flow Overview poster (full version of below) - PDF (low-medium quality), JPG (high quality)
TeamReview Advantages
TeamReview Introduction / How-To Video (6 minutes 39 seconds)
TeamReview By Example
What other people think about TeamReview
More on the business value of TeamReview

Poster created by Willy-Peter Schaub, VSTS MVP and hosted by the Developer Readiness Program community server and the South Africa Architect community server

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

(top)

TeamReview by Example

Updated Wiki: Home

JBBrown — Mon, 25 May 2009 13:34:29 GMT

The most complete solution for Team System Code Reviews

TeamReview Work Flow Overview poster (full version of below) - PDF (low-medium quality), JPG (high quality)
TeamReview Advantages
TeamReview By Example
What other people think about TeamReview
More on the business value of TeamReview

Poster created by Willy-Peter Schaub, VSTS MVP and hosted by the Developer Readiness Program community server and the South Africa Architect community server

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

(top)

TeamReview by Example

Updated Wiki: Home

JBBrown — Fri, 22 May 2009 22:59:36 GMT

New Business Value From Code Review

TeamReview Work Flow Overview poster (full version of below) - PDF (low-medium quality), JPG (high quality)
TeamReview Advantages
TeamReview By Example
What other people think about TeamReview
More on the business value of TeamReview

Poster created by Willy-Peter Schaub, VSTS MVP and hosted by the Developer Readiness Program community server and the South Africa Architect community server

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

(top)

TeamReview by Example

Updated Wiki: Home

JBBrown — Thu, 16 Apr 2009 20:21:09 GMT

New Business Value From Code Review

TeamReview Work Flow Overview poster (full version of below) - PDF (low-medium quality), JPG (high quality)
TeamReview Advantages
TeamReview By Example
What other people think about TeamReview
More on the business value of TeamReview

Poster created by Willy-Peter Schaub, VSTS MVP and hosted by the Developer Readiness Program community server and the South Africa Architect community server

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

(top)

TeamReview by Example

Updated Wiki: Home

JBBrown — Mon, 01 Sep 2008 22:10:56 GMT

New Business Value From Code Review

TeamReview exploits the advantages of Team System and the Vs.net extensibility model to reduce transition waste and surface new value from the code review process. Using Work Items to facilitate the code review process creates a completely in-IDE code review experience, the ability to project-manage the code review tasks, and the opportunity to get new value from the code review process through code review forensics.

TeamReview Work Flow Overview poster (full version of below) - PDF (low-medium quality) , JPG (high quality)
TeamReview Advantages
TeamReview By Example
What other people think about TeamReview
More on the business value of TeamReview

Poster created by Willy-Peter Schaub, VSTS MVP and hosted by the Developer Readiness Program community server and the South Africa Architect community server

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

(top)

TeamReview by Example

Updated Wiki: Home

JBBrown — Mon, 01 Sep 2008 20:42:11 GMT

New Business Value From Code Review

TeamReview Work Flow at a Glance Poster (full version of below) - PDF (low-medium quality) , JPG (high quality)
TeamReview Advantages
TeamReview By Example
What other people think about TeamReview
More on the business value of TeamReview

Poster created by Willy-Peter Schaub, VSTS MVP and hosted by the Developer Readiness Program community server and the South Africa Architect community server

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

(top)

TeamReview by Example

Updated Wiki: Home

JBBrown — Mon, 01 Sep 2008 19:57:55 GMT

New Business Value From Code Review

TeamReview Advantages
TeamReview By Example
TeamReview Work Flow at a Glance Poster (full version of below) - PDF (low-medium quality) , JPG (high quality)
What other people think about TeamReview
More on the business value of TeamReview

Poster created by Willy-Peter Schaub, VSTS MVP and hosted by the Developer Readiness Program community server and the South Africa Architect community server

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

(top)

TeamReview by Example

Updated Wiki: Home

JBBrown — Thu, 21 Aug 2008 21:04:47 GMT

TeamReview by Example

New Business Value From Code Review

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

TeamReview Press

What other people think about TeamReview - https://www.codeplex.com/Thread/View.aspx?ProjectName=TeamReview&ThreadId=26947

Updated Wiki: Home

JBBrown — Fri, 20 Jun 2008 19:08:44 GMT

New Business Value From Code Review

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

TeamReview Press

What other people think about TeamReview - https://www.codeplex.com/Thread/View.aspx?ProjectName=TeamReview&ThreadId=26947

TeamReview by Example

UPDATED WIKI: Home

JBBrown — Thu, 01 May 2008 18:03:43 GMT

Making Code Review Less Painful

Use this Visual Studio Add-In to leverage Team System and the Visual Studio code object model for in-IDE code review feedback, demonstration, and review replay. The inspiration for this project are the many code reviews we've experienced that have been generally underwhelming experiences and less than optimal outcomes. To make code review less painful, and to greatly assist in distributed environment code reviews this project will add Code Review squarely into the VS.Net Team System tools.

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

TeamReview Press

What other people think about TeamReview - https://www.codeplex.com/Thread/View.aspx?ProjectName=TeamReview&ThreadId=26947

TeamReview by Example

UPDATED WIKI: Home

JBBrown — Thu, 01 May 2008 18:02:53 GMT

Making Code Review Less Painful

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

TeamReview Press

What other people think about TeamReview - https://www.codeplex.com/Thread/View.aspx?ProjectName=TeamReview&ThreadId=26947

TeamReview by Example

Jane Coder submits a request to Review Code - she assigns it to Joe CodeReviewer

Then in the IDE Joe CodeReviewer right clicks and uses the TeamReview menu

In the New Code Review Response form Joe selects a Team Query to find Jane's request and then fills out the information and assigns the new Code Review Response to Jane. Note here that the Title is pre-filled by TeamReview

Joe finds another contentious point and uses TeamReview again. This time TeamReview pre-populates the "Query From", "Associate With", and "Assign To" values using the information from the last time.

When Joe is done submitting feedback he re-assigns the original review request from Jane back to her (not shown). Now the review is over and the original code author, Jane, wants to see what feedback was given. She uses the "Code Review Replay" option of TeamReview

The Code Review Replay window comes up and Jane chooses a Team Query to identify her original review request.

Jane starts replaying Joe's feedback by selecting each row in the grid one-by-one, and as she does TeamReview re-opens and re-highlights the section of code Joe originally noted as having an issue.

Jane fixes the code from Joe's feedback and then wants to close the Code Review Response, so she double-clicks in the Code Review Replay Window to open the Work Item.

Of course all of this works because TFS is being used in the background. Here's what Jane's original request looks like with the linked Code Review Response items.

And here is what the Code Details tab of one of those items, Joe's feedback, looks like - with all the code heuristic details available for querying and reporting by TFS or SQL Reporting Services.

UPDATED WIKI: Home

JBBrown — Thu, 01 May 2008 18:02:35 GMT

Making Code Review Less Painful

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

TeamReview Press

What other people think about TeamReview - https://www.codeplex.com/Thread/View.aspx?ProjectName=TeamReview&ThreadId=26947

TeamReview by Example

UPDATED WIKI: Home

JBBrown — Thu, 01 May 2008 17:54:59 GMT

Making Code Review Less Painful

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

TeamReview Press

What other people think about TeamReview - https://www.codeplex.com/Thread/View.aspx?ProjectName=TeamReview&ThreadId=26947

TeamReview by Example

UPDATED WIKI: Home

JBBrown — Thu, 01 May 2008 17:54:26 GMT

Making Code Review Less Painful

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

Press on TeamReview

What other people think about TeamReview - https://www.codeplex.com/Thread/View.aspx?ProjectName=TeamReview&ThreadId=26947

TeamReview by Example

UPDATED WIKI: Home

JBBrown — Wed, 30 Apr 2008 23:25:29 GMT

Making Code Review Less Painful

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

TeamReview by Example

UPDATED WIKI: Home

JBBrown — Tue, 29 Apr 2008 21:12:48 GMT

Making Code Review Less Painful

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

TeamReview by Example

Jane Coder submits a request to Review Code - she assigns it to Joe CodeReviewer

Then in the IDE Joe CodeReviewer right clicks and uses the TeamReview menu

In the New Code Review Response form Joe selects a Team Query to find Jane's request and then fills out the information and assigns the new Code Review Response to Jane. Note here that the Title is pre-filled by TeamReview

Joe finds another contentious point and uses TeamReview again. This time TeamReview pre-populates the "Query From", "Associate With", and "Assign To" values using the information from the last time.

When Joe is done submitting feedback he re-assigns the original review request from Jane back to her (not shown). Now the review is over and the original code author, Jane, wants to see what feedback was given. She uses the "Code Review Replay" option of TeamReview

The Code Review Replay window comes up and Jane chooses a Team Query to identify her original review request.

Jane starts replaying Joe's feedback, and as she does TeamReview re-opens and re-highlights the section of code Joe originally noted as having an issue.

Jane fixes the code from Joe's feedback and then wants to close the Code Review Response, so she double-clicks in the Code Review Replay Window to open the Work Item.

Of course all of this works because TFS is being used in the background. Here's what Jane's original request looks like with the linked Code Review Response items.

And here is what the Code Details tab of one of those items, Joe's feedback, looks like - with all the code heuristic details available for querying and reporting by TFS or SQL Reporting Services.

UPDATED WIKI: Home

JBBrown — Mon, 21 Apr 2008 21:12:34 GMT

Making Code Review Less Painful

TeamReview Advantages

No/less code review meetings necessary
Same place/Same time obstacles are overcome
Makes code review analytics/forensics possible
Easier to split up code reviews both over time and to many people
Accountability - can easily determine if any review feedback was submitted and if that feedback was implemented
Ability to create predefined in-IDE code walk-throughs by any developer on your project without requiring your attendance

TeamReview by Example

Jane Coder submits a request to Review Code - she assigns it to Joe CodeReviewer

Then in the IDE Joe CodeReviewer right clicks and uses the TeamReview menu

In the New Code Review Response form Joe selects a Team Query to find Jane's request and then fills out the information and assigns the new Code Review Response to Jane. Note here that the Title is pre-filled by TeamReview

Joe finds another contentious point and uses TeamReview again. This time TeamReview pre-populates the "Query From", "Associate With", and "Assign To" values using the information from the last time.

When Joe is done submitting feedback he re-assigns the original review request from Jane back to her (not shown). Now the review is over and the original code author, Jane, wants to see what feedback was given. She uses the "Code Review Replay" option of TeamReview

The Code Review Replay window comes up and Jane chooses a Team Query to identify her original review request.

Jane starts replaying Joe's feedback, and as she does TeamReview re-opens and re-highlights the section of code Joe originally noted as having an issue.

Of course all of this is possible because the information is being stored as work items in TFS. Here's Jane's original review request with the linked "Code Review Response" work items.

And here is what one of those associated work items, Joe's feedback, looks like - with all the code heuristic details available for querying and reporting by TFS or SQL Reporting Services.