The CBD process

The CBD process provides a mechanisms for planning a product release and then managing repercussions as the project progresses, enabling FD to incorporate change requirement in a project and also manage deliverables at any point in time, delivering the most appropriate release.

Small, collaborative teams of developers share explicit knowledge about development processes.
Object Oriented technology provides the backbone to FD’s CBD process.

CBD may be selectively applied to procedural systems with clean interfaces and strong data orientation.

The Different Phases of CBD process

The first and last phases (Conceptualize and Deliver) ensues defined methodologies,
where all procedures, inputs and outputs are well indentified. The information of how
to do these processes is specific. This process is linear, with basic iteration in the
planning phase.

The Build phase has many of the processes that are unidentified or uncontrolled. It requires external controls. Accordingly, controls, including risk management, are put on each iteration of the Build phase to avoid chaos while maximizing flexibility. The resulting
‘BUILDS’ are flexible. Explicit process knowledge followed by a trial and error
methodology is used in this phase.

The project is open until it reaches the Deliver phase. The deliverable can be
modified at any time during the Conceptualize and Build phases of the project. The
project remains open to competitive time, quality, and financial pressures,  throughout  these phases.