The Hybrid SDLC

22 Feb

A Hybrid system development life cycle is a combination of both agile and waterfall.

So why would a company use a hybrid SDLC? Why would they combine agile and waterfall?

It’s simple really. Some companies, although not many, decide to use hybrid SDLCs so that they can benefit from both the advantages of agile and waterfall! Listed below are some of the advantages of Agile, and also some advantages of the Waterfall method:

Agile advantages:

  •  Revenue: The nature of the agile method is that features are delivered incrementally which means that some benefits can be seen very early on in the development.
  • Speed-to-market: About 80% of market leaders were first to the market. Agile development includes constantly bringing new releases to the market, thus making the company more profitable.
  • Risk Management: By undertaking developments in incremental steps the owner of the system/development can quickly spot errors or flaws and they can be fixed early to avoid costly future mistakes.

Waterfall advantages:

  • Simplicity: Simple to implement and minimal resources required.
  • High Visibility: Output is generated after each step and so the managers and IS professionals can clearly witness progress.

Below is a diagram showing a hybrid SDLC.






6 Responses to “The Hybrid SDLC”

  1. sad111322576 February 22, 2013 at 9:16 pm #

    Really interesting blog! Never know that a hybrid exisited between agile and waterfall!

    • sad111359681 March 5, 2013 at 4:21 pm #

      😛 haha i didnt either until i looked it up online! thanks for post 🙂

  2. sad112759089 February 22, 2013 at 10:35 pm #

    Never knew what a Hybrid system was before, very interesting!

  3. sad111360051 February 24, 2013 at 4:11 pm #

    this is really good! you can learn a lot from this blog!

  4. sad111353781 February 27, 2013 at 7:20 pm #

    Such an interesting blog, keep up the good work 🙂

  5. garrett Thurston (@aerogman) July 3, 2014 at 1:14 pm #

    This is a decent swim lane formulation, I would be interested in exploring the relative use of Agile vs Waterfall in a regulated context for Stakeholder Validation much earlier in the process than represented here presuming left to right being earlier to later. Where the stakeholder participation might be in the creation of user stories and the development of a prototype with requirements completeness and correctness being the outcome of that process and then using that as the input for the regulated waterfall process. Thoughts, implications, suggestions, concerns?

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: