Improving Software Quality with Effective Feedback
Upcoming SlideShare
Loading in...5
×
 

Improving Software Quality with Effective Feedback

on

  • 1,386 views

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 ...

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.

Statistics

Views

Total Views
1,386
Views on SlideShare
1,004
Embed Views
382

Actions

Likes
0
Downloads
25
Comments
0

4 Embeds 382

http://summit.atlassian.com 309
https://summit.atlassian.com 55
http://magnolia-staging.private.atlassian.com 17
https://wacdev.internal.atlassian.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Improving Software Quality with Effective Feedback Improving Software Quality with Effective Feedback Presentation Transcript

  • Friday, June 15, 12
  • Improving Software Quality with Effective Feedback Andreas Knecht JIRA Developer, AtlassianFriday, June 15, 12
  • OverviewFriday, June 15, 12
  • 4Friday, June 15, 12
  • 4Friday, June 15, 12
  • 4Friday, June 15, 12
  • 4Friday, June 15, 12
  • 4Friday, June 15, 12
  • 4Friday, June 15, 12
  • 4Friday, June 15, 12
  • 4Friday, June 15, 12
  • 4Friday, June 15, 12
  • Burn the building down! 4Friday, June 15, 12
  • It gets worse. You get... & Fanboys HatersFriday, June 15, 12
  • You want... The Crowd!Friday, June 15, 12
  • Friday, June 15, 12
  • Why feedback?Friday, June 15, 12
  • Why feedback? Jeff Atwood http://www.codinghorror.comFriday, June 15, 12
  • Why feedback? 10 improvements Jeff Atwood http://www.codinghorror.comFriday, June 15, 12
  • Why feedback? Getting the details right is the difference between something that delights and something customers tolerate. Jeff Atwood http://www.codinghorror.comFriday, June 15, 12
  • Agile requires fast FeedbackFriday, June 15, 12
  • I deal with god damn customers so the engineers don’t have to! I have people skills! Tom Smykowski Former Initech EmployeeFriday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Why is the Issue Collector better?Friday, June 15, 12
  • Why is the Issue Collector better? 1. Visible TriggerFriday, June 15, 12
  • Why is the Issue Collector better? 1. Visible Trigger 2. Simple FormFriday, June 15, 12
  • Why is the Issue Collector better? 1. Visible Trigger 2. Simple Form 3. No Context SwitchFriday, June 15, 12
  • And the best thing...Friday, June 15, 12
  • And the best thing...Friday, June 15, 12
  • Most importantly ( )=Friday, June 15, 12
  • Most importantly ( )=Friday, June 15, 12
  • What about internal users?Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Same principles as the Issue Collector! • Easy Form to create issues • No context switching!Friday, June 15, 12
  • Once again...Friday, June 15, 12
  • Once again...Friday, June 15, 12
  • What about App Development?Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • Friday, June 15, 12
  • You’ve got issues! Now what?!Friday, June 15, 12
  • Don’t hide feedback from Devs! project = FEEDBACK and created > -1dFriday, June 15, 12
  • Don’t hide feedback from Devs!Friday, June 15, 12
  • Don’t hide feedback from Devs!Friday, June 15, 12
  • Working with Feedback in JIRAFriday, June 15, 12
  • Working with Feedback in JIRA Plan itFriday, June 15, 12
  • Working with Feedback in JIRA Plan it Build itFriday, June 15, 12
  • Working with Feedback in JIRA Plan it Build it Track itFriday, June 15, 12
  • Feedback for JIRA • Over 1351+ issues raised since April ’11 1500 1125 750 375 Apr Jun Aug Oct Dec Feb AprFriday, June 15, 12
  • I love the new view especially with the swim-lanes and the in-screen story viewer. Greenhopper Customer FEEDBACK-1201Friday, June 15, 12
  • Amazing features. Love it!! this is perfect for project management! And also very simple to use... JIRA Customer FEEDBACK-286Friday, June 15, 12
  • 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-820Friday, June 15, 12
  • Better RoadmapFriday, June 15, 12
  • 1. No BarriersFriday, June 15, 12
  • 1. No Barriers 2. Remove the middle manFriday, June 15, 12
  • 1. No Barriers 2. Remove the middle man 3. Contextual feedbackFriday, June 15, 12
  • Friday, June 15, 12
  • Thank you!Friday, June 15, 12