Explore
For Enterprise
Join for Free
Log In

Parcourir
Rechercher
For Enterprise
Connexion
Inscrivez-vous gratuitement

Recap on Designing for Usability

Loading...

Hypothesis-Driven Development

Université de Virginie

4.6 (372 évaluations) | 20K étudiants inscrits

Cours 4 de 5 dans Développement agile Spécialisation

To deliver agile outcomes, you have to do more than implement an agile process- you have to create focus around what matters to your user and rigorously test how well what you’re doing is delivering on that focus. Driving to testable ideas (hypotheses) and maximizing the results of your experimentation is at the heart of a high-functioning practice of agile. This course shows you how to facilitate alignment and create a culture of experimentation across your product pipeline. You’ll understand how to answer these four big questions: 1. How do we drive our agility with analytics? 2. How do we create compelling propositions for our user?  3. How do we achieve excellent usability?  4. How do we release fast without creating disasters?  As a Project Management Institute (PMI®) Registered Education Provider, the University of Virginia Darden School of Business has been approved by PMI to issue 20 professional development units (PDUs) for this course, which focuses on core competencies recognized by PMI. (Provider #2122) This course is supported by the Batten Institute at UVA’s Darden School of Business. The Batten Institute’s mission is to improve the world through entrepreneurship and innovation: www.batteninstitute.org.

Visualiser le programme de cours

Compétences que vous apprendrez

Usability Testing, Continuous Delivery, Lean Startup, Agile Testing

Avis

4.6 (372 évaluations)

5 stars
264 ratings
4 stars
72 ratings
3 stars
24 ratings
2 stars
10 ratings
1 star
2 ratings

RD

Mar 18, 2018

The course contains complete detailed information on Agile Testing. Users should make the best use of this course knowledge as now all the companies are now moving to Agile.

CK

Sep 25, 2018

This course actually bring all that knowledge into light which has been taught in Course 1-3. all videos specially the interview are the essence of this course.

À partir de la leçon

How do we achieve excellent usability? 

The best products are tested for usability early and often, avoiding the destructive stress and uncertainty of a ‘big unveil’. In this module, you’ll learn how to diagnose, design and execute phase-appropriate user testing. The tools you’ll learn to use here (a test plan template, prototyping tool, and test session infrastructure) are accessible/teachable to anyone on your team. And that’s a very good thing- often products are released with poor usability because there ‘wasn’t enough time’ to test it. With these techniques, you’ll be able to test early and often, reinforcing your culture of experimentation.

Test-Driven Product Design8:35

Recap on Designing for Usability4:45

Creating a Good Test Suite9:31

Creating Good Test Items4:47

Testing Your User Stories Part 12:56

Testing Your User Stories Part 23:36

Running Usability Tests3:09

Demo: Running a Usability Test5:33

Demo: Creating Interactive Prototypes in Balsamiq1:27

Laura Klein on Qualitative vs. Quantitative Research4:24

Enseigné par

Alex Cowan
Faculty & Batten Fellow

Transcription

Before we go in to more detail on testing usability, why don't we recap a few of the key things that you learned in course two. So first of all, this idea of simplicity is important, yet a lot more complicated if you're actually having the job of creating simplicity. So to achieve simplicity, we need to get focused, to get focused, we need to have confidence that we understand what's really important to the user, and to have that confidence, we need the understanding that only comes with the kind of validated learning that you now know how to achieve through the tools that you've learned in the course. We learned about a systematic view of user cognition and usability through Donald Norman's 7 Steps framework. So user's move from a goal to this feed forward loop of figuring out how they're going to accomplish that goal with your tool, and then you have a feedback loop where they assess what you're telling them against what they wanted. And we need to both think through this before the fact and then test against this idea after the fact to see if we're achieving good usability for the user. We learned a vocabulary of how to talk about the specifics of our executions around usability. So we learned about signifiers, affordances, constraints, the process of feedback, and how to keep an eye out for identifying and pairing mappings that users have about how things work, especially in the software world with the tasks that we're going to put in front of them. And how to pair those two things, so that we don't create novel affordances or novel signifiers that are confusing to the user. Instead we stick to well established behavioral patterns and mappings. And we learn that the way that we get to those good mappings and those appropriate signifiers and affordances is that we make sure that we come into this process with nice strong narrative about what the user really wants to achieve, and not crappy narrative like the red button story where we kind of just say, well, the user wants this because they want it. We learned how to grind through that and move from personas, to problem scenarios, to user stories, making sure that we're anchoring our execution in a strong, testable proposition, so that our primary input into the design process is vivid, validated, testable narrative. And we learned how to use that process in reverse, so that if we have a feature that's not usable or seems to be irrelevant to users, we know that we can look back through, how did we implement the narrative, to, what did we think was the problem we were solving? Why did we think it was compelling? And who was this person, again? And if you're doing this a lot, totally fine. It's completely normal. It's normal to spend a lot of time assessing usability after the fact. Nobody gets it perfect 100% of the time. Succesful teams recognize that fact and they are constantly looking back at what they did and how the users are reacting to it. We talked about the significance of this third clause on the user story and why it's so important. It's so important because this is where on a story by story basis, so on an interaction by interaction basis, we're creating strong testable views of what we think we want to achieve for the user. And we've talked a lot about this in the last module. But we learned that when we're testing, we want to make sure that we're focused on testing this, and that we control for motivation by establishing motivation and creating a set of tasks for the user, not by doing both at the same time. So for example, if our software paints walls online, then we don't want to ask the user, hey, would you like to paint a wall? What color do you want this wall to be. We just tell them, hey, could you show me how you'd paint this wall yellow? And we're going to talk a lot about how to do that over the balance of this course. We talked about phase appropriate usability testing and the importance of getting at this early. And we talked about this test plan template that is really accessible. Anybody can use it with a small amount of practice. So over the balance of the module here, we're going to use that test plan template as a focal point. And we're going to go through the elements of it. And you're going to learn how to actually go through, create, run, and then act on the results of usability testing over the balance of this module here. So we've recapped a few of the key ideas about usability here. If any of those are fuzzy for you, you can go back to the lesson resources or back to the module on usability sprints in course two.

Explorer notre catalogue

Rejoignez-nous gratuitement et obtenez des recommendations, des mises à jour et des offres personnalisées.

Coursera

À propos
Direction
Carrières
Catalogue
Certificats
Certificats MasterTrack™
Diplômes
For Enterprise
For Government
Pour le campus

Communauté

Étudiants
Partenaires
Développeurs
Testeurs bêta
Traducteurs
Blog
Blog Tech

Plus

Conditions
Confidentialité
Aide
Accessibilité
Presse
Contact
Répertoire
Filiales

Apprendre partout

Suivez-nous

© 2019 Coursera Inc. Tous droits réservés.