Project Learning in Capstone Design See examples from past capstone projects at http://seniordesign.engr.uidaho.edu and www.mindworks.shoutwiki.com

Product Development is a Process!! Project Learning is part of the Process Project Learning Roadmap Conceptual Design / Prototyping Detailed Design Fabrication Validation Product

Goals for Project Learning Agreement on the Scope of the project What is the target? (i.e. when are we DONE?) What knowledge and skills are required to achieve the target? You Are Here! Project Learning Roadmap Conceptual Design / Prototyping Detailed Design Fabrication Validation Product

Importance of Project Learning Opportunity to be Innovative Cost of Change (Mistakes) Project Timeline Project Learning Roadmap Conceptual Design / Prototyping Detailed Design Fabrication Validation Product

Where to Spend Resources? Early in the Design Process Later in the Design Process Broadly defined project Idea generation Problem definition High level engineering analysis Detailed design Design refinement Experts Spend a Lot of Time Here! Project learning adds value (Jain and Sobek, Atman)

Three Areas of Project Learning People User groups Focus groups Ride-Alongs Product Competitive Analysis Observations Dissection Technology Experimentation Prototyping Math Models

Identify Stakeholders and Experts Stakeholders have interest in new product External customers: Purchaser End user Internal customers: Manufacturing Marketing / Service / Aftermarket Financial / Business leaders What is important to each of them? Experts have specific knowledge Usually have years of experience Know the pitfalls and solutions tried before Can help you focus your direction But, don’t let them close your mind Who are your stakeholders? People

Interviewing Stakeholders Groups  Individuals Find out the needs and constraints Focus on “What is needed?” Not on “How to do it?” Often, stakeholders want to think about solutions and share their own experiences Take a step back  Needs People

Ask Questions & Challenge Assumptions The 5 Whys: Root Cause Analysis: The “problem”. Why? My car won’t start. The battery is dead. Alternator doesn’t work. Belt is broken. Belt is old. Car has not been maintained regularly. Root Cause! People

Do you have a list of at least 20 good questions for your client? Interview Guidelines Observe things that unspoken A simple requirement can be overlooked Confirm things that are said Is it clear? Communicate back to customer Clarify priorities Must, should, wish Prioritize complete needs list LISTEN - Let the user/client talk Follow up for clarification  5 whys? Take good notes Be prepared with a list of questions. Do you have a list of at least 20 good questions for your client? People

What needs does your project have in each of these areas? Product Attributes Functional performance Speed, efficiency, flow rate, temperature range, etc. Human factors Ergonomics, noise level, visibility, etc. Physical requirements Size, color, mounting method Reliability Quality Durability  Useful life Manufacturing requirements Serviceability Cost (to acquire, own, and maintain) What needs does your project have in each of these areas? People

Observe the product in use People often do not realize opportunities, realize their problems, or communicate all needs Apply anthropological techniques Document activities Characterize user types Characterize value to user “This is the way we’ve always done it.” People

Empathetic Activities First-hand experience is a great way to grow understanding Use the product Perform the process Experience the hardship! Ride-along How will you interact with and understand your client’s concerns? People

Competitive Analysis Evaluate competitor products (or prior solutions) Teardown  systems  parts Benchmark each attribute Estimate cost Who is your competition? What are their strengths? What are their weaknesses? Product

Every project has a customer. Who is yours? What do they value? Value Proposition Know how your competitor is viewed Know how your customer makes decisions What is important? What is not important? What unique value can you bring? Every project has a customer. Who is yours? What do they value? Product

Mock-ups and Calculation models Evaluate subjective requirements (e.g. ergonomics) What happens if I change this? Calculation Models Governing equations Align with experiment Sensitivity to changing parameters What simple test or math model can you use today to learn more about your project? Technology

Research Emerging technologies (web/patent searches) Alternative materials Existing documentation Vendor catalogs What don’t you know? Technology

Codes & Standards Understand any Regulations Consult with experts These are foundational requirements Technology