DOCSLIB.ORG

User-Centered Design for Agile by USPTO

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
User-Centered Design for Agile by USPTO User-Centered Design for Agile Ketki Dhanesha Computer Scientist – Usability Expert US Patent and Trademark Office June, 2018 Agenda Topic Duration Introduction to User-Centered Design Process at USPTO 5 User-Centered Design Activities 15 User-Centered Design and Requirements in Agile Process 10 3 Introduction to User-Centered Design (UCD) at USPTO The User Experience Branch The User Experience Branch, or UXB, is a human-centered design group focused on understanding the interactions between people, applications and environments. We see ourselves as end-user advocates at the USPTO, ensuring that websites and applications are usable, useful, desirable, and accessible. We strive to work towards a balance between conflicting user requirements, IT constraints, and project constraints. What We Do Our primary roles… Our other responsibilities… • Usability standards creation and compliance • Oversight of vendor deliverables …and iterate System Architecture and Roles Presentation Layer * Service Layer UX lead Business Project analyst Application Layer Manager Technical lead Service Layer Data and Backend Layer Infrastructure Layer * Primary focus for UX Scaling the UCD Process LOW HIGH Level of Effort Level of Effort Reuse patterns and usability Hybrid: Full user-centered design for test the resulting UI with UCD for new features, thoughtful, holistic design of end users reuse and tweaking for new features existing features Follow on small projects UX architecture, Flagship project within the program Follow on mid sized projects User-Centered Design Activities UCD Activity - Research Stakeholder Interviews Product owners and Purpose Methods Subject- Vision Interviews matter experts Goals Brainstorming Priorities Business process How the process can be improved in the new system Policy decisions 11 User Research End users Purpose Methods How end users approach their work Observation of work in the current system How they think and make decisions How specific tasks are done today Interviews What problems and workarounds exist today Brainstorming Ideas for improvements What makes sense and what doesn’t Participatory activities such as sketching, sorting 12 UCD Activity - Design Wireframes Wireframes are black and white drawings of screens, used to work out organization, navigation, page layout, labels, and interactions. The first set of wireframes is sketchy and explores several possible alternatives. We facilitate feedback sessions with users and stakeholders, and walkthroughs with developers, to refine, flesh out more details, and clarify the requirements. Design Ideation Low Fidelity High Fidelity Sketches Wireframes Graphic design and prototypes 15 Design Reuse & Consistency We adhere to USPTO design patterns library to ensure consistency across projects. The library also provides a go to place for new members to quickly come up to speed. Translate to savings and higher efficiency. Functionality reuse within Program We reuse design patterns that have proven successful in one business unit, with some adjustments as needed to support work processes in other business units. Example reuse opportunities (from business architecture)* Case File Management Reporting Deficiency Identification Rights Grant/Denial Dockets Routing Notifications Time Processing Performance Monitoring * Reused design patterns typically need some modifications UCD Activity - Evaluate Usability Testing About twice per quarter, we conduct hands-on tests with: n Realistic tasks n The actual system in a test environment n A trained facilitator n A script n Survey questions for the participants to complete n Observation and note-taking Provides an opportunity to identify problems and fix them. 19 What we need for Usability Testing A Clickable Users’ time - Prototype OR - 3 or more users per role unless there are - Live system in alpha or beta state just less number of users performing the tasks - One hour each per quarter We also perform testing after system goes live in production to get the final evaluation for the existing features and to get initial feedback on new features 20 Usability Testing - findings Re-locate case after interruptions Writing an office action 21 User-Centered Design and Requirements in Agile Projects Wireframes, Epics and Prototypes Planning ahead for Releases and Sprint Wireframes Epic on topic SMEs-Users-UCD PO-UCD-BA of topic A A EPIC A Description: The petitions lead and supervisor ………… assigned to them UI: Xxxxxxxxxxxxxxx AC: Xxxxxxxxxxxxxxx Xxxxxxxxxxxxxxx Epics need to be SMEs Wireframes are broken down and provide/review user facing detailed out into the Epic User Stories for documents and development approve them User Stories User stories document specific functionality and behavior of the user interface. User stories are written at the level of detail needed by technical teams to do their work. Technical teams review the user stories and estimate the level of effort to complete them as a point value. Stories are created by dividing Epics. Wireframes provide visual representations and help everyone understand the requirements better. Wireframes, business rules, procedures and acceptance criteria make up user stories. Teamwork Agile Sprints and Releases Release 1 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Release 2 Sprint 5 Sprint 6 Sprint 7 Sprint 8 Planning Ahead Epics need core UCD activities: Ideally 2-6 Sprints Ahead Development Release 2 User Stories: Ideally 1-2 Sprints Ahead The topics for the next developmentSprint 5 release must beSprint 6 Sprint 7 Sprint 8 known ahead of time in order to be prepared with user research Epics are broken down into User and wireframes for the Epics Stories in accordance with AGile story size requirements Development Release 3 Sprint 9 Sprint 10 Sprint 11 Sprint 12 Meetings and Reviews – activities by Project Members Once a week Gather information, ideas, feedback SME, UCD, BA SME interviews from SMEs Weekly user interviews Observe users’ work practices, Gather Users, UCD User Research and shadow sessions feedback from users Gather requirements and info for SME, BA, UCD Requirements Once a week Gathering process maps Emails or use some of Review draft Epics SME, UCD, BA Review Session the above two meetings Release Sprint Release planning – every Many activities to start once SCRUM MASTER, quarter; Sprint Planning – development team on boards PO, TEAM planning every 3 weeks Thank you!.
Load more

Recommended publications
  • User Psychology of Emotional User Experience JYVÄSKYLÄ STUDIES in COMPUTING 213
    JYVÄSKYLÄ STUDIES IN COMPUTING 213 Jussi P. P. Jokinen User Psychology of Emotional User Experience JYVÄSKYLÄ STUDIES IN COMPUTING 213 Jussi P. P. Jokinen User Psychology of Emotional User Experience Esitetään Jyväskylän yliopiston informaatioteknologian tiedekunnan suostumuksella julkisesti tarkastettavaksi yliopiston Agora-rakennuksen auditoriossa 2 kesäkuun 6. päivänä 2015 kello 12. Academic dissertation to be publicly discussed, by permission of the Faculty of Information Technology of the University of Jyväskylä, in building Agora, auditorium 2, on June 6, 2015 at 12 o’clock noon. UNIVERSITY OF JYVÄSKYLÄ JYVÄSKYLÄ 2015 User Psychology of Emotional User Experience JYVÄSKYLÄ STUDIES IN COMPUTING 213 Jussi P. P. Jokinen User Psychology of Emotional User Experience UNIVERSITY OF JYVÄSKYLÄ JYVÄSKYLÄ 2015 Editors Marja-Leena Rantalainen Department of Mathematical Information Technology, University of Jyväskylä Pekka Olsbo, Ville Korkiakangas Publishing Unit, University Library of Jyväskylä Cover picture: CC-BY-SA by Jussi Jokinen from following images: Coghead: CC-0 Cellphone icon: CC-BY-SA WZ Computer icon: CC-BY-SA Carlosdevivo URN:ISBN:978-951-39-6225-8 ISBN 978-951-39-6225-8 (PDF) ISBN 978-951-39-6224-1 (nid.) ISSN 1456-5390 Copyright © 2015, by University of Jyväskylä Jyväskylä University Printing House, Jyväskylä 2015 “For all men begin, as we said, by wondering that things are as they are, as they do about self-moving marionettes, or about the solstices or the incommensura- bility of the diagonal of a square with the side; for it seems wonderful to all who have not yet seen the reason, that there is a thing which cannot be meas- ured even by the smallest unit.” (Aristotle, Metaphysics, 983a15) ABSTRACT Jokinen, Jussi P.
    [Show full text]
  • Software Quality Management
    Software Quality Management 2004-2005 Marco Scotto ([email protected]) Software Quality Management Contents ¾Definitions ¾Quality of the software product ¾Special features of software ¾ Early software quality models •Boehm model • McCall model ¾ Standard ISO 9126 Software Quality Management 2 Definitions ¾ Software: intellectual product consisting of information stored on a storage device (ISO/DIS 9000: 2000) • Software may occur as concepts, transactions, procedures. One example of software is a computer program • Software is "intellectual creation comprising the programs, procedures, rules and any associated documentation pertaining to the operation of a data processing system" •A software product is the "complete set of computer programs, procedures and associated documentation and data designated for delivery to a user" [ISO 9000-3] • Software is independent of the medium on which it is recorded Software Quality Management 3 Quality of the software product ¾The product should, on the highest level… • Ensure the satisfaction of the user needs • Ensure its proper use ¾ Earlier: 1 developer, 1 user • The program should run and produce results similar to those expected ¾ Later: more developers, more users • Need to economical use of the storage devices • Understandability, portability • User-friendliness, learnability ¾ Nowadays: • Efficiency, reliability, no errors, able to restart without using data Software Quality Management 4 Special features of software (1/6) ¾ Why is software ”different”? • Does not really have “physical” existence
    [Show full text]
  • Quality-Based Software Reuse
    Quality-Based Software Reuse Julio Cesar Sampaio do Prado Leite1, Yijun Yu2, Lin Liu3, Eric S. K. Yu2, John Mylopoulos2 1Departmento de Informatica, Pontif´ıcia Universidade Catolica´ do Rio de Janeiro, RJ 22453-900, Brasil 2Department of Computer Science, University of Toronto, M5S 3E4 Canada 3School of Software, Tsinghua University, Beijing, 100084, China Abstract. Work in software reuse focuses on reusing artifacts. In this context, finding a reusable artifact is driven by a desired functionality. This paper proposes a change to this common view. We argue that it is possible and necessary to also look at reuse from a non-functional (quality) perspective. Combining ideas from reuse, from goal-oriented requirements, from aspect-oriented programming and quality management, we obtain a goal-driven process to enable the quality-based reusability. 1 Introduction Software reuse has been a lofty goal for Software Engineering (SE) research and prac- tice, as a means to reduced development costs1 and improved quality. The past decade has seen considerable progress in fulfilling this goal, both with respect to research ideas and industrial practices (e.g., [1–3]). Current reuse techniques focus on the reuse of software artifacts on the basis of de- sired functionality. However, non-functional properties (qualities) of a software system are also crucial. Systems fail because of inadequate performance, security, reliability, usability, or precision, to name a few. Quality concerns, therefore, should also be front and centre in methods for software reuse. For example, in designing for the NASA Mars Spirit spacecraft, one would not adopt a “cosine” function from an arbitrary mathemat- ical library.
    [Show full text]
  • Design Rules
    Design rules Chapter 7 adapted by Dr. Kristina Lapin, Vilnius University design rules Designing for maximum usability – the goal of interaction design • Principles of usability – general understanding • Standards and guidelines – direction for design • Design patterns – capture and reuse design knowledge types of design rules • principles – abstract design rules – low authority – high generality Guideline s • standards – specific design rules – high authority – limited application increasinggenerality Standards • guidelines generality increasing – lower authority increasing authority increasing authority – more general application Principles to support usability Learnability the ease with which new users can begin effective interaction and achieve maximal performance Flexibility the multiplicity of ways the user and system exchange information Robustness the level of support provided the user in determining successful achievement and assessment of goal- directed behaviour •Predictability •Synthezability Learnability •Familiarity •Generalizability •Consistency Principles of learnability Predictability – determining effect of future actions based on past interaction history – operation visibility Predictability http://www.webbyawards.com/ 7 Principles of learnability Synthesizability – assessing the effect of past actions – immediate vs. eventual honesty Synthesizability 1. 2. 3. 9 Principles of learnability (ctd) Familiarity – how prior knowledge applies to new system – guessability; affordance Principles of learnability (ctd) Generalizability
    [Show full text]
  • Usability Basics for Software Developers Usability Engineering
    focususability engineering Usability Basics for Software Developers Xavier Ferré and Natalia Juristo, Universidad Politécnica de Madrid Helmut Windl, Siemens AG, Germany Larry Constantine, Constantine & Lockwood n recent years, software system usability has made some interesting ad- vances, with more and more organizations starting to take usability seri- ously.1 Unfortunately, the average developer has not adopted these new I concepts, so the usability level of software products has not improved. Contrary to what some might think, us- Usability engineering defines the target us- This tutorial ability is not just the appearance of the user ability level in advance and ensures that the examines the interface (UI). Usability relates to how the software developed reaches that level. The system interacts with the user, and it includes term was coined to reflect the engineering ap- relationship five basic attributes: learnability, efficiency, proach some usability specialists take.3 It is between usability user retention over time, error rate, and sat- “a process through which usability character- and the user isfaction. Here, we present the general us- istics are specified, quantitatively and early in interface and ability process for building a system with the the development process, and measured desired level of usability. This process, which throughout the process.”4 Usability is an is- discusses how most usability practitioners apply with slight sue we can approach from multiple view- the usability variation, is structured around a design- points, which is why many different disci- process follows a evaluate-redesign cycle. Practitioners initiate plines, such as psychology, computer science, design-evaluate- the process by analyzing the targeted users and sociology, are trying to tackle it.
    [Show full text]
  • USABILITY of PROCESSES in ENGINEERING DESIGN Becerril, Lucia; Stahlmann, Jan-Timo; Beck, Jesco; Lindemann, Udo Technical University of Munich, Germany
    21ST INTERNATIONAL CONFERENCE ON ENGINEERING DESIGN, ICED17 21-25 AUGUST 2017, THE UNIVERSITY OF BRITISH COLUMBIA, VANCOUVER, CANADA USABILITY OF PROCESSES IN ENGINEERING DESIGN Becerril, Lucia; Stahlmann, Jan-Timo; Beck, Jesco; Lindemann, Udo Technical University of Munich, Germany Abstract Processes in Engineering Design are generally optimized towards efficiency, quality, costs, risks, etc., however an analysis that includes requirements from the process users' view is missing. Within the last years, the concept of usability has being introduced to examine business processes. This is a promising approach for Engineering Design, by involving process "users" (designers, engineers, software developers, project managers, etc.) in the process planning phase, several issues such as consistency flaws or counter-intuitive information flow can be identified beforehand. This paper aims to explore the transferability of usability concepts and evaluation methods to processes in the field of Engineering Design. The goal of this paper is to set a basis for further studies with regard on how to plan and design processes that interact efficiently, effectively and satisfactorily with the people involved. For this purpose ten process usability attributes are consolidated from the overlap between usability attributes (of products and systems) and process system properties. Moreover, five usability evaluation methods are examined on their applicability for evaluating design processes. Keywords: Design management, Design process, User centred design Contact: Lucia Becerril Technical University of Munich Chair of Product Development Germany [email protected] Please cite this paper as: Surnames, Initials: Title of paper. In: Proceedings of the 21st International Conference on Engineering Design (ICED17), Vol. 2: Design Processes | Design Organisation and Management, Vancouver, Canada, 21.-25.08.2017.
    [Show full text]
  • Quality Attributes and Design Tactics
    Quality Attribute Scenarios and Tactics Chapters 5-11 in Text Some material in these slides is adapted from Software Architecture in Practice, 3rd edition by Bass, Clements and Kazman. J. Scott Hawker/R. Kuehl p. 1 R I T Software Engineering Quality Attributes – Master List • Operational categories • Developmental categories – Availability – Modifiability – Interoperability – Variability – Reliability – Supportability – Usability – Testability – Performance – Maintainability – Deployability – Portability – Scalability – Localizability – Monitorability – Development distributability – Mobility – Buildability – Compatibility – Security – Safety J. Scott Hawker/R. Kuehl p. 2 R I T Software Engineering Achieving Quality Attributes – Design Tactics A system design is a collection of design decisions Some respond to quality attributes, some to achieving functionality A tactic is a design decision to achieve a QA response Tactics are a building block of architecture patterns – more primitive/granular, proven design technique Tactics to Control Stimulus Response Response J. Scott Hawker/R. Kuehl p. 3 R I T Software Engineering Categories of Design Decisions Allocation of responsibilities – system functions to modules Coordination model – module interaction Data model – operations, properties, organization Resource management – use of shared resources Architecture element mapping – logical to physical entities; i.e., threads, processes, processors Binding time decisions – variation of life cycle point of module “connection” Technology choices J. Scott Hawker/R. Kuehl p. 4 R I T Software Engineering Design Checklists Design considerations for each QA organized by design decision category For example, allocation of system responsibilities for performance: What responsibilities will involve heavy loading or time critical response? What are the processing requirements, will there be bottlenecks? How will threads of control be handled across process and processor boundaries? What are the responsibilities for managing shared resources? J.
    [Show full text]
  • Usability and User Experience: Measurement Model
    Master Thesis Software Engineering Thesis no: MSE-2011:78 Month Year Usability and user experience: measurement model Eriks Klotins School of Computing Blekinge Institute of Technology SE-371 79 Karlskrona 1 Sweden This thesis is submitted to the School of Engineering at Blekinge Institute of Technology in partial fulfillment of the requirements for the degree of Master of Science in Software Engineering. The thesis is equivalent to XXX weeks of full time studies. Contact Information: Eriks Klotins Address: 123-46 Lubanas St. LV-1021, Riga, Latvia E-mail: [email protected] University advisor: Dr. Tony Gorschek Department of Systems and Software Engineering School of Computing Internet : Blekinge Institute of www.bth.se/com Technology Phone : +46 455 38 50 00 2 SE -371 79 Karlskrona Fax : +46 455 38 50 57 Sweden Abstract Software quality is one of success factors in software development. Usability and user experience (U&UX) as a part of software quality is becoming more and more important. Although, there has been successful attempts to formalize specific parts of U&UX there is still a need for a systematic framework of U&UX evaluation. This thesis is aimed to study the state of the art in U&UX evaluation in order to develop a single framework that comprises existing knowledge on the topic. Furthermore, the U&UX evaluation framework is aimed to support product development in industry and provide a versatile guide for U&UX practitioners. The study is based on reference based systematic review. The literature review covers both scientific publications and industrial grade papers.
    [Show full text]
  • Application of User-Centered Design for a Student Case Management System
    IT 11 057 Examensarbete 15 hp August 2011 Application of User-Centered Design for a Student Case Management System Vincent Kahl Institutionen för informationsteknologi Department of Information Technology ! Abstract Application of User-Centered Design for a Student Case Management System Vincent Kahl Teknisk- naturvetenskaplig fakultet UTH-enheten The student office and student counselors of Uppsala University’s IT Department need a new application for organizing and coordinating Besöksadress: student cases. The aim of this thesis is to define a specification for a Ångströmlaboratoriet Lägerhyddsvägen 1 new system. A user-centered design (UCD) approach is taken to Hus 4, Plan 0 ensure that the new application will increase productivity, is usable, and is accepted by the people that will work with it. The employed Postadress: UCD process is a custom adaption of the ISO 9241-210 standard’s Box 536 751 21 Uppsala UCD process proposal. Following the activity cycle of the ISO standard for user-centered design, this specification will understand and Telefon: specify the context of use, specify the user and organizational 018 – 471 30 03 requirements, and produce design solutions that are evaluated against Telefax: the requirements. 018 – 471 30 00 Hemsida: http://www.teknat.uu.se/student Handledare: Lars Oestreicher Ämnesgranskare: Lars Oestreicher Examinator: Anders Jansson IT 11 057 Tryckt av: Reprocentralen ITC ! Table of Contents 1! Introduction ........................................................................................................
    [Show full text]
  • 19 Broadening the Boundaries of Communication Design
    SIGDOC ’19 Broadening the Boundaries of Communication Design The 37th ACM International Conference on the Design of Communication Portland, OR, USA October 4-6, 2019 Photo Credit: Umit Aslan Unsplash.com Contents Welcome from the Conference Chairs 3 Welcome from the Program Chairs 4 WiFi & Social Media Info 5 Registration Area Info 6 Acknowledgments 7 Policy Against Harassment at ACM Activities 9 SIGDOC Board Members 12 Best Paper Award 13 Keynote: Megan Bigelow 14 Keynote: Dr. Samantha Blackmon 15 Thursday Night Super Meetup 16 Friday Night Social Events 17 Conference Schedule 18 Workshops 22 Student Research Competition 23 Concurrent Session A 24 SIGDOC Poster Presentations 25 Concurrent Session B 26 Concurrent Session C 27 Session D 28 Session E 30 Concurrent Session F 31 Sponsors 32 CDQ Call for Papers 36 SIGDOC Career Advancement Grant 37 SIGDOC 2020 39 2 Welcome from the Conference Chairs Sarah Read, Lars Soderlund, & Julie Staggers Welcome to Portland! We hope you have an enriching and entertaining stay in the Rose City for SIGDOC 2019. We’ve chosen conference, hotel, and meeting spaces that we think reflect Portland’s unique character, and we look forward to meeting you and hearing the insights that come up during this conference. Here’s to a stimulating conference and lots of great conversations. From the Conference Chairs, Sarah Read (top right), Lars Soderlund (middle right) Julie Staggers (bottom right) 3 Welcome from the Program Chairs Dan Richards, Tim Amidon, & Ehren Helmut Pflugfelder We are pleased to share with the SIGDOC community this year’s conference program and proceedings. This year’s event is particularly notable for its international representation, with presenters either teaching or enrolled at universities in the United States, Canada, Brazil, China, and the Netherlands.
    [Show full text]
  • An Analytics Platform for Everyone: Flexibility, Scalability, Usability
    An Analytics Platform for Everyone: Flexibility, Scalability, Usability ALLIANCE Comprehensive analytics and reporting capabilities of WebFOCUS from Information Builders, running on the robust and scalable Teradata® Database redefines self- Information Builders and Teradata service analytics by helping organizations use BI more The Need strategically across the enterprise. BI and analytics are needed more than ever to help The value of BI is best measured by how widely it can organizations succeed and thrive in ever more competi- impact decision making across the enterprise and beyond. tive landscapes. This means extending access to BI and WebFOCUS on Teradata Database answers this need, analytics throughout the enterprise. delivering rich, consumable, interactive information to the widest range of employees, managers, analysts, The Solution partners, and customers. All of this can be done in real- WebFOCUS by Information Builders, running on time, while importing data from a spectrum of disparate Teradata ® Database, provides the industry-leading sources—structured and unstructured data, and present- BI and analytics platform. WebFOCUS dashboards, ing results in award-winning user-friendly dashboards and scorecards, and other features provide self-service, other rich formats. real-time solutions to maximize the benefits of BI and analytics across the organization. The Challenge of Pulling Insights The Benefits from Data • Comprehensive solution serves as a complete BI and analytics platform. Business intelligence has long been mission critical, yet many organizations, bursting with data, are frustrated by • Real-time analytics. the challenges of integrating disparate data sources to • Ease of use and award-winning UI answer the need harness the information generated by every customer, for self-serve BI and analytics.
    [Show full text]
  • Mapping the Range of User Roles in Open Development Games Projects
    Not just users: Mapping the range of user roles in open development games projects Luke Thominet Florida International University Miami, FL, USA [email protected] ABSTRACT love what you’re doing, and they’re not playing a lot, Open video game development systems provide a useful model but they might be writing fanfction, they might be for designing an engaging user experience (UX) research project. drawing, they might be doing other things, and they’re While UX research has typically framed people simultaneously as not actually just a hardcore player. [19] research subjects and users of a technology, some work has also At the 2015 Game Developers Conference, a panel of experienced problematized each of these categorizations. For instance, UX prac- developers discussed their experiences with open development titioners have questioned the framing of people as generic users, projects. In the quote above, Jamie Cheng described how partici- and participatory design has repositioned participants as co-owners pants in these projects were doing a lot more than just playing the of the results of research. This article ofers a complimentary per- game. This paper expands on this observation to review the broad spective by applying the concept of user roles to the activity of range of roles that user-participants adopt in open development participation in open development. Open development, which is the systems. prolonged process where incomplete games are publicly released Broadly speaking, open development is publicly distributing an and iterated on based on player feedback, is fundamentally a UX incomplete game, sharing information about the game develop- research process.
    [Show full text]