Building Feedback Loops
 into your Architecture
Zach Nies
Replace guessing
 with feedback
Where are you
 guessing?
Feedback creates
 better decisions
Feedback loops
Built to learn
Learn through
reflection
Inspect &
Adapt
                           Direct
            Adapt
                         Experience




              ...
Team
            Retrospectives

                           What
                                    S
What has    What   ...
PDCA
Cycle
        Adjust   Plan

        Check    Do
A3 Process
Development
  Process
Iterative Feedback
Development
   Cycle
Build
feedback
Build Trends
Code quality
   feedback
Stop the line
Performance
Server and client
Server side
Client side
Exceptions
Building in feedback
Data collection
Data sources



request-id



request-id
Data analysis
Reporting feedback
  Specific
  Measurable
  Actionable
  Relevant
  Timely
Real-time feedback
Feedback replaces
    guessing
What is the biggest
guess you’re making?
Replace that guess
    with data
zach.nies@rallydev.com
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Building Feedback Loops
Upcoming SlideShare
Loading in …5
×

Building Feedback Loops

1,065 views

Published on

No I’m not talking about the feedback loops that you might hear over a bad PA system. I’m talking about building into your architecture the feedback gathering that will give you valuable insights into how your users are using your application, the perceived performance of your application, how the quality of your application is trending over time, how effective your development process is, and allow you to fix bugs before your users report problems. This knowledge will empower the team to make fact-based decisions based on data, rather than only being able to use the team’s intuition.


This presentation will cover: the theory behind why feedback is important, the ways you can progressively build feedback into your architecture, and detail some real world examples.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,065
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Building Feedback Loops

  1. 1. Building Feedback Loops into your Architecture
  2. 2. Zach Nies
  3. 3. Replace guessing with feedback
  4. 4. Where are you guessing?
  5. 5. Feedback creates better decisions
  6. 6. Feedback loops
  7. 7. Built to learn
  8. 8. Learn through reflection
  9. 9. Inspect & Adapt Direct Adapt Experience Inspect
  10. 10. Team Retrospectives What S What has What HYPOTHESE HELPED HIND has could we ERED us?! us?! draw about how we move forward?!
  11. 11. PDCA Cycle Adjust Plan Check Do
  12. 12. A3 Process
  13. 13. Development Process
  14. 14. Iterative Feedback
  15. 15. Development Cycle
  16. 16. Build feedback
  17. 17. Build Trends
  18. 18. Code quality feedback
  19. 19. Stop the line
  20. 20. Performance
  21. 21. Server and client
  22. 22. Server side
  23. 23. Client side
  24. 24. Exceptions
  25. 25. Building in feedback
  26. 26. Data collection
  27. 27. Data sources request-id request-id
  28. 28. Data analysis
  29. 29. Reporting feedback Specific Measurable Actionable Relevant Timely
  30. 30. Real-time feedback
  31. 31. Feedback replaces guessing
  32. 32. What is the biggest guess you’re making?
  33. 33. Replace that guess with data
  34. 34. zach.nies@rallydev.com

×