• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Feedback - The Secret ingredient of success
 

Feedback - The Secret ingredient of success

on

  • 1,137 views

A presentation given at the

A presentation given at the

Statistics

Views

Total Views
1,137
Views on SlideShare
1,004
Embed Views
133

Actions

Likes
0
Downloads
5
Comments
0

7 Embeds 133

http://blog.sharpdomains.com.br 102
http://www.linkedin.com 13
http://www.practical-agile.com 11
http://practical-agile.com 4
http://www.slideshare.net 1
http://blog.sharpdomain.com.br 1
https://www.linkedin.com 1
More...

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

    Feedback - The Secret ingredient of success Feedback - The Secret ingredient of success Presentation Transcript

    • Question: What is the difference between a home cook and a professional chef?
    • The biggest difference between home cooks and professional chefs is that home cooks don't taste the dish often enough as they prepare it. They just follow the recipe step-by-step, without getting that feedback along the way. [Wolfgang Puck – chef – Owns 20 restaurants]
    • The Secret Ingredient Of success Feedback
    • What is Feedback ?
      • The supply of an input to some process or system as a function of its output
    • What if...
      • There was a 30 second delay between pushing the breaks, and your car responding?
      • There was a 10 minutes delay between responses in a conversation?
      • There was a 15 second delay between pushing the button and this bullet appearing? 
    • Late Feedback Is Useless!
    • The cost of changes increases exponentially the farther along you are in the development cycle [Dr. Barry Boehm]
    • How does a chef work?
    • Agile is all about Shrinking the feedback loop [Corey Haines]
    • Question: What is difference of feedback loops in agile software development process?
    • Agile Development Practices
    • Code Review Feedback Loop Developer / TL Developer Several days
    • Code Review Feedback Loop Several minutes Development pair
    • Bug Feedback Loop Release Integrator Developer Bug tracking System QA Team leader between 1 week and 1 month
    • Bug Feedback Loop Developer 3 to 10 minutes 1 to 3 days QA Unit test
    • Build status Feedback Loop SCM system Developer QA Release integrator Bug tracking System between 1 day and 2 weeks
    • Build status Feedback Loop SCM system Developer between 5min and 1 hour CI Server
    • Agile Feature Management
    • Requirement Feedback Loop Marketing System Team leader Between 3 month and 1 year Customer Developer
    • Requirement Feedback Loop Customer Product Owner between 1 to 4 weeks Developer Acceptance tests up to 3 days
    • Feature Progress Feedback Loop Team Leader Developer Project Manager Tool Plan between 1 week and 1 month
    • Feature Progress Feedback Loop Developer Max. Daily Max. Daily Task Board & Burn down Rest of the Team Plan Max. Sprint length
    • Agile Project Management
    • Regression Feedback Loop SCM system Developer QA Release integrator Bug tracking System between 1 week and 2 month
    • Regression Feedback Loop SCM system Developer between 30min and 6 hours CI Server
    • Improvement Feedback Loop Team Leader Developer Project Manager Lessons Learned QA Once per release Not enough testing
    • Improvement Feedback Loop Developer Project Manager QA Once per sprint Retrospective
    • Keep It Simple
    • Summary
    • Let’s Look At The big Picture Development Practices level Feature level Project level
    • Success is about: Feedback loops Nested Short Fast Many Having
    • Shrink The Feedback Loop
    • Improve The Feedback Loop
      • Pair Programming
      • Unit testing TDD.
      • Having the QA eng. Inside the team.
      • Running Automatic build process.
      • Working in short Iterations.
      • Documenting Acceptance tests.
      • Having daily meetings.
      • Using Burn-Down charts.
      • Running Automatic test process.
      • Doing Retrospectives.
      • KPIs at the right level.
    • Thank you Any Questions ? Elad Sofer - Agile coach www.theScrumster.com / @ eladsof / elad.sofer@gmail.com