XM Review Standards

=Review Standards=

Review is useful at many points of a development process. Together with Test-Driven Development, this can provide feedback necessary for project success - by converging on workable solutions more quickly than 'reinventing the wheel' or working by oneself. It should be noted that very few things are original - many things have been tried - so it's more worthwhile to search prior art than to reinvent the wheel.

The following list shows suggestions for successful review at various steps.

=Prior to Investment=

Review can be useful at the investment-searching stage, when proper review via third parties provides the necessary confidence to the investor.

Review may consist of calculation conclusions, verification of calculations, recommendations from others, peer review of the concept, etc.

=Prior to CAD Design=
 * Industry Standard Analysis
 * hat are the various systems in use
 * what is their design rationale
 * what lessons can we adapt to our work
 * who can we add to our Advisor List from those with experience?
 * What are the calculations, and can someone review those?
 * What is the SEBD, and can the Components be broken down even further?
 * What are the interfaces between the components, and are these interfaces well-defined?

Work product:
 * Status Log on XM Project Page reflects: review step, date of completion of review step, and link to the actual work

=After Design=

Review is useful after the design stage - when the design can be reviewed for:
 * Manufacturability - assessment of:
 * Welding hours required
 * Metal cutting and preparation
 * Hole-making
 * Machining requirements
 * Stock steel usage vs. weldments
 * Castings vs weldments
 * Modularity - what features would allow the system to be built as a 'construction set'?
 * Rapid Prototyping (RP) assessment
 * What RP would be useful to inform the build in a tangible way?
 * If RP is decided, redesign for easy prototyping according to XM Rapid Prototyping, where the build will be design for testing of various uncertainties or risk factors
 * Weight, and cost of base metal
 * Review of range of motion
 * Simulate desired range of motion via animation software or CAD
 * Obtain data points on distances and heights
 * CAE analysis for relevant features?
 * Strength, deformation, heat dissipation, etc.
 * Precision analysis - will the device have the precision or alignment required?
 * What are the tolerances and how do they add up?

=Advisors vs. Subject Matter Experts= Advisors, and in particular advisors who can be accessed within minutes of a problem being defined, are extremely useful - in their capacity for instant removal of blocks and challenges. An adviser is someone with perspective who can provide the correct direction to a project. A Subject Matter Expert (SME) is one who typically does the work after an adviser provides the correct direction. The SME does work, the Advisor affects the direction of work

=Addressing Blocks or Status of Development to Set Development Strategy=


 * 1) Define Problem Statement to involve others in development for transperancy and ability of both parties to assess the situation
 * 2) Quick video can show this.
 * 3) Introduce yourself if it's your first video
 * 4) For hardware, take object, picture, or design - and discuss it in an under 5 minute video for the component.
 * 5) Potentially set up space for this in XM Project Page
 * 6) CAD available for review - CAD is prerequisite
 * 7) In absence of CAD, drawings may suffice
 * 8) Static pictures for key mechanisms and processes presented clearly
 * 9) XM Project Page has review materials in a separate window?
 * 10) Everything documented at x Project XM Review page on wiki

=Review Steps by Joe=


 * No more process than absolutely necessary
 * Retrospective - what worked and didn't work
 * Invite all Advisors, SMEs to Demo
 * People doing work do retrospective.
 * Demo goes before retrospective
 * Sprint planning only if financed by stakeholder for another task

If you are a super successful scrum team, you can use a faster method - Kanban.
 * Avoids formalities of Scrum by all team members understanding this

Critique Review Steps in Scrum

 * Tradeoff - stakeholder does not interrupt, team goes heads down
 * Go off rails only to one spr int length. Team is heads down, focused, and empower
 * Review Flash Mob
 * If they are only review points, team does not learn
 * What is minimum of learning relationship? Being on the team.

Option for remote mentorship, work, collab

 * Pair on physical tasks can happen remotely
 * If paired work is remote, we can share screen.
 * Take design and redline work

=Other Review Steps=
 * XM Product Ecology Review
 * XM Fabrication Review
 * XM Component Test Procedure
 * XM_Product_Test_Procedure