Round 1 Technical: Requirements vs. Status Dashboard


Scenario #1: You painstakingly work to create and prioritize requirements that accurately reflect your users and their problems. You lovingly hand them over to be built and then crickets. No update on what’s being built; no checkpoints along the way. If you’re lucky, one day you get an email announcing a finished product ready for you to launch. Scenario #2: Every week you have visibility into the status of the latest release – progress towards milestones, burn down charts, risks and dates. What’s being built may have been defined by other internal forces or client-specific requests, but you know what’s coming and when, and can try and weave that in to a release story or feature set. Both scenarios are far from ideal, but which are you more likely to make a successful product in?

(0) Comments

Looking for the latest in product and data science? Get our articles, webinars and podcasts.