Package Software Implementation and Agile

Executive Summary
These days’ package applications make up a large percentage of the business transformation projects.   A package application standardizes processes within an organization and streamlines data flow between different parts of the business. Most companies choose package applications to leverage off the shelf business best practices associated with package software, respond faster to the changing business needs and reduced TCO. Best practices and reduced TCO being the obvious benefits associated with package applications, major focus is around realizing faster time to market. System integrator acting as an implementation partner plays an important role in laying out a solution deployment roadmap for the customer and one of the most important factors taken into consideration is feature prioritization based on business need. Feature prioritization initiatives are jointly undertaken by implementation partner and chosen subject matter experts from the customer end.
This lays the foundation for success/failure of the program and is considered to be the most important phase of the project. Delivery of the software features based on customer priority takes the front stage from here on. Most of the package software vendor has their own implementation methodology which is mostly aligned with waterfall principles. Here comes the question: Do we really need to relook at the waterfall based implementation methodologies and reengineer them to gain immediate insight into the business value in a faster rate, increased flexibility in implementation and more transparent progress/status monitoring as the project moves ahead.
The Problem
What is the issue that demands resolution?
Waterfall being sequential in nature, the biggest bottleneck associated with waterfall is the delayed time to market. There’s very less room for error as the plan is frozen in the beginning of the project and followed with minor changes as the project progresses. Waterfall relies heavily...