Uploaded bySven Peters
How effective feedback can improve your software
The document discusses the importance of effective feedback in software development, emphasizing the need for developers to actively listen to user needs and improve their products accordingly. It outlines a series of stages for gathering feedback, from prototyping to automation, and suggests methods for engaging users, including gamification. The key takeaway is to prioritize user input and reduce barriers to feedback to enhance product development.
More Related Content
Similar to How effective feedback can improve your software
How effective feedback can improve your software
- 1. Stop Talking StART LISTENING How Effective Feedback improves your software
- 2. That‘s me Sven Peters Atlassian Ambassador speters@atlassian.com @svenpet svenpet.com
- 3. Users Developers New Project Management Operation
- 4.
- 5. Budget Features Project Lead Time
- 7. They don't know but we I'm missing what they want showed it to functionality customers
- 8.
- 9. no real data Why did this happen? Test Users not representative not listening
- 10.
- 11.
- 12. ideas Learn Build Product Data Measure
- 13.
- 15. Stage Fake it 1 til you make it
- 16. p er p e s D o pa ot y Pr o t
- 17. p er p e s D o pa ot y Pr o t
- 19.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27. Faking Recipe 1 Makea Screenshot 2 Mix IT in Keynote 3 Link It & Animate it
- 29. Stage Get ready 2 for Feedback
- 30. Fast Feedback Slow Releases
- 31. Devops Little bit weird Pulls levers & turns knobs Sits closer to the boss Easily excited Thinks too hard Yells a lot in emergencies http://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr
- 32. automate Delivery
- 33. one Click Release afraid of releasing?
- 34.
- 35. Stage 3No Barriers
- 37.
- 39. You get Haters feedback Fanboys
- 40. You WANT THE CROWD
- 41. in the Face
- 43. Make it Simple
- 44. Make it Simple
- 45. In Application Feedback
- 48. 2012 400 1000 2011 Responses Responses
- 49.
- 50. Stage 4 Make it an Experience
- 51.
- 52. Simple but boring Will I do this again?
- 53. Make People wantto come back
- 54.
- 56. Make it fuN
- 57.
- 58.
- 59.
- 60. Help Stage 5 if you can
- 61. Can you pleasegive me your Telephone Number Birthdate Social Security Number ...
- 62.
- 63. A picture Saysmore than 1000 words
- 65.
- 66.
- 70. Stage Developers and 6 Feedback
- 71.
- 72. The Sh*t umbrella 425 Million user 100 developer
- 73.
- 74. Everyone on the Front line
- 76.
- 77.
- 78. WE Have DoS Developer on Support
- 79. Stage Don't Rely On Opinions 7
- 80. your code your App What are you testing? your Infrastructure your Test
- 81. Prototypes Do you testyour ideas?
- 82. Do you testyour users?
- 83. so far... Opinions f*%! bigger not work greener more faster
- 84. A B testing
- 88. A B
- 89. A B
- 90.
- 91.
- 92.
- 93. Consider removing features removed from iOS
- 94.
- 95. 1 Fake it til you make it 2 Get ready for Feedback 3 No barriers 4 Make it an experience 5 Help if you can BRing in Developers 6 7 Don't rely on opinions
- 96. The small things 10 improvements Jeff Atwood http://www.codinghorror.com
- 97. Stop Talking Start Listening
- 98.