Complete Design & Gate Review. Complete Design Detailed Design Review (DDR) 1.“High and medium technical risk” areas –Design Review (Prelim-DDR): standard.

Slides:



Advertisements
Similar presentations
MICS4 Survey Design Workshop Multiple Indicator Cluster Surveys Survey Design Workshop General Structure of a Survey Plan.
Advertisements

Project Management Concepts
Roadmap for Sourcing Decision Review Board (DRB)
’s TechStat Framework Agency Seal. Agenda 1.TechStat Overview 2.TechStat Process 3.Managing Outcomes 2.
PROJECT TITLE Project Leader: Team: Executive Project Sponsor (As Required): Date: Month/Day/Year 110/17/2014 V1.
TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE.
Project Control Techniques
Project Management Process. Project Complexity means that: a team of people are needed to supply expertise the work needs to be broken into manageable.
P10511: Miniaturization of Xerography Derek Meinke (ME, PM) Matthew Liff (ME) Tony Zhang (EE) Zaw Htoo (ISE)
Project Review. Current State Currently on track to meet our mission objectives and cover all customer needs – Unpredictable to know whether or not sensors.
Making Sense of the WIC EBT IAPD IAPD Session of the 2014 WIC EBT User Group Meeting July 23, :00 AM to 12:00 PM Presented by Cheryl Owens, MAXIMUS.
MSD-I Project Review Modular Motion Tracking Sensors 1.
ELC 347 DAY 7. Agenda Questions Assignment 3 Due Assignment #4 posted  Due next week Group Progress report due next week Exam 2 next week  Same format.
Design Reviews.1 KGCOE Multidisciplinary Sr. Design Borkholder 2007 R I T Design Reviews Objectives of the Design Review Participants for a successful.
Team Sponsor Defines team ’ s work boundary. Appoints team leader. Receives and reviews team reports. Reviews and critiques team recommendations. Visits.
Design Reviews.1 KGCOE Multidisciplinary Sr. Design Borkholder 2006 R I T Design Reviews Objectives of the Design Review Participants for a successful.
Project Name Steering Committee Meeting Project Manager: Project Manager Name Program Manager: Program Manager Name Project Sponsor: Project Sponsor Name.
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
Your Name Agency Where are you from Position on Team Your Course Expectations.
Guide Workshop Tuesday, August 19, Agenda I.MSD Fall 14 Logistics Werth –45 minutes 1.Class Schedule high level 2.Grading Period Highlights 3.MSD.
Discussion Items with Bruce
S/W Project Management
McLean & Company1 Improving Business Satisfaction Moving from Measurement to Action.
Software Engineering Chapter 15 Construction Leads to Initial Operational Capability Fall 2001.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
T Project Review RoadRunners [PP] Iteration
T Software Development Project I Customer Info Jari Vanhanen Ohjelmistoliiketoiminnan ja –tuotannon laboratorio Software Business and.
10/10/2015 IENG 471 Facilities Planning 1 IENG Lecture END Project Report Requirements & Project Presentation Information.
InTeGrate Assessment David Steer, University of Akron Ellen Iverson, Carleton College May 2012.
Project Post-Mortem University of California Berkeley Extension Copyright © 2008 Patrick McDermott From an AutoContent Wizard 10/27/2007.
Executive Session Director’s CD-3b Review of the MicroBooNE Project January 18, 2012 Dean Hoffer.
AREVA T&D Security Focus Group - 09/14/091 Security Focus Group A Vendor & Customer Collaboration EMS Users Conference September 14, 2009 Rich White AREVA.
Detailed Design & Component Selection. Detailed Design Phase Portion of the engineering design process where the engineering team can completely describe.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
6/3/2016 IENG 471 Facilities Planning 1 IENG 465 – Final Design Project Report & Presentation Requirements.
PM00. 6 Project Management Preparation for Success
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
SOLUTION What kind of plan do we need? How will we know if the work is on track to be done? How quickly can we get this done? How long will this work take.
Module 5 Session 5.2 Visual 1 Module 5 Refining Objectives, Scope, and Other Project Parameters Session 5.2 Reviewing the PAR and refining key project.
ESSRT Status Report as of July 31, 2013
T Iteration Demo Tikkaajat [PP] Iteration
MSD END-STATE EXPECTATIONS. Today’s Agenda 7:30-7:59 Continental Breakfast & Reconnecting 8:00 Review of Agenda Workshop with students –EH 8:02-8:30 MSD.
Meeting Practices Yan Wei Foundation Extreme programming is used Meeting practices are based on extreme programming technology with.
2/27/2016 IENG 471 Facilities Planning 1 IENG 464 – Conceptual Design Project Report & Presentation Requirements.
1 Chapter 8 karvaytMélKMerag nig kareFVIr)aykarN_ nig karbiTKMerag Project Evaluation, Reporting, and Termination.
 Prepare  Study the agenda  Study the minutes  Prepare for your contributions  Prepare to play a major role  List questions.
What has been accomplished at the end of MSD 1 & 2?
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
Strana 1MBA kurz informačního inženýrství INITIATE CONSTRUCT DELIVER MAINTAIN & SUPORT quality assurance, manage project, trainig&education, manage.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
MGT 437 OUTLET Become Exceptional/mgt437outlet.com FOR MORE CLASSES VISIT
Director’s Progress Review Closeout Meeting
Sample Fit-Gap Kick-off
Office 365 Security Assessment Workshop
VAR Preparation Meeting
Project Management Lifecycle Phases
[Project Name] Post-Mortem
PROJECT NAME POST-MORTEM
Project Roles and Responsibilities
Director’s Progress Review Closeout Meeting
IS&T Project Reviews September 9, 2004.
[Project Name] Post-Mortem Presentation Template
Project Name Post-Mortem
QA Reviews Lecture # 6.
P Nano-ink Deposition System Detail Design Review
CS 410 Professional Workforce Development I Spring 2019
Software Reviews.
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

Complete Design & Gate Review

Complete Design Detailed Design Review (DDR) 1.“High and medium technical risk” areas –Design Review (Prelim-DDR): standard format PLUS focused meetings w/ subject-matter-experts 2.“Low technical risk” areas (& action items from 1 st phase) – complete detailed design –Design Review (DDR): standard format ( min) –You may need more time or multiple sessions

Questions to answer What is your evidence that your design will meet requirements (inspection, reference, analysis)? Have you demonstrated proof-of-concept (all critical areas)? Have all factors influencing operation been considered? What can the user do "wrong" and how will your design respond? Are all drawings, schematics, flow charts, and other artifacts complete (everything needed to physically and functionally realize your system)? Have long lead items and vendors been identified and reviewed against budget? How are you going to test for each requirement? What is your most challenging subsystem to build, and have you ensured enough time to complete it? What is each team member planning to work on during MSD II??

Deliverables (see rubric) Complete design output including BOM (see previous presentation & questions to answer) – sufficient information to order long lead time parts and implement the design All design documentation (complete & up-to-date on EDGE). See P13026, P13011, P12361 websites Engineering requirements (complete) Test plan (rev 1 complete, addresses all requirements, equipment & procedures defined, traceable to engr. rqmts) Risk assessment, mitigation plans & triggers MSD II plan (rev 1 but with project-specific detail)

DDR – Who You Should Invite All team members should contribute Guide People who can help you by critically reviewing your design: –Technical experts – faculty, others –Customer (if appropriate) – technical expertise, or to represent the user(s) (go/no-go)

DDR – Logistics 90 – 120 min. recommended: available times during class: 2:00- 3:30 or 3:30-5:00. More time may be needed. Prepare detailed agenda – allocate time to most critical areas and highlight times for specific (discipline) attendees Invite participants in advance and distribute materials w/in 48 hrs All appropriate documentation on laptop or hardcopy (examples: P13026, P13011) Manage agenda Emphasis is on review, NOT on “presentation” Take notes! Questions, critiques, action items, decisions Ask experts if your design is ready for build & test phase Update EDGE with notes and design documents

Gate Review (exam week) Management level review of project status & readiness for build & test (MSD II) 1 hour duration is expected – you schedule with Guide All team members, Guide, and Customer (if “go/no-go” decision on funding has not been provided) Assessment of design readiness for MSD II (Guide) –Green light = “ready” in most areas: rqmts complete, design will meet customer rqmts and is supported by customer, sufficient detailed design info exists to implement design –Red light = “not ready”: significant issues exist before build-test => Action plans needed + Critical Design Review by week 2 “I” grade are rarely used and ONLY for circumstances beyond your control

Gate Review (exam week) Grades: review any outstanding deliverables for final phase Meeting notes & action items: must be posted on EDGE before final grades will be issued See MyCourses handout (“MSD I Gate Review”) for more detail to help you prepare

Schedule MSD II Prep: review action items, check delivery status Wks 1-2: –Resolve MSD I action items, post-mortem –If “red light”: hold Critical Design Review –Update Project Plan & Test Plan (rev 2) –Ready testing resources for implementation Wk 14 (5/5-9) MTWRF Wk 16 (5/12-16) MTWRF Exams (5/19-22) MTWR DDR Gate Review