Once an idea has been determined(for a short iteration project), what is the best way for the CEO(non technical)/Product Manager/Marketing/Dev/UX team work together to come up the project spec and start working on it, without having meetings after meetings?

Kudos. Getting to agreement on an idea is often the hardest part. You might benefit from a purpose-built software planning  tool like http://www.aha.io If you have not discovered Aha! yet, here's the background story. After  our last two companies were acquired by Aruba Networks and  Citrix        respectively, we wanted to help product and engineering  managers in software companies get their mojo back. We were tired  of using spreadsheets and wikis and trying to apply generic   project  management tools that were not designed for product management and   planning.  We also saw too many product folks beaten down by  soft  strategies, weak    communications, and lousy tools. So, we built  Aha! and seem to have touched a nerve and are already serving some of  the best know technology and Web companies around. We also just announced a new http://blog.aha.io/index.php/startups-wanted-new-aha-startup-pack/ for other software startups, so it's affordable for all companies to  create brilliant roadmaps and better manage features and requirements. Check out a few screenshots of what Aha! can do for agile teams. Screenshot of planning board Screenshot of feature planning Screenshot of sprint planning Screenshot of strategic planning

I was involved in developing (which failed)  a comprehensive platform for managing the career development services in my B school. We had five stakeholders - students, student body in charge of the services, career development office, designer (one of the students) and an outsourced developer. Collaboration tools are a boon in such geographically spread and time-constrained projects where you have limited time and resources to meet regularly. We used collaboration software (Google Docs) to maintain the requirement specs and continuously updated the status every time there was a need for one. The developer would give status updates soon after a feature was developed, the designer ensured all design aspects were covered in the spec, the student body ensured design specs were correct by regularly reviewing the specs. In brief, collaboration tools, when used properly, can greatly enhance productivity and reduce your time-to-market.

No matter what you'll need to have weekly meetings to supervise the development  especially in a statup environment. Creating user senarios, helps a lot to graps the concept and prioritize the development. you need to trust your tech. team and some may not work out but you won't know that right away. Until you have at least an Alpha you won't be able to really feel or see the opportunities for further development. No matter what get an alpha made and work from it. If you need tech help we have a bunch of people willing to work for equity on http://ekwity.com (Disclaimer: I'm the founder.)