User Driven Development for NFAIS

Slide 1: User-Driven Development Presented By: Jonathan Clark Date: February 27th 2006

Slide 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 2

Slide 3: User-Centred Design Process Understand the user, their tasks and their goals Design for the user, make sure they can efficiently and easily complete their tasks Evaluate the UI, not the user 3

Slide 4: Example: Electronic Information Retrieval Morning Lunch Afternoon After Hours Librarian Researcher Student Practitioner Significant generalizations; Use of Elsevier electronic products is much smaller 4

Slide 5: Example: Differences and Similarities rs Pr he • Clinical decision • Values completeness ac rc support and fact lookup and exhaustiveness tit ea io es • Collaborative • Need for a concise ne • Links to references R and easily rs and evidence • Likes to cast a broad scannable answer search first, then • Current awareness systematically refine • Need for concise results overviews • Quick and Advanced searching • Interested in seeing • Highly mobile what has NOT been • Help user understand done content • Time pressured • Needs to secure • Spellchecking grants/funding • Has little time to sift through large answer • Needs to publish sets original research 5

Slide 6: User-Centred Design Process Understand the user, their tasks and their goals Design for the user, make sure they can efficiently and easily complete their tasks Evaluate the UI, not the user 6

Slide 7: Evolution of the Refine Results box 7

Slide 11: How to display citation tools? ? 11

Slide 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 12

Slide 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  13

Slide 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  14

Slide 15: Elsevier Agile Development Process + Prototyping Architect/Developer (IT Lead) QA Specialist Initiate + Initial Story Writing Content Workflow Manager Project Manager Release Project Planning Initial Spikes + Iteration Manager Product Manager Content Planning + UCD Analyst Iterative Development Feedback / Usability Testing Preparation Spike Release! Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5 Deployment Run Run Write Functionality Write Write Iteration Select Prioritize Functional Regression Stories Review Code Tests Showcase Story Stories Tests Tests & Tests Kick-Off Development Testing Update Usability Monitor Verify Ranking/ Design Fix/ Review Stories Testing Progress Story Estimating Session Correct Stories 15

Slide 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)  PathologyConsult Stickers show progress: 2.3 Inline Images • Red: Development has started As a pathologist, I want to be able to see images that relate to the text of a diagnosis appear in • Orange: Development the appropriate place. has completed The images of Rosai should appear in the text in the appropriate place and so must be linked to • Yellow: Testing by the data. Images should have the label and caption underneath as well as an ALT description . Developers & QA is complete Acceptance Criteria: · Hovering over or right-clicking the image should result in the label and caption being • Blue: The Product displayed. Manager has signed · 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. off that card is complete Estimate: 2pts 16

Slide 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 17

Slide 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 18

Slide 19: Differential Diagnosis: low-fi prototype Home > Differential Diagnoses First, select a body system Thyroid Select a different body system Then, select up to 5 diagnoses to compare View Amyloidosis Follicular carcinoma Differential Clear cell tumors Follicular adenoma Hürthle cell (oncocytic) tumors Papillary carcinoma Add  Hyalinizing trabecular adenoma and related lesions  Remove LYMPHOID TUMORS AND TUMORLIKE CONDITIONS Malakoplakia Medullary carcinoma MESENCHYMAL TUMORS METASTATIC TUMORS Other neuroendocrine tumors Parathyroid tumors Poorly differentiated carcinoma 19

Slide 20: Differential Diagnosis: low-fi prototype Home > Differential Diagnoses > Comparison Follicular carcinoma Follicular adenoma Papillary carcinoma Remove from comparison Remove from comparison Remove from comparison Image caption Image caption Image caption (stain, magnification) (stain, magnification) (stain, magnification) • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl • Diagnostic Pearl 25 additional images available 15 additional images available 18 additional images available View complete diagnostic View complete diagnostic View complete diagnostic information for Follicular information for Follicular information for Follicular carcinoma adenoma carcinoma 20

Slide 21: Differential Diagnosis: as deployed 21

Slide 22: Differential Diagnosis: as deployed 22

Slide 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 23

Slide 24: “Process is what you focus on when you don’t have the right people with the right skills” Jared Spool 24

Slide 25: Thank you j.clark@elsevier.com

Slideshare.net (beta)