Going in for agile make sure the game is worth...
- START with the most basic idea of a product, just to prove the concept. The so-called minimum viable product will show whether the game is worth the candle. Besides, it will require much less time, effort and money than full-scale product deployment. There are no new shining features until the concept is validated.
- WRITE the code and DEPLOY it to the production soon after that. Every new product release brings updates and keeps users on tenterhooks. It is easier to track the product popularity and watch for the consumer attitude to the product. Highly-appreciated features are then promoted and upgraded while others are either rebuilt or replaced.
- PROVIDE several versions of the product to see what consumers like most. Users like to have a choice, while you can try out several potential directions of product development.
- VERIFY and ANALYZE the users’ feedback. Apply reliable tools to collect usage data and analyze it to take further decisions. The more reliable the metrics is, the more unbiased consumer feedback you get.
- LEARN what consumers like and dislike about the product, what they need and what they’d like to have. Everybody would agree that it is vital for a business to learn about its customers’ needs. During the traditional development process information about consumers arrives only twice. Some data is provided at the very beginning in the form of initial development requirements. They are very biased and represent what business owners just think to be necessary for the public. Most data arrives after the release and it is usually too late to be used. A continuous deployment process allows receiving more info about the consumer attitude to the project. The results of the data analysis can significantly alter the product development direction.