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.

1. Building Feedback Loops
into your Architecture

2. Zach Nies

5. Replace guessing
with feedback

6. Where are you
guessing?

7. Feedback creates
better decisions

8. Feedback loops

9. Built to learn

10. Learn through
reflection

11. Inspect &
Adapt
Direct
Adapt
Experience
Inspect

12. Team
Retrospectives
What
S
What has What HYPOTHESE
HELPED HIND has could we
ERED
us?! us?! draw about
how we move
forward?!

13. PDCA
Cycle
Adjust Plan
Check Do

14. A3 Process

16. Development
Process

17. Iterative Feedback

18. Development
Cycle

19. Build
feedback

22. Build Trends

23. Code quality
feedback

27. Stop the line

29. Performance

30. Server and client

31. Server side

32. Client side

34. Exceptions

37. Building in feedback

38. Data collection

39. Data sources
request-id
request-id

40. Data analysis

43. Reporting feedback
Specific
Measurable
Actionable
Relevant
Timely

44. Real-time feedback

46. Feedback replaces
guessing

47. What is the biggest
guess you’re making?

49. Replace that guess
with data

51. zach.nies@rallydev.com