I created this presenentation using pubic sources to explain how product development and product management are done at Intel. The audience were the management and employees of my company. My goal was to educate the audience on the possible ways we could do product management and development. I\'ve included hyperlinks to all the sources.

1. Product Development and Product Management at Intel PUBLIC DOCUMENT Kurt Shuler September 11, 2008

3. How is this presentation organized? 06/06/09 , Page PUBLIC DOCUMENT Exploration Planning Production Development Exploration Production Development Planning 3-5 yr ~1 yr

6. The Intel Product Life Cycle (a.k.a. the “IPLC”) has milestones with clear and measurable entrance and exit criteria… PRODUCT DOCUMENTS & REVIEWS Ship Release Approval (SRA) Product Discontinuance Approval (PDA) ROADMAPS Market Segment Analysis (MSA) Product Strategy Document (PSD) Source: Intel Quality Systems Handbook, Dec 2003, p. 5-3. Public document. BUSINESS INPUTS MILESTONES/ APPROVAL MEETINGS Internal Product Roadmap External Product Roadmap Product Overview Proposal (POP) / “MRD” Product Requirements Document (PRD) Design Specs and SoW Program Implementation Plan (PIP) Technical Product Specification (TPS) Product Readiness Review (PRR) Product ion Qualification (PDQ) PDT Postmortem Full Qualification (FLQ) Implementation Plan Approval (IPA) Development Investment Approval (DIA) Concept Approval (CA) 06/06/09 , Page PUBLIC DOCUMENT Exploration Planning Production Development Planning Production Development Exploration 3-5 yr ~1 yr Linking Strategy and Products

7. … but it is only a part of the complete strategy-to-product picture. Source: Intel Quality Systems Handbook, Dec 2003, p. 1-8. Public document. 06/06/09 , Page PUBLIC DOCUMENT 3-5 yr ~1 yr 3-5 yr ~1 yr Linking Strategy and Products

8. The PLC is easy to adapt to iterative development techniques like Extreme Programming and other methods of Agile development. Source: Erik Simmons, Intel Corp., Presentation, “Lessons Learned in Large Scale Process Improvement”, . Page 27. Public document. 06/06/09 , Page PUBLIC DOCUMENT 3-5 yr ~1 yr Linking Strategy and Products

9. Defining products is a part of the continuous strategic planning process. Source: Intel Quality Systems Handbook, Aug 2006, p. 11. Public document. SLRP = Documented Strategy and Market Segment Analysis (MSA) PLBP = Product Strategy Documents (PSD) and Roadmaps 06/06/09 , Page PUBLIC DOCUMENT 3-5 yr ~1 yr Linking Strategy and Products

10. Strategy, markets and business requirements tightly link to products. Sources: Intel presentation by Rudy Hacker, “Quality as an Information Systems Enabler.” Public document. Intel Quality Systems Handbook, Aug 2006, p. 11. Public document. Strategic Planning Product Development Business Strategic Objectives Market Segment Analysis (MSA) Product Strategy Document (PSD) Product Line and Technology Feedback With SLRP: With PLBP: POPs (“MRDs”) PRDs 06/06/09 , Page PUBLIC DOCUMENT Exploration Planning Production Development Exploration Planning Production Development Exploration Planning Production Development Single Product Life Cycle 3-5 yr ~1 yr Linking Strategy and Products

11. Intel balances Strategic and Tactical Decisions using the IPLC and Zero-Based Budgeting (ZBB). Market Strategy Product Life Cycle MSA From SLRP: From PLBP:     PSD Roadmaps Zero-Based Budgeting (ZBB) Strategic Decisions Tactical Decisions 06/06/09 , Page PUBLIC DOCUMENT Exploration Planning Production Development Exploration Planning Production Development Exploration Planning Production Development Single Product Life Cycle 3-5 yr ~1 yr Linking Strategy and Products

14. Internal and External Roadmaps graphically depict the product lines required to meet the business requirements in the PSD. 06/06/09 , Page PUBLIC DOCUMENT 3-5 yr ~1 yr Linking Strategy and Products

18. Concept Approval is required prior to starting a POP / MRD. An MRD is required prior to DIA. 06/06/09 , Page PUBLIC DOCUMENT Exploration Planning Production Development Exploration Phase PRODUCT DOCUMENTS & REVIEWS Ship Release Approval (SRA) Product Discontinuance Approval (PDA) Exploration Planning Production Development Planning Production Development Exploration ROADMAPS Market Segment Analysis (MSA) Product Strategy Document (PSD) BUSINESS INPUTS MILESTONES/ APPROVAL MEETINGS Internal Product Roadmap External Product Roadmap Design Specs and SoW Program Implementation Plan (PIP) Technical Product Specification (TPS) Product Readiness Review (PRR) Product ion Qualification (PDQ) PDT Postmortem Full Qualification (FLQ) Implementation Plan Approval (IPA) Development Investment Approval (DIA) Product Overview Proposal (POP) / “MRD” Product Requirements Document (PRD) Concept Approval (CA)

19. Many people perform many activities to create the POP / MRD and get to DIA. Success requires constant negotiation! * At a minimum, the Requirements Team consists of Product Management / Marketing, Engineering and Finance 06/06/09 , Page PUBLIC DOCUMENT What is Happening? Who is Doing it? Research Marketing, Engineering Prototyping Engineering Planning Program Manager Feasibility Analysis Engineering Understand Intel Channels, SLRP, PLBP and initiatives Requirements Team* Develop Business Plan, product vision, market window, etc. Marketing, Finance Define customers, users and usage models Marketing Create Revenue Forecast and ROI Marketing, Finance Create the POP (MRD) document Requirements Team Perform a Technical Review on the POP Requirements Team and others Communicate POP contents to broader team Requirements Team Conduct DIA meeting Requirements Team, Marketing, Engineering, etc. Baseline the POP (i.e. put under change control) Program Manager Exploration Planning Production Development Exploration Phase

29. After Development Investment Approval, the next step is the Planning Phase. Planning 06/06/09 , Page PUBLIC DOCUMENT PRODUCT DOCUMENTS & REVIEWS Ship Release Approval (SRA) Product Discontinuance Approval (PDA) Exploration Planning Production Development Planning Production Development Exploration ROADMAPS Market Segment Analysis (MSA) Product Strategy Document (PSD) BUSINESS INPUTS MILESTONES/ APPROVAL MEETINGS Internal Product Roadmap External Product Roadmap Design Specs and SoW Program Implementation Plan (PIP) Technical Product Specification (TPS) Product Readiness Review (PRR) Product ion Qualification (PDQ) PDT Postmortem Full Qualification (FLQ) Implementation Plan Approval (IPA) Development Investment Approval (DIA) Product Overview Proposal (POP) / “MRD” Product Requirements Document (PRD) Concept Approval (CA) Planning Phase

31. Many people work together on the PRD to get to IPA. Engineering is the author of the PRD. * At a minimum, the Requirements Team consists of Product Management / Marketing, Engineering and Finance Success requires constant negotiation! 06/06/09 , Page PUBLIC DOCUMENT What is Happening? Who is Doing it? Continued Prototyping Engineering Detailed Requirements Specification Requirements Team* Update information in POP / MRD as required Requirements Team* Write the PRD Engineering (author assigned at DIA) Establish requirements baseline Requirements Team* Perform a Formal Technical Review on the PRD Requirements Team and others (Engineering leads this) Detailed Project Planning All, with guidance from Program Manager Conduct IPA meeting Requirements Team, Marketing, Engineering, etc. Baseline the PRD (i.e. put under change control) Program Manager Planning Phase