When does software development end for a product?


Many a times we notice development teams getting annoyed and frustrated by feedback requests to improve certain features/experiences. annoy

Is their attitude acceptable?…

 

Let’s look at it objectively.

Software product development, particularly in the consumer industry (B2C space), is highly driven by user experience. There’s no way the Product Manager and UX designers could get it right unless it gets used by folks fitting the target persona attributes. Feedback from users is very important.

As Alan Cooper, author of ‘The Inmates are Running the Asylum’, put it:

The primary purpose of a persona is so that you won’t design for yourself, or for your boss, or that loud, annoying client.

Software development does not end with the ‘last development sprint’ of the release, but it continues until the product is deemed to be acceptable by the target users. Some developers get it but most don’t.personaacceptance

Most often than not it’s only after the last development sprint that product & user-experience acceptance phases begin with Dog Food and Beta tests. Any feedback that’s provided by these users will be evaluated by product management and queued up for incremental implementation.

 

Would love to hear your thoughts on how we (i.e. product management) could make software development think about the product from an end user’s perspective and take them on-board in the journey of building innovative-yet-user-centric products.