? QA Design Gurus: Releasing a product?

Mar 30, 2016

Releasing a product?

Today is the day to release the product, the team worked hard spending countless hours engineering the new features. But are the things ready?

Do we know the product that is being released is ready to be shipped? Who calls out that we are ready? And what all we did prior to release?

Improving the product and means improving the quality of product and also improving the release process of the product.

Having a improved release process will produce best quality of engineering and thus reduces the headaches for customers. In current world, the releases are fast, which is great however, releasing fast does not mean releasing with quality. Important areas of product could be missed.

Team members with various roles and skill set have various perceptions about the features and usage of features in the product. The product might be tested thoroughly, however, considering the views of various members in the team before release is important. To make the point simple, there are lot more things to consider before releasing the product than just developing, testing and releasing.

Few things to keep in mind as you are coming closer to a release.
  • Have we communicated everything? Any ambiguity? Did we follow best practices and processes? 
  • Testing criteria should be detailed, specified and communicated that what and how we tested and what and why we did not test. 
  • Are the views and perceptions related usability and user experience has been taken into consideration?
  • Any external factors such as events, holidays been considered?
  • Has the Technical support team prepared and had experienced the new features.
Customers and Engineering both should be happy to make a successful release.

No comments:

Post a Comment