DPM Example: Template for DPM Roadmap Planning
/public/

Objective Tree

REPLACE THIS ENTIRE PAGE WITH INFORMATION APPROPRIATE TO YOUR PROJECT

Create one Objective Tree for your overall roadmap. This single objective tree should consolidate the needs from all of your affinity diagrams into a single comprehensive view describing WHAT your product or process needs to do FOR the stakeholders, and provide clarity as to WHY each stakeholder needs your product or process. each stakeholder group that your team feels is important to the roadmap. When you are done with Part I of DPM, you should have one single Objective Tree that consolidates all of the needs expressed by your stakeholders that you have deemed to be within scope for your roadmap. Please note that in constructing the Objective Tree, your team may choose to exclude some stakeholder needs listed in the affinity diagrams.

Use each affinity diagram to organize the raw data you have obtained from your stakeholder analyses. As you gather information from each stakeholder group, be sure to focus on WHY the stakeholder group needs your product/process just as much as you learn WHAT they would like the product/process to accomplish for them. After you construct each affinity diagram from the raw data you compile, be sure to review each diagram with your guide and with the corresponding stakeholder representatives to insure the completeness and accuracy of your data.

When you present your single Objective Tree to your class-mates, the visual representation should allow you to quickly, concisely, and completely articulate the scope of the problem you have chosen to attack with your roadmap. You may find it helpful, for example, to color-code the entries in the objective tree with the corresponding color of an affinity diagram, so that it is readily apparent where the needs arose, and when they are shared by multiple stakeholders. An example of an objective tree is shown below. The left most block of the objective tree should reflect the mission statement of your roadmap (as it may evolve over the quarter). The second level should reflect the top level needs of your stakeholder groups. The third level should (unlike this example) contain complete sentences reflecting a single discrete need of one or more stakeholder groups. A fourth level, if you show it, should link back to the underlying raw data from the individual affinity diagrams, to illustrate clearly how you have interpreted each statement of need.

LV Objective Tree.

LV Objective Tree.

Prioritizing the Voice of the Customer -- Example of An Objective Tree. This objective tree was prepared using information captured by RIT students who were studying the development of an open source, open architecture, modular land vehicle for education and research at RIT.
Mission Statement | Stakeholders | Benchmarks | Affinity Diagrams |Objective Tree | Constraints | Voice of the Customer

Home | Mission Statement | Team Values and Norms | Photo Gallery