Agile software implementation methodology contributes to ERP failure.
- Drafting SOWs that include milestones, deliverables, and deadlines is challenging when Agile is utilized.
- Its iterative approach is not compatible with holding your ERP integrator accountable.
- Spending less time defining the product beforehand and trusting that the product will come together one iteration at a time is problematic.
- Focusing on (i) developing working software over a comprehensive product, (ii) collaboration over contract negotiation, and (iii) responding to change over following a plan all create challenges when it comes time to enforce contractual obligations – especially when deadlines, milestones, and acceptance testing criteria do not exist.
Agile is a software development methodology. It is not an ERP implementation methodology. It does not lend itself to carefully crafted Statements of Work with deadlines, milestones, and substantive contractual obligations.
This is a problem. I discuss these issues in my latest YouTube video.