Delivering applications or systems that keep pace with evolving customer needs requires more than the adoption of agile KPIs in development processes. It requires a customer-focused, iterative mindset. By that we mean, any features that are included should be determined by how well they measure up to a product vision, not whether or not they were part of a pre-determined project plan.
This is not to say that plans are useless. It simply means that project plans should be guided by the product vision. The vision is what lights the fire in a software team and drives them to think about solving problems and not simply getting to the next stage of development. It also puts an emphasis on listening to user feedback in order to determine what areas will be critical to future cycles.
In this article, we will take a quick look at some of the best ways to create, communicate, and execute a product vision. Along the way, we’ll touch on things like the differences between a vision and a plan, hypothesis-driven development, and why user testing and metrics are so essential to a successful product.