How Working Backwards Backfired At Us And What We Learned From It!
Working Backwards is something that is becoming quite popular and majorly used nowadays in software development. Amazon gets tagged with this for using the approach in its way and being successful with it.
According to Business Insider, Andy Jassy says, Working Backwards forces the team to get the most difficult discussions out of the way early. They need to fully understand what the product’s value proposition will be and how it will be pitched to customers. If the team can’t come up with a compelling press release, the product probably isn’t worth making.
Working Backwards: Sounds as simple as it is to understand. All it says is to start from your users/customers to understand what problem you are solving and is it worth solving instead of starting with an idea for a product and trying to fit customers into it. Just like reverse engineering with different approaches/methods like business model canvas, lean canvas, etc.
This story takes me back to 2018 when one of our product teams at mySugr was tasked to solve the problems of a specific user group, me supporting them as their Agile coach.
Welcome to my Agile Diaries, where I share my experiences and my point of view on agile product development!
