Out of many Product Management domains I am particularly fascinated about one: figuring out the right time for launching a new major product release developed using Agile methodology.
How do we balance between secrecy and openness? What's the best way to harness the power of our customers' curiosity about upcoming product release with our desire to build the product in close collaboration with its ultimate users? We can't be secretive and open at the same time, or can we?
Agile software methodology calls for continuous collaboration with our customers, rigorous end of sprint validation and re-balancing of backlog priorities from sprint to sprint to achieve optimal alignment with the latest market needs. Yet, it's hard to resist the desire to follow the footsteps of proven winners like Apple who design and develop their products under seemingly impenetrable clout of secrecy.
So how can we as Product Managers strike the right balance between open collaborative approach toward our customers and desire to deliver that magic moment of unveiling groundbreaking, amazing, new product?
How do we balance between secrecy and openness? What's the best way to harness the power of our customers' curiosity about upcoming product release with our desire to build the product in close collaboration with its ultimate users? We can't be secretive and open at the same time, or can we?
Agile software methodology calls for continuous collaboration with our customers, rigorous end of sprint validation and re-balancing of backlog priorities from sprint to sprint to achieve optimal alignment with the latest market needs. Yet, it's hard to resist the desire to follow the footsteps of proven winners like Apple who design and develop their products under seemingly impenetrable clout of secrecy.
So how can we as Product Managers strike the right balance between open collaborative approach toward our customers and desire to deliver that magic moment of unveiling groundbreaking, amazing, new product?
