DPM Example: Template for DPM Roadmap Planning
/public/

Stakeholders

Replace the contents of this page with information appropriate to your roadmapping team as you progress through the quarter

Identify and gather raw data from stakeholders here. Stakeholder groups for your project may include customers, users, sponsors, students, etc. Each stakeholder group should be represented by one or more individuals -- whom we refer to as stakeholder representative here. Your roadmapping team will interact with these stakeholder representative (through a combination of interviews, focus group, use cases, contextual observations, etc.) in an effort to better understand the needs of each stakeholder group as the are related to your project family.

Stakeholders
Stakeholder Groups Raw Data from Stakeholder Representative Interactions
Add a New Stakeholder Group Here

Add Links to interview results here

This is a template for recording the results of a customer interview.

Read some DPM Student Suggestions About Interviewing here! This information consists of unfiltered DPM student observations and recommendations about how to better conduct stakeholder interviews. Contributors to this page included students from the DPM Class in Fall 2009-1. Contributors were: Eric Albanese, Michelle Bard, Dean Culver, Kristin Gagliardi, Eric Hettler, Shawn Hoskins, Andrew Krall, Derek Meinke, Ryan Miller, David Monahan, Christian Moreno, Manuel Paris, James Reepmeyer, Stephen Rois, Alexander Ship, Timothy Salter, and Christopher Wakely. Student names have been removed from their individual submissions for privacy reasons related to grading, but the roleplaying interview findings are presented in the words of the students.

Methods for gathering data from stakeholders 'Know-Why'

Replace these instructions with a summative paragraph about the methods and motivations your team employed to gather information from stakeholders.

DPM focuses on a combination of engineering product development tools and managerial skills development.One early activity in the DPM course requires teams of students (usually 4 to 6 students in a team) to identify stakeholders to the proposed project family. DPM students gather the Voice of the Customer using a variety of methods including those which engage the customer in their actual usage environment, as well as stakeholder interviews, as illustrated here:

 Stakeholder Data Gathering

Stakeholder Data Gathering

This Figure illustrates various methods for Hearing the Voice of The Customer. (following Burchill, G., Concept Engineering: an Investigation of Time vs. Market Orientation in Product Concept development. Massachusetts Institute of Technology Ph.D. Thesis, 1993.)

In a complete market assessment, you should not rely exclusively on stakeholder interviews. There is a lot of value to be gained from visiting client sites, watching products being used, and learning about past failures. Reflect on the best ways to gain a thorough understanding of your stakeholder needs. Do not feel restricted to simply conducting interviews when you are conducting your needs assessment.

After gathering large amounts of raw data from stakeholders about product needs and desires, the DPM students begin to interpret the data, and seek out common themes, using a tool known as affinity diagramming. Affinity diagrams permit DPM students to identify common themes that were recurring issues across stakeholders, and to identify unique perspectives that may be brought to light through contextual observation of product users.


Mission Statement | Stakeholders | Benchmarks | Affinity Diagrams |Objective Tree | Constraints | Voice of the Customer

Home | Team Values and Norms | Photo Gallery