Why Are Implementations Faster with Kenandy?
By Lisa Schagunn and Emilia Meldrum-Taylor
Whenever you implement an ERP system—whether it’s on-premise or on the cloud—you must address some key functional considerations to ensure a successful deployment. Traditional software vendors realize that deploying their ERP solutions is a very difficult and lengthy process. Recognizing this, they have devised various methods (such as the use of templates and accelerators) to speed up the operation. Unfortunately, the success of these approaches has been predicated on deploying “must use” business processes and configurations.
So, what happens if your business is highly innovative and you want to leverage your own best practices?
The Traditional Waterfall vs. Agile Approach
Most existing ERP systems were developed using the Waterfall software development methodology. Though variations to the Waterfall approach are common, they all share a consistent theme: Testing and Conference Room Pilots (CRPs) occur well after a prolonged Design and Build process. In the meantime, the business might have evolved, or the stakeholders might have shifted on specific requirements, causing the implementation team to return to the proverbial drawing board. This slow and painful process is one of the main reasons why ERP implementations are notoriously behind schedule and over budget. Time and money are disproportionately spent on documenting requirements rather than actually building a solution. The end result is a system that bares a striking resemblance to the one the customer wants to replace.
The Agile development methodology is gaining significant traction in many organizations, where small “scrum” teams are trained to work in quick cycles. Lamentably, traditional software companies lack the agility to support the Agile approach, and these shortcomings are reflected in their ERP solutions. They require laborious upfront configuration, and without a preconfigured template, the implementation process suffers from an extensive requirements-gathering cycle and long design phases.
For example, you must install and extensively configure the application to simply enable basic processes, such as order-to-cash. System preferences must be carefully tuned and repeatedly tested before the solution is even presented to the customer.
Below is step-by-step comparison between the traditional ERP Waterfall methodology and Kenandy’s Agile approach for a single-facility company leveraging Financials through Manufacturing.
With Kenandy Cloud ERP and the Agile methodology, companies can rapidly increase time to training and go-live. You don’t need to purchase and configure hardware, download software, burn DVD’s, or hire an expert DBA to install the system. With Kenandy, provisioning an org only takes a few hours. You can then easily load data and rapidly start the prototyping process.
Want to read the full white paper? Click here to find out more about why implementations are faster with Kenandy.