Meet with your team and review the project plan assigned to you.

Through two sessions, you will be critiquing the other team's plan in several areas. Be sure to provide thorough/constructive feedback, and after the fact be sure to account for legitimate feedback provided by another team to your plan.

When your review is complete, please share your findings with the other team's PM and submit to the appropriate dropbox.

Names of Reviewing Team Members Team Being Reviewed
Names Group XX

Project Plan Peer Review Areas - Artifact 1

Area Comments
Problem/Opportunity Statement
  • Is the problem or opportunity clear?
  • Would a bystander get a clear picture of what the project is about without reading the scenario given to the team?
Goals and/or Projected Benefits
  • Are the goals/benefits appropriate and achievable?
  • Do they fit the previously defined problem/opportunity statement?
Initial Stakeholder List
  • Though brief, does this list show proper consideration of high-level stakeholders for the given project?
  • Does the list include both internal and external stakeholder groups?
Project Organizational Structure
  • Is the team structure appropriate for the project at hand (its scope, etc.)?
  • Does this section go beyond basic identification of the team, bringing in elements of the larger organization, team members' level of experience, etc.?
Scope Statement
  • It it clear to the reader what is and what isn't included as part of the project's deliverables?
  • Does the scope statement seem to include the right level of detail?

Project Plan Peer Review Areas - Artifacts 2 and 3

Area Comments
Changes Made to Artifact 1: Overview, Organizational Structure, and Scope
  • Has the first artifact improved or been refined?
  • Do the changes made reflect suggestions given?
Methodology Analysis
  • Does each analysis properly addresses strengths, weaknesses, team, and organizational structure specifically in the context created by the first artifact?
  • Are the risks appropriate and distinct between each analyzed methodology?
Chosen Methodology
  • Is the chosen methodology appropriate for the conditions of the scenario/scope with well-supported reasoning?
  • Are the additional risks realistic, reaching beyond the methodology itself?
Work Breakdown Structure (WBS)
  • Does the WBS cover the entire scope defined in a previous artifact?
  • Is the WBS consistent and follow the 1-2 rule?
Continue with either Plan-Driven or Agile depending on the choice made in the team being reviewed's artifact.
Plan-Driven
  • Estimation Process - Did the team arrive at their estimates in a logical, well-laid-out manner?
  • Estimations - Do the estimations cover everything in the WBS?
  • Schedule/Gantt Chart - Is this a proper Gantt chart? Is there proper consideration for sequencing and resource assignation?
Agile
  • Technical Process - Does the artifact clearly convey how the team is to operate, the mechanics of meetings, user stories, etc.?
  • Product Backlog - Do the user stories have correct form and story points? Do they account for the entire scope of the project/WBS?
  • Sprint 1 Backlog - Are these the right stories for sprint 1? Are they fully elaborated?