Getting early feedback from the users of your software is imperative for raising the quality bar. Listening to your customers, testers, and peers can make the difference between shipping the next killer feature or a dud. Learn how Atlassian leverages JIRA to capture feedback and incorporate it into our software development process.

1. Friday, June 15, 12

2. Improving Software Quality
with Effective Feedback
Andreas Knecht
JIRA Developer, Atlassian
Friday, June 15, 12

3. Overview
Friday, June 15, 12

4. 4
Friday, June 15, 12

5. 4
Friday, June 15, 12

6. 4
Friday, June 15, 12

7. 4
Friday, June 15, 12

8. 4
Friday, June 15, 12

9. 4
Friday, June 15, 12

10. 4
Friday, June 15, 12

11. 4
Friday, June 15, 12

12. 4
Friday, June 15, 12

13. Burn
the building
down!
4
Friday, June 15, 12

14. It gets worse. You get...
&
Fanboys Haters
Friday, June 15, 12

15. You want...
The Crowd!
Friday, June 15, 12

16. Friday, June 15, 12

17. Why feedback?
Friday, June 15, 12

18. Why feedback?
Jeff Atwood
http://www.codinghorror.com
Friday, June 15, 12

19. Why feedback?
10
improvements
Jeff Atwood
http://www.codinghorror.com
Friday, June 15, 12

20. Why feedback?
Getting the details right is the difference
between something that delights and
something customers tolerate.
Jeff Atwood
http://www.codinghorror.com
Friday, June 15, 12

21. Agile requires fast Feedback
Friday, June 15, 12

22. I deal with god damn customers so the
engineers don’t have to! I have people
skills!
Tom Smykowski
Former Initech Employee
Friday, June 15, 12

23. Friday, June 15, 12

24. Friday, June 15, 12

25. Friday, June 15, 12

26. Friday, June 15, 12

27. Friday, June 15, 12

28. Friday, June 15, 12

29. Friday, June 15, 12

30. Friday, June 15, 12

31. Why is the Issue Collector better?
Friday, June 15, 12

32. Why is the Issue Collector better?
1. Visible Trigger
Friday, June 15, 12

33. Why is the Issue Collector better?
1. Visible Trigger
2. Simple Form
Friday, June 15, 12

34. Why is the Issue Collector better?
1. Visible Trigger
2. Simple Form
3. No Context Switch
Friday, June 15, 12

35. And the best thing...
Friday, June 15, 12

36. And the best thing...
Friday, June 15, 12

37. Most importantly
( )=
Friday, June 15, 12

38. Most importantly
( )=
Friday, June 15, 12

39. What about internal users?
Friday, June 15, 12

40. Friday, June 15, 12

41. Friday, June 15, 12

42. Friday, June 15, 12

43. Friday, June 15, 12

44. Friday, June 15, 12

45. Friday, June 15, 12

46. Friday, June 15, 12

47. Same principles as the Issue
Collector!
• Easy Form to create issues
• No context switching!
Friday, June 15, 12

48. Once again...
Friday, June 15, 12

49. Once again...
Friday, June 15, 12

50. What about App
Development?
Friday, June 15, 12

51. Friday, June 15, 12

52. Friday, June 15, 12

53. Friday, June 15, 12

54. Friday, June 15, 12

55. Friday, June 15, 12

56. Friday, June 15, 12

57. You’ve got issues!
Now what?!
Friday, June 15, 12

58. Don’t hide feedback from Devs!
project = FEEDBACK and created > -1d
Friday, June 15, 12

59. Don’t hide feedback from Devs!
Friday, June 15, 12

60. Don’t hide feedback from Devs!
Friday, June 15, 12

61. Working with Feedback in JIRA
Friday, June 15, 12

62. Working with Feedback in JIRA
Plan it
Friday, June 15, 12

63. Working with Feedback in JIRA
Plan it
Build it
Friday, June 15, 12

64. Working with Feedback in JIRA
Plan it
Build it
Track it
Friday, June 15, 12

65. Feedback for JIRA
• Over 1351+ issues
raised since April ’11 1500
1125
750
375
Apr Jun Aug Oct Dec Feb Apr
Friday, June 15, 12

66. I love the new view especially with the
swim-lanes and the in-screen story viewer.
Greenhopper
Customer
FEEDBACK-1201
Friday, June 15, 12

67. Amazing features. Love it!! this is perfect
for project management! And also very
simple to use...
JIRA Customer
FEEDBACK-286
Friday, June 15, 12

68. I am a former Rally user and I have to
share with you that JIRA is really difficult
to use. To expect an issue to be able to
represent either a bug or a user story is
extremely naive and doesn’t work...
JIRA Customer
FEEDBACK-820
Friday, June 15, 12

69. Better Roadmap
Friday, June 15, 12

70. 1. No Barriers
Friday, June 15, 12

71. 1. No Barriers
2. Remove the middle man
Friday, June 15, 12

72. 1. No Barriers
2. Remove the middle man
3. Contextual feedback
Friday, June 15, 12

73. Friday, June 15, 12

74. Thank you!
Friday, June 15, 12