The link to the website Think for a Change no longer works, unfortunately. I don’t know why. However, I have left this post intact. There was a very good article over at the website Think For A Change on the differences and similarities between the Software Development Life Cycle and the Project Management Methodology. The article was called The SDLC is *NOT* a Project Management Methodology. As mentioned, this website “Think for a Change” does not seem to be up any longer.

A common misperception amongst project stakeholders is the erroneous belief that the Software Development Life Cycle (SDLC) is a project management methodology. What are the differences between the two? What are the similarities? First of all, the two are complimentary to each other for information systems development projects.

The project management life cycle adds two phases that the SDLC does not have:

• Initiation and Approval – before the SDLC even starts
• Closing – after the SDLC completes (however the SDLC doesn’t actually complete – Maintenance Phase)

The SDLC adds one phase that is not part of the project management life cycle.

• Maintenance Phase

In a perfect world, the PM processes should be led by a Project Manager and the SDLC processes should be overseen by a Systems Manager.

Above is a diagram from Think For A Change website, which unfortunately does not appear to exist any longer.

SDLC vs. SDLC

There is a difference between the Software Development Life Cycle and the Systems Development Life Cycle.

The software development life cycle is often interpreted as a step-by-step approach where you fully complete as step (as best you can) before moving on to the next. However, I believe, in the real world you should take more of an Agile approach.