Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why Have a Separate Project Management Methodology?

methodology separate
0
Posted

Why Have a Separate Project Management Methodology?

0

The methodology most organizations are referring to is some type of Systems Development Life Cycle (SDLC) with a bit of project management thrown in. The project management methodology should address the specific project management deliverables. This includes specific processes for project initiation, prioritization, project planning, status reporting, issue/decision/change management, quality management, risk management, etc. These fundamental elements of project management apply to virtually all projects. The same basic project management methodology should work whether one has been implementing a new customer application or if one has been managing an office move. What would be different is the “Product methodology” – the methodology one needs to use to deliver the product or outcome of the project.

Related Questions

Thanksgiving questions

*Sadly, we had to bring back ads too. Hopefully more targeted.