I'm guessing you are very much her target audience, above are a bunch of traditional ideas about development that result in huge, drawn out processes for out of

I'm guessing you are very much her target audience, above are a bunch of traditional ideas about development that result in huge, drawn out processes for out of date designs that more often than not have some big omission missed during planning. In the meantime you've got a team so ingrained in how their project should work (after years of effort, probably forgotten what they're even building, lost in a world of type masturbation and implementing whatever cool tech they read about today, and demotivated because they've delivered F.A. in the meantime), regardless of its function, that pivoting the mess post-delivery is now impossible. Yahoo isn't exactly sending men to Mars, they're cobbling together fairly simplistic web apps to serve ads and perhaps even subscriptions that at best need a bit of fancy realtime communication or maybe a very large database in the background. For these kinds of apps and open source where it is now, you can get 'prototype one' built in about 90 minutes by one guy defining a bunch of models and a 0 byte index.html. Given a team of 3, one week is more than enough time to have a couple of buttons, some rough page layout, and most importantly an increasingly sterling idea of the problems you're going to start running into and how you need to adjust. It's called iterative software development, it's great. Now just add one PM to whip the software kids in the right direction, and you have a viable chance at delivering an internal demo in 2-3 months.