user driven development for nfais

User-Driven Development

Presented By: Jonathan ClarkDate: February 27th 2006

2

Product Development should start and end with the user (UCD)

user understanding user acceptance avoid opinion wars

should deliver just what's needed (Agile) understanding of user needs by all involved prioritising to these needs avoid requirements wars

Create opportunities for common ground between IT and Business

3

Understand the user, their tasks and their goals

Evaluate the UI,not the user

Design for the user, make sure

they can efficiently and

easily complete their tasks

User-Centred Design Process

4

Librarian

Morning Lunch Afternoon After Hours

Researcher

Student

Practitioner

Significant generalizations; Use of Elsevier electronic products is much smaller

Example: Electronic Information Retrieval

5

Example: Differences and Similarities

• Values completeness and exhaustiveness

• Clinical decision support and fact lookup

• Interested in seeing what has NOT been done

• Need for a concise and easily scannable answer

• Links to references and evidence

• Current awareness

• Quick and Advanced searching

• Help user understand content

• Spellchecking

• Needs to publish original research

• Has little time to sift through large answer sets

Resea

rcher

s Practitioners

• Need for concise overviews

• Time pressured

• Highly mobile

• Collaborative

• Needs to secure grants/funding

• Likes to cast a broad search first, then systematically refine results

6

Understand the user, their tasks and their goals

Evaluate the UI,not the user

Design for the user, make sure

they can efficiently and

easily complete their tasks

User-Centred Design Process

7

Evolution of the Refine Results box

8


9


10


11

How to display citation tools?

?

12

Summary – UCD Process Involves users throughout development process Users are at the centre of the process

decisions based on user data reduces design battles & opinion wars

Iterates through “understand, design, evaluate” cycle until there is user acceptance

13

Product Development should start and end with the user (UCD)

user understanding user acceptance avoid opinion wars

should deliver just what's needed (Agile) understanding of user needs by all involved prioritising to these needs avoid requirements wars

14

Elsevier Agile Development Process Based on Agile software development and project

management methodologies rapidly emerging in the last few years: Scrum, eXtreme Programming, Crystal etc.

Key characteristics: Iterative Time-boxed Dedicated team Collaborative Customer focused Testing intensive

15

Elsevier Agile Development Process

Iterative Development

Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5 Deployment

Preparation Feedback / Usability Testing

Release!

Initiate Project

Architect/Developer (IT Lead)

Analyst

QA Specialist

Iteration Manager

Project Manager

Product Manager

Content Workflow Manager

UCD

Prototyping

Initial Story Writing

Initial Spikes

Content Planning

+

+

+

+

Release Planning

Write Stories & Tests

Review Stories

Kick-Off

Prioritize Stories

Functionality Review

Ranking/ Estimating

Design Session

Development

Select Story

Write Tests

Verify Story

Write Code

Monitor Progress

Testing

Run Functional

Tests

Run Regression

Tests

Fix/Correct

IterationShowcase

Update Stories

UsabilityTesting

Spike

16

Tell the story… Requirements are captured as “Stories” on index cards. Stories are short descriptions (1-2 sentences) of something a

user wants to do or a capability the system must have. Typical form: “As a ___, I want to __, so that I can ___”. Acceptance criteria go on the card (usually the back)

PathologyConsult2.3 Inline Images

As a pathologist, I want to be able to see images that relate to the text of a diagnosis appear in the appropriate place.

The images of Rosai should appear in the text in the appropriate place and so must be linked to the data. Images should have the label and caption underneath as well as an ALT description.

Acceptance Criteria:

· Hovering over or right-clicking the image should result in the label and caption being displayed.

· References in the text to an image should be a link that jumps the user to the image where it is displayed on the page.

Estimate:2pts

Stickers show progress:

• Red: Development has started

• Orange: Development has completed

• Yellow: Testing by Developers & QA is complete

• Blue: The Product Manager has signed off that card is complete

17

User stories come from UCD UCD is integral to our agile process A UCD Specialist builds prototypes in collaboration with

the Product Manager and users Analysts draw the stories from the prototypes UCD has a on-going role in the product development

process: Working one or more iterations ahead of development Gathering feedback and usability results to update stories for

future iterations Provides input to the Product Manager on the prioritization of

the stories

18

PathCONSULT Online diagnostic clinical decision support covering

general pathology. Designed to be used at the point of work. Image based. Core is differential diagnosis tool to compare conditions. At launch will includes 500 most useful conditions based

on feedback from Pathologists

19

Amyloidosis

Clear cell tumors

Hürthle cell (oncocytic) tumors

Hyalinizing trabecular adenoma and related lesions

LYMPHOID TUMORS AND TUMORLIKE CONDITIONS

Malakoplakia

Medullary carcinoma

MESENCHYMAL TUMORS

METASTATIC TUMORS

Other neuroendocrine tumors

Parathyroid tumors

Poorly differentiated carcinoma

Home >

Differential Diagnoses

Then, select up to 5 diagnoses to compare

Add

Remove

Follicular carcinoma

Follicular adenoma

Papillary carcinoma

First, select a body system

Thyroid Select a different body system

View Differential

Differential Diagnosis: low-fi prototype

20

Home > Differential Diagnoses >

Comparison

Image caption (stain, magnification)



• Diagnostic Pearl



25 additional images available

View complete diagnostic information for Follicular carcinoma





View complete diagnostic information for Follicular adenoma





View complete diagnostic information for Follicular carcinoma

Papillary carcinomaRemove from comparison

Follicular adenomaRemove from comparison

Follicular carcinomaRemove from comparison

Differential Diagnosis: low-fi prototype

21

Differential Diagnosis: as deployed

22

Differential Diagnosis: as deployed

23

Summary When the process revolves around the user

user understanding increased => better products teams have a common focus => better collaboration

When traditional requirements are replaced by stories / low-fi prototypes etc

whole team better understands user needs => faster When short iterations are used

better prioritisation => more focus on business value The challenge is how to manage interface with less agile

parts of the organisation

24

“Process is what you focus on when you don’t have the right people with the right skills”

Jared Spool

Thank [email protected]