Chevron Left
Zurück zu Running Product Design Sprints

Kursteilnehmer-Bewertung und -Feedback für Running Product Design Sprints von University of Virginia

4.6
551 Bewertungen
106 Bewertungen

Über den Kurs

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, we'll show you how to plan and run situation-appropriate sprints to avoid waste and deliver value sooner. You'll explore how to do this across customer discovery, testing with Learn Startup, usability testing, and product 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....

Top-Bewertungen

KS

Feb 27, 2019

Very interesting class that has very practical guidance. Alex makes the information he provides very consumable. Given that he has used the skills he teaches in the real world, I learned a great deal.

SW

May 20, 2018

Great course for the agile enthusiast that is passionate about bringing agile and lean methodologies into their start up to large corporation. Highly recommend! Thanks for Believing - Shane Wooten

Filtern nach:

101 - 102 von 102 Bewertungen für Running Product Design Sprints

von Abdalrahman S

Apr 13, 2016

I posted questions and couldn't find any answer. The course also doesn't allow me to be creative (although it's about design!) in answering assignments.

von celina o

Apr 06, 2016

I only did week one of the course and quit for the following reasons:

Presentation of the content is too fast and provides little information among lots of noise. Most of what's said is generic keywords assembled in sentences that don't make much sense, or implies "common sense" evidences barely illustrated with vague figures and no sources to support them. It makes everything hard to follow for beginners and unconvincing for more advanced students.

On top of that, I feel offended by the mysogynist examples and the underlying contradictory assumptions that designers outside of agile are basically incompetent while saying at the same time that they will just use methods they already know anyway.