The Ucd Kick-off Tool. Frederik Hoolhorst Mascha van der Voort

Transcription

1 The Ucd Kick-off Tool Frederik Hoolhorst Mascha van der Voort

2 Overview Ucd Kick-off Tool Design brief Development method selection 3 Desired results: selected 1 Stakeholder mapping 4 Development method specification Desired results: Scheduled activities; of required input per activity; allocated resources Detailed user-centred plan of approach Describing: Required basic product characteristics; main process constraints; core develop team members Desired results: prioritized ; promising combination of 2 Describing: Product vision; milestones, selected ; product activities; required input per product activity; allocated resources Result planning Desired results: Product vision; product conditions; contextual conditions; milestones The UCD kick-off Tool 2

3 Stakeholder Mapping 1 2 Design brief Required basic product characteristics; main contextual constraints; core team Mapping Stakeholder Stakeholders, power & their consequences Combine Promising combination of focus Skills Cognitive properties Use knowledge/ taking related expertise/ to project skills related Availability Resources taking Power Effectiveness Efficiency User Interests Use goals Error tolerance Ease to learn Engaging Events Physical properties Non-physical properties for product project for company for product project for company Use environments Antropometricalproperties User characteristics Budget related to project Availability Power Resources taking Equipment Stakeholder related Organisational skills Skills Interests Development skills Interests related Interests related to project Budget related to project Availability Power Resources taking Equipment Team related member Organisational skills Skills Interests Development skills Interests related Interests related to project for product project for company Complete of Prioritise prioritised interest 2 Negotiate about unfeasible or conflicting 3 Promising combination of focus 1 4 Verify on feasibility and conflicts Verified on feasibility and conflicts Make a promising selection of The UCD kick-off Tool 3

4 Stakeholder Mapping 1. Mapping Stakeholders Availability Budget related to project for product Equipment Organisational skills Skills Resources Power Stakeholder taking related project Development skills Interests Interests related Interests related to project for company The UCD kick-off Tool 4

5 Stakeholder Mapping 1. Mapping Stakeholders (Users) Availability Use knowledge/ expertise/ skills Resources taking related to project taking related for product Skills Power Physical properties Cognitive properties User characteristics User Interests Use environments Non-physical properties project Antropometricalproperties Effectiveness Efficiency Use goals Error tolerance Ease to learn Engaging Events for company The UCD kick-off Tool 5

6 Stakeholder Mapping 2. Combine Stakeholders Interests Prioritise prioritised interest 2 Negotiate about unfeasible or conflicting 3 Complete of Promising combination of focus 1 4 Verify on feasibility and conflicts Verified on feasibility and conflicts Make a promising selection of The UCD kick-off Tool 6

7 Result Planning Verify conditions and define missing information 2 Define product vision 3 Complete of Verified conditions missing information Product vision Promising combination of focus Promising combination of focus 1 4 Define conditions Define milestones Product usability conditions Milestone Contextual conditions The UCD kick-off Tool 7

8 Development Method Selection 2 Complete of (focus on resources) Product vision & milestone Pre)select 1 Identify possibilities to increase selected use More efficient set in of 3 Indicate application feasability Indication of feasability of application Overview of selected (pre)selected The UCD kick-off Tool 8

9 Development Method Specification Substep 2: Resource allocation Product vision & milestone selected Product vision & milestone selected Overview required input/ activities Determine desired equipment per product activity equipment per activity Determine desired execution time per product activity Allocated time per activity specified product Stakeholder (focus on resources) Contextual conditions Stakeholder (focus on resources) Determine desired: knowledge/ expertise; Knowledge/expertise Allocated per activity Determine desired budget per product activity Allocated budget per activity 1 Contextual conditions 2 milestone/ method combinations Define required input and product activities Overview required input/ activities Allocate resources specified The UCD kick-off Tool 9

10 Development Method Specification 2. Resource Allocation Product vision & milestone selected Determine desired equipment per product activity equipment per activity Determine desired execution time per product activity Allocated time per activity Overview required input/ activities specified product Contextual conditions Stakeholder (focus on resources) Determine desired: knowledge/ expertise; Knowledge/expertise Allocated per activity Determine desired budget per product activity Allocated budget per activity The UCD kick-off Tool 10

11 Guidelines for Defining User-Centred Plans of Approach 1 For each product process a dedicated user-centred plan of approach is formulated. 2 Each member of the product team is familiar with the full plan of approach. 3 The plan of approach explicitly addresses the expectations regarding the usability of the product to be designed and its use situations. 4 The project team is dynamically defined as members are added or withdrawn from the team during the product process based on the need for their contribution. 5 In the process of writing the plan of approach team members are aware of the contextual conditions (such as procedures, agreements, policies, rules or protocols) as well as their consequences on the product process and the product usability. 6 In the process of writing the plan of approach all to the product process (including the team members) have been identified. For each of them their as well as their possible contribution in the form of expertise/skills, decision taking, equipment, availability and budget is defined. 7 The plan of approach states not only the expected end results of the project, but also indicates all intermediate results needed to achieve these end results in terms of content and format. 8 In the process of writing the plan of approach a wide range of and tools that can be applied to realize the needed intermediate results have been investigated (i.e. beyond the range of and tools team members are most familiar with). 9 Methods and tools included in the plan of approach have been selected based on their effectiveness and efficiency to generate the required results as well as on their fit to the resources and skills available for this specific project. 10 The plan of approach not only defines the and tool to be applied, but also specifies when, how, by whom and with what means they will be applied. 11 Team members know which role(s) they have during the product process and which deliverables are expected from them during each design activity in terms of content and format and where they are used for. 12 Team members have a good of the budget, time as well as equipment that can be used per design activity. The UCD kick-off Tool 11

12 Contact Do not hesitate to contact us for more information or remarks with respect to the UCD Kick-off tool: University of Twente Faculty of Engineering Technology Laboratory for Design, Production & Management PO Box AE Enschede NL Contact persons: Frederik Hoolhorst MSc T: (053) E: Mascha van der Voort PhD T: (053) E: The UCD kick-off Tool 12