OK let me explain. I have seen a number of project management frameworks that include what I would consider System Development Life Cycle artifacts not just project management artifacts.
For example a system design document to me is a product of the project not a product of the project management framework/methodology, but all too often they get wrapped up into a customised, lets call it a "project delivery methodology".
Anogther example is Agile, again this is an SDLC tailored for IT delivery but some people call it Agile project management, is this the same thing?
I am not saying that either is good or bad, but there will be pros and cons for mixing up the different life cycles. One of which,the PM framework becomes less applicable to all projects and only applicable to one specific project type, is that a pro or a con? Saving Changes...
