...
- Create a coherent set of web pages in the Fluid wiki containing guidelines and protocols to guide the efforts of evaluators.
- Highlevel protocol and guidelines
- Checklists, principles, and protocols (step by step procedures) for conducting walkthroughs
- Reporting templates
- Create and document some basic resources for reviewers
- Procedures for selecting target product instances
- List of pre-selected product instances for review
- List of personas
- List of scenarios
- Create standard mechanisms for processing the results of walkthroughs
- Distilling observations
- Identifying pain points (user problematics)
- Assessing frequency and severity
- Identifying solutions
- Proposing components
- Ranking and prioritizing
- Create mechanisms for producing other artifacts from walkthrough results, and publishing
- Design patterns
- Guidelines and approaches for developers
- Pitfalls to avoid for developers
- Other rules of thumb for developers
- Messages to communities
- Messages to stakeholders (e.g. funding bodies)
- Integrate all of the above as part of the UX ToolkitDesign Handbook
- Assess coverage achieved to date over 3 products and 3 methods, for both accessibility and usability
- Create a mechanism for triggering walkthroughs when they are required by the Fluid project (Wave Planning)
- Observed need for coverage such as new or changed product functionality
- Release cycle - e.g. every couple of milestones
- Other triggers
- before general release of componentry
- project deliverables: e.g. report to funding bodies
- prioritization: e.g. pain point impact
- Create a process to initiate, coordinate, and conduct walkthroughs as required
- List coverage required (from Wave Planning)
- Assemble the reviewer teams
- Select protocols and resources
- Conduct the walk-throughs
...