Benefits of Early and Frequent Feedback in Agile development

One of the reasons why Agile is preferred over traditional development method is "Early and Frequent Customer Feedback". This is not only helps customer to get what he wants but also helps development team to understand the requirement better. There is no room for misunderstandings and delays. so no BAD CUSTOMER SERVICE!

In this post, I am going to discuss about some of the major benefits of early and frequent feedback in Agile. One way to get the early feedback is "CI" or Continuous Integration. There are many tools available in the market like Jenkins which help in running automated tests when a change is introduced in the build and give the feedback on the build performance or quality. Below are some of the advantages of early and frequent feedback:

• Early and regular feedback helps in clearing out the misunderstanding of the requirements. Unlike in traditional method, fixing the issues or requirements change is a lot less expensive. Customer get to see the product early.
• When customer sees the partial product, it is much easier to tell what to change if there is any. In this way, customer gets what he wants and ask for changes if needed. In traditional method where the product is delivered at the end where it is too costly to make changes and sometimes that can effect the deadlines badly. 
• CI helps in getting the feedback regularly and early which gives enough time to resolve the quality problems. It saves a lot of time and rework. 
• Early feedback also helps the agile team in planning their tasks and estimating the deadlines. 
• As mentioned earlier, Early feedback will result into happy and satisfied customers. Perfect products and timely delivery. 

One of the agile principle is "Our highest priority is to satisfy customer through continuous delivery of valuable product", and this principle is easily followed when our team adapts early and frequent feedback theory.