Adopting A Whole Team Approach To Quality

Post on 28-Jan-2015

105 views 1 download

Tags:

description

A presentation give at Agile Carolinas on some things that I think are needed to build quality software. The content of the presentation is in the presenter notes.

Transcript of Adopting A Whole Team Approach To Quality

Adopting A Whole-Team Approach To Quality.

Our users deserve better than this.

What can we do?

Destination

3 parts1. See the whole.

2. Build the right things.3. Build things right.

1. See the whole.

Why are we building this?

Who are we building this for?

The real goal.

em-pa-thy

noun.the ability to understand and share the feelings of another.

2. Build the right things.

?What percentage of software is frequently used?

20%

?What percentage of software is occasionally used?

16%

?What percentage of software is never or rarely used?

64%

64% 20% 16%

Your Backlog

$1m Cost12 Months Effort100 Stories

From:

$200k Cost2.4 Months Effort20 Stories

To:

How do we build the right things?

ProductBacklog

SprintBacklog

Sprint

DailyScrum

ProductIncrement

Start With NoMake features work hard to be implemented. The secret to building half a product instead of a half-ass product is saying no.

“- 37Signals (from Getting Real)

3. Build things right.

How do we build in quality?

un:learn

re:think

mistake proofing

Start testing here…

… instead of here

We Get There Through…

Acceptance Criteria

Automated Acceptance Testing

Test-Driven Design

Automated Unit Testing

Continuous Integration

Continuous Governance

Our users deserve great (quality) software.

Sit togetherSee the wholeHave a visionFind “true north”Know (really know) your usersPractice empathyAvoid local efficienciesUse systems thinkingBuild the right thingsFocus on the 20%Hang out with usersUse Contextual InquiryLo-fi usability testingPaper prototypesLeverage your feedback loopsBuild communitiesListen to your usersStart with “no”Build in qualityMistake-proof

Have acceptance criteriaAutomated acceptance testingTest-drive designAutomate unit testingContinuous integrationContinuous governance

Ben CareyAgile Coach @ Rally Softwareben.carey@rallydev.com

www.thesherpaproject.comhttp://twitter.com/bencarey

Attributionhttp://en.wikipedia.org/wiki/File:Snellen_chart.svg - Jeff Dahlhttp://www.flickr.com/photos/wisdoc/2799750403 - WisDochttp://www.flickr.com/photos/thomashawk/229516213 - Thomas Hawkhttp://www.flickr.com/photos/bookgrl/3193199682 - bookgrlhttp://www.flickr.com/photos/solyoung/2503383819 - SolYounghttp://www.flickr.com/photos/rosefirerising/1175879764 - RoseFireRisinghttp://www.flickr.com/photos/missizss/2470738904 - ~ezshttp://www.flickr.com/photos/cesarastudillo/1275797028 - cesarstudillohttp://www.flickr.com/photos/frances1972/2247431698 - Frances1972http://www.flickr.com/photos/ex_magician/2867480911 - Ex Magicianhttp://www.flickr.com/photos/lachlanhardy/3283320402 - Lachlan Hardyhttp://www.flickr.com/photos/37872410@N00/3146253560 - toml1959http://www.flickr.com/photos/mkmabus/2988760669 - The Doctrhttp://www.flickr.com/photos/notjake13/2574325874 - JacobEnos