The Feedback Loop in Agile
The Feedback Loop in Agile
Do work, get feedback and learn, repeat to meet user needs and get value
About the Book
The feedback loop and feedback process is something we have come to avoid. Often to protect feelings and avoid potential conflict. However, we forget that constructive feedback is one of the most efficient ways to learn and do work. This applies to Agile software development especially but extends to all kinds of work. Good feedback loops enable effective communication and learning by all involved. Get feedback to learn and adapt, which allows for obtaining real user value.
Do you ask any of these questions?
Why should we get feedback?
How important is customer feedback?
How can we improve software quality?
Feedback loops in Agile software development are critical to the
process. However, they are often ignored and relegated to second class
processes. In favor of more traditional requirements gathering processes.
Feedback is how you build efficiently, to meet user needs. Good feedback lets
you build the right things, the first time around, with quality built in.
Software feedback enables getting value and helps to build in quality.
Feedback enables you to get the information that you often can't via other means. Giving and receiving feedback can be a touchy subject, because we tend to avoid the more difficult conversations. But it doesn’t have to be. As feedback can be used as a learning tool. It has the ability to speed up your delivery of work. Feedback helps you to work in better quality from the beginning. Feedback embraces the unknowns that are inherent to today's building of software. By embracing them and learning from them, you fix them and move forward faster. Learn about impediments to this learning process, so that you know how to get feedback. Good learn and adapt processes will enable your team to move fast, so use them to improve software with feedback.
The benefits are endless when you get and use feedback in quick,
efficient ways. So don’t avoid feedback, embrace it. Feedback could be the
single greatest factor for your team’s improvement. Let’s bring back an
attitude of relying on and using feedback. It will help us all to do better
work. Read more about feedback loops today, and build up your Agile software
delivery processes!
About the Author
Table of Contents
-
Chapter One - Introduction and intent
- Intro
- Why I am qualified for this
- Intent
- Always aiming to provide good info and earning your business
- Chapter Two - What is the feedback loop
-
Chapter Three - Why feedback is so important to the team
- Why feedback loops in Agile?
- Feedback is a learning process
- Feedback facilitates faster results
- Feedback is the best way to know if you meet user needs
- Feedback supports so many of the Agile best practices and values
-
Chapter Four - Agile and software development processes that need feedback
- Shorter iterations
- Improved quality
- Iterative and incremental progress forward
- Build, learn, repeat
- Real evidence and information from users
- Just in Time Requirements
- Testing assumptions requires feedback
- Get info, determine solutions, get feedback, repeat
- The scientific process uses feedback by testing a created hypothesis
- Feedback loops in Agile – Include in your processes
-
Chapter Five - The fundamentals of good feedback
- Open and honest communication
- Direct communication
- Real evaluation of needs
- Be ready to learn and go again
-
Chapter Six - Reasons we moved away from feedback loops
- Why we strayed from getting feedback
- Requirements sought as a way to replace feedback
- We try to figure it out prior
- Expectations influence completion
- Embrace the criticism, but use it only to move forward
-
Chapter Six - Requirements took over instead of good feedback
- Requirements Are Too Stringent Of A Guideline
- Feedback loops in Agile win over requirements in any example
- Requirements are often incomplete
- When Are You Done
- Final Thoughts On Whats Better Than Requirements
- Chapter Seven - How to bring it back to the team
-
Chapter Nine - Feedback processes
- Demo
- User surveys
- Monitoring
- Data and analytics
- User acceptance tests and test environments for users
-
Chapter Ten - Benefits of feedback loop processes
- Why feedback loops in Agile are important
-
Chapter Eleven
- Contact
- Find more @ Agile Rant
- Please sign up for the Agile Rant newsletter
- Upcoming content
The Leanpub 60 Day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.
You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!
So, there's no reason not to click the Add to Cart button, is there?
See full terms...
80% Royalties. Earn $16 on a $20 book.
We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $13 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them
