When developing a new technical initiative, the tech team will suggest a development methodology for the platform delivery. Understanding the two popular delivery methodologies at a high level are very important for the a CEO because this knowledge will contribute immensely for the success of the platform and the company. CEO will be able to understand the time and cost needed not only for the tech team but also for other business units needed for the continues delivery of a quality platform. The two well know methodologies are Waterfall and Agile. Agile software development relies on self-organizing, cross-functional teams discovering and building a solution using an iterative process to discover and build the solution, as opposed to the traditional Waterfall method that defines and plans the entire project before any development work begins.

Key factors to be considered in selecting a delivery approach.

1. Few initial Product and Regulatory Requirements ( Use Agile)   
2. Strict Process in Place (Use Waterfall)
3. High Product Owner involvement (Use Agile)  
4. Greenfield product (Use Agile)
5. Fixed & Firm Timeline (Use Waterfall)
6. Fixed, Inflexible Budget (Use Waterfall)

The Waterfall methodology prevails when the initiative is constrained by cost and/or time, and the requirements and scope are well understood. In these cases, the Waterfall methodology provides a set of processes that are built on the principle of approval of the previous phase.

Agile wins the day when the product team is unsure at the onset what needs to be built or they wish to discover what should be built based on adjustments they make along the way. Agile will produce more features in a shorter period of time and also gives the team more flexibility throughout the process so that they can take advantage of opportunities as the project unfolds.