4 ms·
As a product manager, I have often found it beneficial to write requirements backwards. Start first with the desired result of a feature or flow and work backwa
by tpurves 8y ago
As a product manager, I have often found it beneficial to write requirements backwards. Start first with the desired result of a feature or flow and work backwards to the necessary steps, options, preconditions, actors, setup/enrollment steps etc. that would have been required required to get there.
- icebraining 8y agoTDD is essentially the same.
- breakall 8y agoPersonally I have to be careful of this....it’s easy for me to focus so much on the solution that the problem is never even clearly articulated to the developers (who may have a better solution that I came up with once they grasp the problem). I ran across an interesting essay on Medium recently on this topic, advocating a new approach to roadmaps focused on the problems: the problem roadmap. Instead of saying what new features the team will be working on in the future, map out what problems they’ll be working on.