Running Day 5 of the Usability Sprint

Loading...

From the course by University of Virginia

Running Product Design Sprints

374 ratings

University of Virginia

Running Product Design Sprints

374 ratings

Course 2 of 5 in the Specialization Agile Development

Typically, clients and managers don't want to pay for design (or strategy) -- they want ‘results’! Too often, this leads to solutions that just don’t make sense and aren’t valuable to anyone. Design sprints allow you to meet client's desire for quick, specific outcomes while making time to do things right. In this course, you’ll learn how to plan and run situation-appropriate sprints to avoid waste and deliver value sooner. We'll show you how to: - Plan, sell, and conduct design sprints that deliver valuable, actionable insights - Go out and learn who your customer really is and what’s important to them - Test your value propositions before you invest in building solutions - Test your user interface design to make sure it’s really usable - Focus and drive to actionable conclusions on questions of approach and architecture As a Project Management Institute (PMI®) Registered Education Provider, the University of Virginia Darden School of Business has been approved by PMI to issue 25 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. Prerequisites: Getting Started: Agile Meets Design Thinking or familiarity with agile and design thinking methodologies.

From the lesson

Testing Usability in Design Sprints

The paradox of good usability is that while it's simple for the user, getting to that level of simplicity is somewhat complex. In this module, you'll learn how to focus your usability objectives, identify interface patterns, and test alternative interface patterns- all without having to develop software. Naturally, we'll encapsulate this in a nice, tidy 1-week design sprint.

Running Day 1 of the Usability Sprint5:51

Running Days 2 and 3 of the Usability Sprint2:30

Running Day 4 of the Usability Sprint2:26

Running Day 5 of the Usability Sprint2:26

Meet the Instructors

Alex Cowan
Faculty & Batten Fellow
Darden School of Business

All right, day five.

So you've got your test plan results and now you need to figure

out what you learned, what it means, and what you're going to do next.

And so you'll spend the morning finishing up your testing and

then I think you'll find you'll have plenty of time in the afternoon to

make those final set of conclusions and drive to your next steps.

So morning time,

you're running your test plan, we're really just looking at this part here.

I would repeat basically what you did on day four and post those top learnings,

stick a vote on them to drive discussion, and then assign peers and

review your test plan notes, okay.

You'll probably have fewer notes on these, and yes, you have the recordings,

but make sure that you're cleaning up those transcripts.

You're making notes on the insights, and it's not, okay, Alex,

review the notes you made again.

It's Stan review Alex's notes.

Alex, review Stan's notes.

That's important because the whole point of this is that you accrue this asset.

And other people are able to go in as you find other things that are and are not

important in the future and look at the results you've got and what happened.

It took you a lot of time to get this, so

you might as well make sure it's usable and readable.

You'll have some time to do updates on that, you have a break.

And then whatever revisions to your mock ups,

your software, your test plan for next time, you want to go ahead and make those.

And then you want to review and prepare next steps.

What are you going to do now?

Go build software, think about architecture, rinse and

repeat some of the other stuff.

This is a time when you, in principle, have driven through a relatively specific

view of what's going to be valuable to the user.

And you may be quite ready to build software if you know what approach

you're going to take.

So here you've learned how to take this sort of nebulous thing

of usability and put it in the right place in your process, so

you know when it's time to really focus on that.

You have a systematic way to think through it and you have a test regime that is sort

of phase appropriate, highly approachable, I think you'll find.

And something that you can do regularly with your team to make sure that you

figure out what's going to be usable and

valuable to the your end user before you go and you release software.

Explore our Catalog

Join for free and get personalized recommendations, updates and offers.

Coursera provides universal access to the world’s best education, partnering with top universities and organizations to offer courses online.

© 2018 Coursera Inc. All rights reserved.

Download on the App Store

Get it on Google Play