Profitability and Cost Management - Solution Development: From Concept Design to Delivery

Hey! Yes you. How many solution development methodologies could we consider? Yeh waterfall we got that. What else? Ok RAD, Agile, what else? Nothing? oh ok Prototyping, What else? Iterative?? Is that a thing now?

The process of development of a solution usually gets left to the project manager and budget holder to decide. It is normally a tactical decision in order to ensure fulfillment of the project to time and scope. The solution architect, technical consulting lead rarely gets a look in to the decision on solution development but it is integral to the nature of the solution that will be developed.

I dare say some solution development methodologies are chosen because it is well known to the project team and not necessarily best fit for the client, requirements, or solution.

The Systems Development Life Cycle (SDLC) is the standard for describing all the methods and processes involved in solution design. It also translates to recognized management control domains.

It begins in the 60's and 70's with Cap Gemini SDM, or SDM2 an early waterfall based software development methodology.

IEEE ( Institute of Electrical and Electronics Engineers) created a standard for the SDLC methologies IEEE 12207-2008 - Systems and software engineering -- Software life cycle processes. That is high praise if ever there was surely.

Let us look at the major solution development methodologies.

Waterfall

Spiral

DevOps

Prototyping

RAD

Agile

Iterative

V-Model

Big Bang

Phased

Hybrid Methodologies

Combining elements of one of the above.

1) Waterfall and Phased: Is a popular choice, the phases being most often are determined by some overarching transformation project.

2) Prototype and Waterfall: The prototype serves as a proof of concept and pathfinder for the concept design of the main waterfall delivery.

3) Agile and Phased: The agile delivery of a current phase with a future phased planned.

4) RAD and Big Bang: The project is to be delivered in 3 RAD cycles but each RAD cycle is a big bang. Neat 

Does anyone assess the risk of employing a SDLC methodology which is incorrectly applied to the solution development process.

Does anyone quantify the risk of choosing the Project Delivery methodogy.

How do you choose SDLC methologies if you are serious about delivering to time and scope and quality?

For Profitability and Cost Management solution delivery it is imperative that some analysis of the feasibility of each SDLC method and the project approach be done to quantify and mitigate the risk of failure.