Talking with Users

Loading...

Из курса от партнера University of Virginia

Agile Development in Practice (Project-centered Course)

95 оценки

University of Virginia

Agile Development in Practice (Project-centered Course)

95 оценки

Курс 5 из 5 — Specialization Agile Development

This project-centered course provides a guided opportunity for you to practice your agile development skills. Using the venture design process that frames the four courses in this Specialization, you will apply agile processes to a project of your choice or to a provided venture concept. From persona, problem scenario, and user story development to designing user testing and product launch, you’ll practice leading an agile project. You’ll finish the course with a portfolio-building design brief that demonstrates your learning and specialized skills in agile product development. To get the most out of this course, we suggest you first complete the other four courses in the Agile Development Specialization: Agile Meets Design Thinking; Running Product Design Sprints, Managing an Agile Team, Testing with Agile. By the end of this course, you'll be able to: --Formulate foundational positioning statements --Create, refine and test actionable personas --Conduct user interviews and analyze the results --Determine a 'happy path' to quickly test user stories --Run motivation and usability testing and evaluate the results As a Project Management Institute (PMI®) Registered Education Provider, the University of Virginia Darden School of Business has been approved by PMI to issue 40 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.

Из урока

Complete Persona Discovery

Welcome to Week 3. This week, you'll continue working on persona development by interviewing at least three people. As you process the transcripts, look for key learnings and share these in the discussion forum, noting how these interviews impact your direction and point of view. If you want to accelerate your learning, interview at least three more learners and complete a "Day in the Life".

Getting People to Interview7:10

Talking with Users4:51

Skit: Interviewing Trent the Technician5:45

Overview Problem Scenario Sprint5:23

Познакомьтесь с преподавателями

Alex Cowan
Faculty & Batten Fellow
Darden School of Business

In this video, we're going to talk about interviewing subjects.

Here's a checklist of things to make sure you prepared.

The first thing is you want to make sure you've got those screened subjects,

that's what been talking about.

Then you want to have the interview guide,

we talked about how to prepare that in course one.

Now next, you want to make sure you have an intro script.

You think, probably, you'll remember to tell them all these various things, but

you probably won't.

Here you want to thank them, explain what the research is about,

explain to them that you're not there to judge them or evaluate them,

you're just trying to learn about whatever it is you're learning about.

Remember, if there is a question about confidentiality about what you're doing,

you probably don't even really need to get in that with them, in fact you shouldn't.

Remember, we talked about the yellow Walkman problem, you don't want to put

the solution in front of them, you just want to talk about the problem.

And then you want to explain how their information will be used.

You also want to make sure that you're clear with them about the compensation,

how that would work.

And if you need paperwork, like a release or something,

you want to have that obviously prepared and ready to go.

If you're not using their names or recording them or using

any this material in any public way, you may find that you don't need a release.

But that is going to depend on who your subjects are, what geography you're in,

a bunch of other things you should check about.

You want to have your notes and recording ready and

now this may involve a couple of things.

One, there is a form to take notes on in Appendix A of the Google Doc.

It says notes for field interviews, I think.

I like to have a few of those tables copied out and ready to go so

I'm not fiddling with it in front of the subject.

Personally, I like to take notes on my computer.

It's a little awkward but most of the subjects really don't mind about it.

You can also,

if you have someone else that will come with you to take notes that's great,

it allows you to be much more focused on what's going on with the interview.

You can also record as long as you have the agreement and that can work but

you may find that you have trouble finding the time to go back and

listen to that whole recording again and transcribe it.

Personally, I like to just sit there and I try to take pretty detailed notes.

I'm a not fantastic, but relatively fast typer, so that that works.

You'll find what works for

you but make sure you have whatever it is ready in advance.

If you're going to do the day in the life followup, which involves getting photos

back from them, you want to make sure you have that squared away and

squared away with regard to your paperwork.

Just as a reminder, we're focused on this part of

our product or feature hypothesis, we're trying to learn these specific things.

The reason why I'm making this distinction is we're going to look

at the value hypothesis when we go to the motivation sprint, but

if we bleed any of that material into this activity,

we're going to end up with a yellow Walkman problem, if you remember that.

The punchline of that story was, we asked people if they like our

hypothetical product, they're going to say yes.

And not only that, but they're going to start telling us,

probably, what they think that we want to hear, which isn't what we want.

What we want to do is use a nice, solid interview guide like this.

You learned how to this in course one and we want to move from very general things,

very general questions, not leading to relatively more specific questions.

That's how we get a good interview.

That's how we get responses that have a high degree of evidentiary value.

If we ask a general question and we get a specific response that's

what we've thought was our most important problem, that's very valuable to hear.

If we ask them a very specific question and

then they just say yes, then that's not very valuable to hear.

The most important thing as you're getting ready for

your sessions is to have this in order and to practice.

You probably should practice at least one, two, three of these interviews yourself so

that you can be a good coach to your team on how to do this.

In this video,

we looked at how to actually conduct these subject interview sessions.

Now If you've ever gone skiing or surfing,

or maybe played tennis, I mean all these things feel awkward and

maybe you don't like that the first few go arounds and that's natural.

But I would encourage you to try it a few times before you

make any final conclusions about how hard it is or how you don't like it.

It is a very new type of skill, but I think it'll be really valuable to

you in your career if you give it a little bit of practice and

bring home some valuable insights that you can use for your project.

Ознакомьтесь с нашим каталогом

Присоединяйтесь бесплатно и получайте персонализированные рекомендации, обновления и предложения.

Coursera делает лучшее в мире образование доступным каждому, предлагая онлайн-курсы от ведущих университетов и организаций.

© Coursera Inc., 2019 Все права защищены.

Загрузить из App Store

Загрузить в Google Play