Skip to main content

Agile – Key to product development success

Agile product development can be traced back to the lean manufacturing principles W. Edwards Deming implemented in Japan after World War 2. [1] Deming focused on improving quality and reducing cost through continual improvement of the manufacturing system driven by feedback from internal stakeholders and customers.

Deming’s philosophy allowed Japanese car manufacturers to differentiate their products and appeal to customers around the world. In his book on Deming’s philosophy,  Rafael Aguayo shares a popular story about how American customers buying Ford vehicles in the 1960s would request and wait for models with Japanese transmissions. Both transmissions were made to the same specifications. However, Japanese transmissions built under Deming’s philosophy were of better quality which meant customers experienced fewer problems. [2]

Since then, Agile practices have been adopted across different industries including manufacturing, construction, business intelligence, and software development to name a few. Product development projects that utilize Agile methodology are more likely to be successful. According to the CHAOS Manifesto report by the Standish Group Agile projects are successful three times more often than non-Agile projects. [3] The study defines project success as being delivered on time, on budget, and with all planned features.

Customer Feedback – Core driver of the Agile Product Development

Agile’s success rate is primarily driven by its focus on prioritising and addressing customer requirements and pain points. A good example of this comes from software development. The very first principle in the Agile manifesto for software development states – ‘Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.’ [4] The same principle can be applied to agile product development across all industries.

Satisfying the customer starts with collecting their feedback on expectations, preferences, and pain points. Feedback can be collected across the product life cycle via different methods. For instance before launch, usability testing of early prototypes can can help gather insights into key missing features or poor execution of existing ones. [5]

Brands can get more actionable feedback from customers post product launch. They can gather product feedback via short surveys that collect open-ended answers and Net Promoter Score. [6] Social media, while primarily used as a customer service channel, is another possible means of collecting customer feedback.

One of the more readily available channels to collect customer feedback is online reviews. Customer reviews offer a comprehensive idea about how users perceive the product, especially from those who have used it for a long period of time. One of the biggest challenges with online reviews is to identify all the possible sources where people submit review. Review Monitoring can track customer submitted online reviews across multiple sources and aggregate them in one convenient location for further analysis.

Role of customer reviews in driving Agile product development

3 key reasons to use online reviews in an Agile product development cycle

  1. Get an unbiased perspective

Online reviews are voluntarily submitted by customers who buy and use the products. Unlike surveys where users get rewarded for feedback, reviews are based on real customer experiences. The opinions expressed in an online review are more likely to be honest. This is most easily seen in the fact that online reviews can be positive or negative. Not every customer is going to be pleased with the product. Therein lies an opportunity for the brand to innovate and drive Agile product development.

A unique advantage of using Review Monitoring is that it uses both positive and negative customer ratings to return a Net Promoter Score (NPS) – a key topline metric that is easy to track and useful to compare with NPS data a brand might have from other customer feedback touchpoints.

  1. Get the full 360 industry view

Brands should not limit themselves to collecting and analysing reviews of their own products. Online reviews on competitor products are available just as easily. Understanding why people prefer competitor products can provide valuable insights into what features need to be prioritised in the next iteration of an Agile cycle. This can enable challenger brands to close the gap with competitors and leading brands to solidify their prominence.

One of the main challenges with any competitor research is to track all competitors across a long period of time. This is where reviewmonitoring.com can help you. The tool tracks competitor reviews from across different online channels and makes it available at your fingertips. For every competitor product, you can track review volumes against sales or market share figures to see where competitor brands are making gains or losing ground. You can also analyse competitor reviews to identify what features drive their strengths and weaknesses in the customer’s view.

  1. Get actionable insights

Online reviews can provide real time actionable insights. Agile product teams can monitor reviews to identify emerging positive and negative trends. This will help them respond to customer needs before an issue turns into a PR catastrophe.

Review Monitoring conveniently provides the trending keywords for both positive and negative reviews. Once you start with the top keyword, you can drill down with the Word Tree feature to identify common phrases used with the keyword. This will lead you directly to identify any upcoming issue.

Review Monitoring’s advanced Smart Analytics can better categorize reviews and extract actionable insights. Smart Analytics uses Machine Learning and Natural Language Processing to identify the most popular and least popular features of a product mentioned across all reviews. Smart Analytics also provides useful guidance on how the product can go from 4.5 star to a 5 star product. This is immensely helpful for an Agile product team. It gives them quantifiable insight into what features to include in future iterations.

References

  1. https://en.wikipedia.org/wiki/W._Edwards_Deming
  2. https://www.amazon.com/Dr-Deming-American-Japanese-Quality/dp/0671746219
  3. https://www.quanta.co.uk/blog/2012/10/agile-projects-3-times-more-successful-non-agile-projects
  4. http://agilemanifesto.org/principles.html
  5. https://en.wikipedia.org/wiki/Usability_testing
  6. https://en.wikipedia.org/wiki/Net_Promoter