Gaining periodic customer feedback of working software is an important aspect of agile development, because it ensures that you are constructing a valuable solution for the customer. Without customer feedback, you are not really applying agile; you are just doing a form of iterative development without aligning your work with the customer’s need. While the engineering practices applied within an agile project focus on building the product right, the validation practices focus on building the right product.
The notion of thinking through and establishing a serious feedback approach for the product, which I term the Agile Customer Feedback Vision, is missing from many agile projects—and even missing within the bailiwick of agile practices. This vision is a strategy for identifying the right customers, applying personas, establishing feedback sessions throughout the project, and then motivating the customers to attend the feedback sessions.
Establish Customer Profiles
Customer profiles are important to a successful implementation of customer validation. A customer profile identifies common traits in your target customers, including demographics, buying patterns, and areas of interest. The goal is to identify and select customers who meet the profile you are looking for and who are willing to provide feedback.
Personas represent the users of the product that is being developed. There are often several personas that use a product for various reasons. An example of 3 personas that may use an on-premise application are: "Regular User", "Power User", and "Administrator". They all use the product a bit differently and features are built for their needs. The importance of identifying the personas in regards to customer feedback is that you should invite the customers that represent that persona when those features are being demonstrated. For example, when you are demonstrating a feature that focuses on administration tasks, then the best feedback comes from having someone from the customer who represents the administrator.
Motivate Customers to Attend
Start by inviting customers to just one end-of-sprint review or demo session and getting their input. Customers who have not experienced something like this before typically are impressed to see working software so early in a release lifecycle. If they like the first validation session, then invite them to the next end-of-sprint review and excite them by highlighting where you’ve incorporated their input. At this point, ask the customers if they want to participate periodically at a per-sprint cadence.
Capture Customer Feedback
Capturing customer feedback is important to ensuring we are "building the right thing". I have seen feedback languish which defeats the point of gaining the feedback. It is critical that the feedback gets incorporated into the next Sprint Review. The feedback that you gain should be linked to the User Story and should also capture the customer by way of Customer Profile that gave the feedback.
Consider Various Types of Customer Feedback Loops
While there is significant benefit to the end-of-sprint review or demo, the customer is, in most cases, only viewing the working software at that point. Let us review the potential types of customer validation sessions and their attributes in more detail.
• Sprint Review/Demo—This is a type of feedback that demonstrates the working software completed during the sprint, shown to customers in order to both highlight progress and gain the all-important customer feedback.
• Hands-on Experience—This is a type of feedback where customers will exercise the software in a hands-on manner in a simulated or pilot working environment. This could be in the form of alphas or betas.
• On-premise Installation Feedback—this is a type of validation where customers physically install the working software into their environment.
Once you have established the Agile Customer Feedback Vision, it is important to share it with the team so that everyone is aware of the vision and the importance of the validation activities.
To learn more about Personas, go to: http://cmforagile.blogspot.com/2013/12/personas-do-you-really-know-your-users.html.
To read the full article, go to: http://www.agilejournal.com/articles/columns/column-articles/6310-agile-customer-validation-vision.
Quite elaborate and informative tips to learn.ThanksReplyDelete
If the first time the customer sees your product is at the review, you have invited them in way too late. The review/demo is the closing of a loop that started at the beginning of the iteration. The customer should be there at the beginning of that loop -- to clearly articulate what The Finish Line needs to look like. The Product Owner then captures this in the form of User Acceptance Criteria, and the QA team decomposes this into tests... including the script of the actual demo. Once the iteration is constructed and launched, the delivery team writes code to the tests, and creates product to do exactly what the customer/PO articulated. When the customer comes back at the end of the iteration, the delivery team accounts for the commitment that they made at iteration planning. They do this by demonstrating to the PO/Customer that they have satisfied the success criteria as agreed.ReplyDelete
I have found that when you engage the Customer in this manner, they are quite eager to attend iteration review/demo.
Online customer reviews and feedback management software. Gain real your customer’s reviews and ratings with our SaaS-based Testimonials and Reviews Management Software. Use customer feedback software to boost your business thought our Software. Defend on your Business and Product Service gain a competitive advantage.ReplyDelete
Customer Feedback Software
Collect testimonials, reviews and feedbacks from your customers easily using simple Customer Feedback Software on your website. Set up real-time ... Customers love giving reviews if it’s simple and fast.ReplyDelete
Customer Feedback Software
In software project management, software testing, and software engineering,ReplyDelete
verification and validation (V&V) is the process of checking that a software system meets specifications and that it fulfills its intended purpose.
It may also be referred to as software quality control.
I really like examining and also following ones write-up when i locate them incredibly beneficial and also fascinating.ReplyDelete
That write-up is usually just as beneficial along with fascinating.Verification and Validation both are independent type of testing. Obviously,
If we look both of these activities as a whole, we can also call it testing.
Verification and Validation are the activities performed to improve the quality and reliability of the system and assure the product satisfies the customer needs.
Verification assures the product of each development phase meets their respective requirements.
Validation assures the final product meets the client requirements.
I also tell my team members to spend qaulity time doing analysis of the work they do. Do not spend the entire day in just doing testing.ReplyDelete
Spending everyday sometime on Analysis will help them
to move in the right direction in the work and also helps them to see in a bigger and broader perspective of the work.
Finally, just spend good amount of time in planning, reviews and analysis, the execution will be done like in no time.
your service is just amazing and your blog also.
I think my site is also a great site for this types of product.Because it is fast and trusted.
I enjoyed reading your article :) PLease continue publishing helpful topics like this. Regards, from alwaysopencommerce.com.ReplyDelete
I think this article will fully complement your article.
Agility marketing and development can boost up the delivery of initial business value and it guarantees that the value will be amplified throughout the development process. Your informative blog clearly shows how to avail Agility marketing solutions from the most trusted organization. Great work man!ReplyDelete
That's quite an amazing explanation of what people think the customer and stakeholders are. I think, most of companies have a lack of understanding how this is actually important to understand and to address the development that way. Scrum teams need to know this, they must.ReplyDelete
This comment has been removed by the author.ReplyDelete
Great Article. Thank you for sharing! Really an awesome post for everyone.ReplyDelete
good one.... Customer feedback appReplyDelete
Additional credentials required by some firms and institutions may include years of experience in investment banking, insurance, or finance, as well as a passing grade of the exams required for licensing. For more ideal details about expanding business portfolio, pop over to these guys.ReplyDelete
The next step in how to start a small business at home is choosing your niche. Your niche is the part of a larger market that you are interested in. This ensures that you choose a product or service that will attract customers and potential customers who are within your target market. If you want to know more about starting a small business, you can find its details on bizop.ReplyDelete