Fast results on a project is a formula for a shit project.
One thing I've learned over the years is that like growing corn. Software develops at its own speed and trying to force it is like running a hamburger grinder at 10,000 RPM. What you get out is more likely to be cooked meat, assuming that you don't wreck the machinery. A great deal of the work I've done wasn't done sitting in a cubicle at a keyboard working 80-hour days, it was done in my head while showering or in bed at 3 AM. Or while out in the garden.
The way to "Git 'er Dun!" is to cut corners. OF COURSE work that isn't done doesn't take any time to do, and work that is pushed into the production phase that could have been better debugged in the
test phase likewise is "fast development" at the expense of reliability and security.
A good team isn't all stars, nor is it all grunts. You need experienced people to manage the Big Picture and less-experienced people can make their work easier (thus better quality) by handling the stuff that doesn't need
rocket scientits. Too often though, people cheap out and dump the entire workload on too few people instead of leveraging the strengths of the many.
As for speed, if you're imagining that being first to market is sure-fire success, go looking for Apple Newtons and Palm Pilots. First only gets you so far.