My Artictles

Feature Demo

What is a feature demo ?

Feature demos are scoped-in smaller demos from developers/leads. It could be as simple as ... like upload button takes files as upload. Or It could be a complete user-journey demo.

Why have frequent feature demos ?

Frequent features demos, gives us clear idea about how a product is shaping out. It also gives us ample time early-on to make small cosmetic suggestions and clearity of deliverables. & This also gives us oppurtunity to appreciate the devs and create a positive work environment.

Trade-offs

Finding the sweet-spot of when to have feature demos is key, if feature demos are kept towards the very end of the cycle, it wont do good. If kept very early the features are not very polished at this stage.

Based on my experience I have found the sweet-spot to be a day after dev-box, so while dev-box developers usually shares the developement insights like API, test data etc & QA also join-in to make sure the features are working good.

The day after is feature-demo where usually devs or leads present the feature, and typically tries to hit the user-journey flows. This meeting is typically joined by business folks also like BA, EM, PM, PO etc

Post Live Testing

No matter how much we prepare before the Product Release some time there are external factors like changes in Infra, App Store / Play Store changes, some core api-changes and other external factores.

This is where PLT ( Post Live Testing works ) obviously, we have to have user-journey and steps well defined to make it work and we have to test it fast. Here there are oppurntunities to use Automation , specially In-device automation testing helps here.

Everything cannot be tested manully with speed. So here where test devices come to play.

One real-life example is in early version of BrowserStack automation testing I observed that our test-suit was passing perfectly.

Now what happned later when we launched the app to app-store and play-store, there were some underlying changes in play-store api's and older api's were not forward compatible this we found at In-Device Testing.

Previous
Stakeholder Relations