• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Long feedback loops in software development
 

Long feedback loops in software development

on

  • 219 views

A Keynote presentation I presented at the StepAuto conference in Bangalore, India.

A Keynote presentation I presented at the StepAuto conference in Bangalore, India.

Statistics

Views

Total Views
219
Views on SlideShare
218
Embed Views
1

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 1

http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

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

    Long feedback loops in software development Long feedback loops in software development Presentation Transcript

    • Rob Lambert Creative Directorhttp://www.softwaretestingclub.com
    • Rob Lambert Test Managerhttp://www.newvoicemedia.com Cloud based call centre solutions
    • Communication
    • A story aboutFEEDBACK
    • Feedback A Process
    • Are ourfeedbackloopstoo BIG?
    • An Old Way Waterfall? V-Model?A New Way Agile?
    • This is whatwe do...
    • What could bewrong withthe old way?
    • 1. We lock inassumptionsDo we reallyknoweverything atthe start?
    • 2. Our documents becomeour Oracles But ideas can come from other sources...
    • 3. The designsticksWe end up withusability & flowproblems
    • 4. Progress is based on testexecution rates Are all test cases created equal? What about new ideas as we test?
    • But they matter... don’t they?5. We don’t involve thecustomer until the end
    • 6. The customer fills thescope But wouldn’t you ask for it all .... and then some more?
    • 7. We use information toolsfor conversations
    • 8. We aren’t“one” teamIt’s themand us
    • Why don’t wechange? Could it be because we are scared?
    • 3 Good Reasons to try a new way
    • 1. It’s liberatingOur measure of success issoftware, not percentage of testsrun We are free to use our minds and explore
    • 2. Testing is centralWe do nothing without testing We become advisors, explorers and champions
    • 3. We gain a greater purposeWe see our work being used We see software being shipped. Regularly
    • To be part of aprocess like thisis empowering,motivating andfun.
    • Image ReferencesCommunication - http://www.flickr.com/photos/wfryer/4773103417/sizes/o/in/photostream/Microphone – http://www.flickr.com/photos/pmarkham/5431231488/London Eye – http://www.flickr.com/photos/dantaylor/64860668/sizes/o/in/photostream/Padlock – http://www.flickr.com/photos/gromgull/2642629481/sizes/o/in/photostream/Document – http://www.flickr.com/photos/smemon/4902517280/sizes/o/in/photostream/Sellotape – http://www.flickr.com/photos/sk8geek/5649020434/sizes/l/in/photostream/Number – http://www.flickr.com/photos/horiavarlan/4513523409/sizes/l/in/photostream/Customer –http://www.flickr.com/photos/rachaelvoorhees/435964839/Overflow Pool – http://www.flickr.com/photos/dasqfamily/2689550144/sizes/l/in/photostream/Information – http://www.flickr.com/photos/heathbrandon/3187207970/sizes/o/in/photostream/Huddle – http://www.flickr.com/photos/jeffk/92047417/sizes/l/in/photostream/