Why to give up on Microsoft Project (and Waterfall Methodology) and why it’s still being used

This was originally intended for Microsoft Project, but because MS Project is based on Waterfall, it is best to add Water Methodology as well. Why it’s time to give up on Microsoft Project and Waterfall Methodology

• Waterfall methodology is dying a slow death and this methhod works best with Microsoft Project
• Microsoft Project will be merge into their Microsoft Planner tool sometime in the future and it’s quite obvious.
• Agile is now king
• Defined requirements decrease the room for creativity within the staff. Defined requirements work best from the standpoint of “because I said so” approach.
• Waterfall methodology is usually always more costly and Microsoft Project you must pay for from the start. There are plenty of free tools that can be used instead.
• Requirements can be misinterpreted
• More effort is put into the documentation then the actual building of the product, which slows down the process from a to z.
• Times have changed. Microsoft Project and Waterfall Methodology barely has.
• Change is happening faster than ever and Microsoft Project and Waterfall are not known for this
• Microsoft Project is Desktop Application
• It’s near impossible to rack real progress in MS Project on a daily basis.
• You must use other tools to fill in the gaps

Reasons why Microsoft Project and Waterfall Methodology is still being used

• In order to be collaborative with clients, project managers like to use the same software as their clients.
• The majority of government still rely on projects based on Waterfall Methodology and thus Microsoft Project works best for, but project based on waterfall methodology is known for delays and etc. Government project is slowly, but surely adopting the agile methodology, which Microsoft Project will never match other tools like JIRA, BaseCamp, Microsoft Azure DevOps, and etc.