Code Library

Product demos are key to improving customer confidence and transparency. Through the sprint planning, the team commits to accomplishing a certain number of features for the sprint. When the product demos occur at the end of the sprint, the team shows the customer everything accomplished for that sprint. It provides transparency and confidence for the customer, and a sense of satisfaction for the team. Sitting with your customer to show them what you’ve done and listen to their comments about it is very valuable. It gives back to the customer in a way that was never done before. Developers are no longer allowed to go into a black hole while the customers pray that they get what they want at the end of three to six months. As shown in the case study, every two weeks the development team meets with the customer to show what the team is working on—and everyone is glad that they met.

Creating software is just that, creating software. In agile, it’s the primary measure of progress as a team. It's creating something that oftentimes people have not seen before. When the team does a “show-and-tell” for the customer, that piece is already built and there's something concrete that the team and the customer can discuss. As with our case study, often the product demos will spark inspiration for new ideas from the team or the customer. This innovation and inspiration is a fruitful result of the collaboration between the team and the customer. While this innovation and inspiration is highly encouraged, the team and the customer need to understand that the definition of “done” that they decided beforehand is still in effect. Any new ideas need to be groomed and their priority determined before working on them. A great idea one day may become lowest-priority idea another day.

Source of Information : Pro Agile .NET Development with SCRUM