What has been accomplished at the end of MSD 1 & 2?

MSD End State Expectations High Level MSD 1 & 2 Outcomes Your Customer and Team are enjoying a working prototype. You have Delighted Customers like Dr. Roman Press & Jeff Gutterman from Team Your Team executed an effective design process. You grew as an engineer and were part of a productive Project Team.

Student Takeaways from the MSD Experience Project Completion ◦Satisfaction that comes with real accomplishment ◦Something to add to your resume and highlight during job interviews Process Competence ◦Methods and tools to execute the engineering design & delivery process that you can use on any future project Individual Contribution & Personal Development ◦Project ownership and effectiveness in a diverse team setting ◦Personal growth and increased confidence in engineering, problem solving, and presentation skills MSD End State Expectations

Project Completion – Ideal Working prototype is delivered All requirements are verified by test data All required documentation is delivered Possible improvements are identified Customer is satisfied if not delighted MSD End State Expectations

Project Completion – Typical Most functionality is delivered Most requirements are verified by test data Essential documentation is delivered Shortfalls are identified with action plans Possible improvements are identified Customer is satisfied MSD End State Expectations

Process Competence – Ideal Design, development & delivery process is rational, traceable and documented. Methods and tools utilized are appropriate, effective, and efficient. Team prepared, followed, and continuously updated a plan leading to predictable outcomes. MSD End State Expectations

Process Competence – Typical Design, development & delivery process was not consistently followed, but it was rational, traceable, and reasonably well documented. Methods and tools utilized are mostly appropriate, effective, and efficient. Team prepared and generally followed a plan leading to mostly predictable outcomes. MSD End State Expectations

Individual Contribution – Ideal Accepted, understood, & took ownership – “did everything you could” Exhibited positive, constructive, & professional behavior at all times Individual Contribution – Typical Generally took ownership – contributed significantly but missed some opportunities Generally exhibited constructive & professional behavior with some exceptions during crises MSD End State Expectations

Be sure to consider all key stakeholders Your Customer & Sponsor ◦Would I pay for what was delivered? ◦Could they do it again (because they understood & followed good process)? ◦Would I hire these young engineers? Your Team – discuss !! ◦Learned to resolve conflicts? Started to appreciate process and value of planning & risk assessment? Applied appropriate engineering analysis? Faculty ◦Students achieved learning objectives MSD End State Expectations

The Journey – MSD I & II 30 weeks (6 credits) ◦MSD I: Project definition and design ◦MSD II: Prototype development and delivery Design & delivery process defined by RIT faculty ◦Five 3-week phases each semester ◦Review and grading after each phase Students take ownership – utilize process methods & tools to define, develop and deliver expected outcomes, implement peer reviews All engineers utilize appropriate analysis tools to support engineering decision making MSD End State Expectations

MSD I WksPhaseDeliverables 1-3 Problem Definition Customer Requirements, Engineering Requirements (& Relationship Diagram), Project Plan 4-6 System Design Functional Decomposition, Concepts Developed, Engineering Analysis to support critical technology, Architecture, Test Plan, Risk Assessment, Update Project Plan 7-9 Subsystem Design (High Technical Risk) Requirements Flowdown, Engineering Analysis to demonstrate feasibility of critical subsystems, Update Test Plan, Update Risk Assessment, Update Project Plan Detailed Design (High & Med Technical Risk) Design Output (drawings, schematics, layouts, algorithms, BOM), Engineering Analysis to support Detailed Design, Update Test Plan, etc Complete Design (Low Technical Risk) Complete Design Output (…), Design Package Completion, Ready to order long lead time parts 16MSD I WrapupGate Review – Readiness for MSD II

MSD End State Expectations MSD II WksPhaseDeliverables 1-2 Subsystem Level Prep/Build & Action Items (if failed Gate Review) Test Bench setup, simulation, analysis, Create Problem List, Update Test Plan & Project Plan 3-5 Build/Test/Integrate Subsystem Level Testing, simulation, analysis, Subsystem Function Demo, Update Problem Status, Test Plan, Project Plan 6-8 Build/Test/Integrate Subsystem & System Level Execute overall Test Plan to evaluate performance, Preliminary Integrated System Demo, Update Problem Status, Conference Paper Outline 9-11 Build/Test/Integrate System Level Continue full system testing for reliability, Full Integrated System Demo with Customer, Project Documentation Complete Verification & Validation Project Complete Complete full system testing for reliability Project Complete – handoff obligations to Customer Complete Paper & Poster, ImagineRIT 15Final Presentation & ReviewCompletion of MSD II

MSD End State Expectations MSD II WksPhaseDeliverables 1-2 Subsystem Level Prep/Build & Action Items (if failed Gate Review) Test Bench setup, simulation, analysis, Create Problem List, Update Test Plan & Project Plan 3-5 Build/Test/Integrate Subsystem Level Testing, simulation, analysis, Subsystem Function Demo, Update Problem Status, Test Plan, Project Plan 6-8 Build/Test/Integrate Subsystem & System Level Execute overall Test Plan to evaluate performance, Preliminary Integrated System Demo, Update Problem Status, Conference Paper Outline 9-11 Build/Test/Integrate System Level Continue full system testing for reliability, Full Integrated System Demo with Customer, Project Documentation Complete Verification & Validation Project Complete Complete full system testing for reliability Project Complete – handoff obligations to Customer Complete Paper & Poster, ImagineRIT 15Final Presentation & ReviewCompletion of MSD II

MSD End State Expectations MSD GRADING Emphasis Project Completion 70% Process Followed & Tool Usage 20% Personal Contribution to Team 10%

MSD End State Expectations Grade Definitions *Letter Grade ScoreBrief DescriptionLonger Description A+100 Outstanding (Work is high quality) - Deliverables completed and high quality; - Executed process and used process tools very effectively; - Took ownership of the project by consistently demonstrating initiative, persistence, and process discipline. A95 A-92 B+88 Good to Very Good (Work is satisfactory) - Deliverables completed and acceptable; - Executed process and used process tools satisfactorily; - Took some ownership of the project by demonstrating periodic initiative, persistence, and process discipline. B85 B-82 C+78 Minimally Acceptable (Most work is satisfactory) - Deliverables minimally acceptable but incomplete in some areas; - Process haphazardly followed, not intelligently or efficiently applied; - Lacked ownership of the project by seldom demonstrating initiative, persistence, or process discipline. C75 C-72 D+68 Unacceptable (Less than half of the work is satisfactory) D65 D-62 F55 Disaster (Little to none of the work is satisfactory) Guide reserves the right to assign a score lower than 55 if less than 55% of the work has been done. MSD GRADING RUBRIC Grade Expectations B is a good to very Good outcome A is an outstanding Outcome. (It is not the Default)

Comments Project-based course – no “right” answers, only better solutions All projects have QCD goals ◦Quality = What will be delivered as defined by performance metrics, etc… ◦Cost = Cost incurred to deliver the what ◦Delivery = When the what is delivered MSD Projects can be ◦A working device or a “process” for accomplishing something – both are prototypes ◦First time attempt or leverages a prior MSD project MSD End State Expectations

Comments Expect that deliverables must be iterated & refined – see Schedule for details Expect that you must exhibit dynamic zoom – consider the 20,000 ft. view, a system level view and a detailed view. Move in and out until you get convergence and coherence. Ensure coherence of your documentation: eg. major technical risks should be supported by a set of activities on the schedule. MSD End State Expectations

Final Thoughts Ownership & Accountability Discipline Teamwork Communication (internal, external) Personal satisfaction & growth Great results Customer satisfaction Good grade Enjoyment MSD End State Expectations