Edit Oyster: Product review meeting

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.

Pearl

To:	proudly present the new value just created and collect feedback to inform future development
Stage:
Theme:	Select allSelect none Agile Maneuver Lean Scrum Extreme Programming Kanban Quality Metric Jumpstart Decide Change Coach Team Don’t just do something The Work Trust Product
Context:	in between the current and next {{p\|sprint}},
Wish:	Elegantly pleasing the real and current needs of your users is fulfilling, gives meaning, and makes everybody happy.
So:	Reserve time in the agenda to collect some basic feedback about the results of the last sprint.
Captive image:	Upload file
Prologue:
Wish (full):	Elegantly pleasing the real and current needs of your customers and users is fulfilling, gives meaning, and makes everybody happy and avoids surprises. Tweaking and tuning your product based on feedback and {{p\|measurable goals}} keeps everyone happy.
Background:	During the {{p\|sprint review meeting}}, the {{p\|development team}} demonstrates completed functionality to interested stakeholders, gathering feedback. Simple surveys can provide quick quantitative feedback during {{p\|sprint review meeting}}s. Not everything needs to be perfect—'''focus on core and differentiating features'''! Collecting useful feedback from real customers and users on the latest results can be as simple as taking five minutes to ask the audience to answer the following questions: :“This design is meant to {{p\|sprint goal}} or {{p\|design goal}}. We would like to collect your feedback on the results of this sprint. So, can you please rate on a scale of 1–5: :Did this design elegantly fulfill its proposed case? :Would you recommend this design to a friend? :Is this design better than current working alternatives familiar to you?” Iterate your product based upon customer and user feedback and evolve it accordingly. Involve them directly in rapid feedback loops. There is no substitute for rapid feedback from real end users, but it requires preparation. Cultivate an ongoing, self-replenishing group of users that you can call on regularly. Rotate users among products and services. Example: Google holds monthly tests in major cities, putting various products in front of paid users. Encourage long-term participation where sensible: **Example: LEGO MindStorms recruited expert builders for months to help design their next-generation product.
Therefore (full):	Reserve time in the agenda to collect some basic quantitive feedback from users, customers and key stakeholders about the core and differentiating {{p\|user stories}} of the last product development cycle. Relate your current product revision to the {{p\|vibrant personas}} you use throughout.
New:	Every now and then, a {{p\|usability test}} gives you a ton of useful feedback in a very short time.
Epilogue:

Free text

Web (optional)

http://alistapart.com/blog/post/feedback-phases-and-personas · A List Apart · Anthony Colangelo · Feedback Phases and Personas

https://medium.com/facebook-design/critique-is-an-important-part-of-an... · Medium · Tanner Christensen · Four Things Working at Facebook Has Taught Me About Design Critique

https://www.uie.com/brainsparks/2011/10/27/moving-from-critical-review... · User Interface Engineering · Jared Spool · Moving from Critical Review to Critique

http://sethgodin.typepad.com/seths_blog/2016/03/show-your-work.html · Seth’s Blog · Seth Godin · Show your work

Add another

Source of this pearl (optional)

Source:
Author(s):	×Steve Krug
Translator:
Coder:
Original pattern name:
Original pattern number:
Page number:
Website URL:
Website title:

Add another

Summary:

This is a minor edit

Watch this page

Cancel

Edit Oyster: Product review meeting

Navigation menu

Search