Friday, June 15, 12

JIRA Developer, AtlassianAndreas Knecht

Improving Software Quality with Effective Feedback

Friday, June 15, 12

Overview

Friday, June 15, 12

4

Friday, June 15, 12

4

Friday, June 15, 12

4

Friday, June 15, 12

4

Friday, June 15, 12

4

Friday, June 15, 12

4

Friday, June 15, 12

4

Friday, June 15, 12

4

Friday, June 15, 12

4

Friday, June 15, 12

4

Burn the building

down!

Friday, June 15, 12

It gets worse. You get...

Fanboys Haters

&

Friday, June 15, 12

You want...

The Crowd!

Friday, June 15, 12

Friday, June 15, 12

Why feedback?

Friday, June 15, 12

Why feedback?

http://www.codinghorror.comJeff Atwood

Friday, June 15, 12

Why feedback?

http://www.codinghorror.comJeff Atwood

10improvements

Friday, June 15, 12

Why feedback?

http://www.codinghorror.comJeff Atwood

Getting the details right is the difference

between something that delights and something customers tolerate.

Friday, June 15, 12

Agile requires fast Feedback

Friday, June 15, 12

I deal with god damn customers so the

engineers don’t have to! I have people skills!

Former Initech EmployeeTom Smykowski

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

Friday, June 15, 12

Why is the Issue Collector better?

Friday, June 15, 12

Why is the Issue Collector better?

1. Visible Trigger

Friday, June 15, 12

Why is the Issue Collector better?

1. Visible Trigger

2. Simple Form

Friday, June 15, 12

Why is the Issue Collector better?

1. Visible Trigger

2. Simple Form

3. No Context Switch

Friday, 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

• Easy Form to create issues• No context switching!

Same principles as the Issue Collector!

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

project = FEEDBACK and created > -1d

Don’t hide feedback from Devs!

Friday, 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 JIRA

Friday, June 15, 12

Working with Feedback in JIRA

Plan it

Friday, June 15, 12

Working with Feedback in JIRA

Plan it

Build it

Friday, June 15, 12

Working with Feedback in JIRA

Plan it

Build it

Track it

Friday, June 15, 12

• Over 1351+ issues raised since April ’11

Feedback for JIRA

375

750

1125

1500

Apr Jun Aug Oct Dec Feb Apr

Friday, June 15, 12

FEEDBACK-1201

I love the new view especially with the

swim-lanes and the in-screen story viewer.

Greenhopper Customer

Friday, June 15, 12

FEEDBACK-286

Amazing features. Love it!! this is perfect

for project management! And also very simple to use...

JIRA Customer

Friday, June 15, 12

FEEDBACK-820

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

Friday, June 15, 12

Better Roadmap

Friday, June 15, 12

1. No Barriers

Friday, June 15, 12

1. No Barriers

2. Remove the middle man

Friday, June 15, 12

1. No Barriers

2. Remove the middle man

3. Contextual feedback

Friday, June 15, 12

Friday, June 15, 12

Thank you!

Friday, June 15, 12