Last Modified: June 17th, 2021
The conventional implementation process isolates the clients or businesses in the development of the implementation which can hinder clients from providing feedback to the NetSuite Implementation team.
The conventional implementation process relies on a linear development of the waterfall model. The waterfall methodology best applies to rigid management processes that apply most in construction industries where a fixed design and objective is in place from the very beginning. The linear waterfall methodology may not apply best to the ever-changing and dynamic environment of software development like NetSuite Implementation where specific customization and design specification are changing with each stage of the implementation.
The Agile Methodology
The agile methodology is Excelym’s approach to a successful NetSuite Implementation process. Excelym uses Agile in software development which is a part of the Agile methodology for greater adaptability and faster implementation through the iterated development of the implementation through modules and sprints.
The agile daily meetings allow for greater collaboration between clients and Excelym’s NetSuite Implementation Consultants. An agile team is a small group that consists of the client or product owner and the NetSuite Implementation Consultants assigned to specific roles.
Excelym has two types of teams for NetSuite Implementation. One team is specific for purely implementing NetSuite out of the box and another team is for NetSuite Implementation, customization and integration of third-party applications like Salesforce, Shopify and etc. The NetSuite Consultants determine if there is a need for specific customization according to the client’s requirements.
Sprints are the progressive iteration of NetSuite’s Implementation. Excelym’s sprint typically lasts for 2 to 4 weeks depending on the degree of the client’s specifications Each sprint is started with a sprint planning meeting where the team members together with the client. The team together with the client defines any backlogs, identify the scope of work and modules for the sprint.
Each sprint is culminated with a sprint review meeting together with the Agile team and the clients to review the progress, formulate feedback and develop ways to further improve the NetSuite Implementation in the next sprint. This allows for the continual improvement of the NetSuite Implementation.
For more about Agile Methodology: Delivering a Cloud ERP Implementation with Agile
The Beginnings of a Sprint
In the early stages of NetSuite Implementation, the specific roles of the Agile team are assigned and a client representative is identified. The roles of Agile team are typically the lead business consultant, the business analyst and the QA testers together with the product owner or client. The presence of the product owner or client in Agile team meetings is one of the core aspects of the agile methodology.
The key role of the lead business consultant is to facilitate and guide the team throughout the NetSuite Implementation. The main role is to ensure that the cadence and timeline of the sprint is being followed and help the team determine key points of improvement from client feedback. The team lead is also responsible for educating the clients, product owner and key stakeholders of the progress of the sprint and the whole project.
The implementation team is comprised of team members with specific tasks and roles to help accelerate the NetSuite Implementation. The specific roles are assigned to avoid confusion and delegate the task according to the team member’s specialization like business analysis, and quality assurance testing.
Excelym’s Agile Methodology in NetSuite Implementation
Excelym has successfully adapted the Agile methodology in its NetSuite Implementation. The company has successfully deployed NetSuite to over a hundred different clients from different businesses and industries sector with varying degrees of customization according to their specific requirements and demands. The Agile Methodology allows for greater collaboration between Excelym’s Agile team of NetSuite Implementation Consultants and the Product Owners. The improved interaction allows for greater adaptability through immediate feedback between Sprints and subsequent improvement derived from the Agile Meetings.
Excelym’s implements NetSuite ERP through 8 sprints that typically last 2 to 4 weeks per sprint depending on client demands and specification. The first sprint focuses on the consultation of the client or business owner to identify existing business processes, business requirements, and specification. The first sprint is crucial in determining the critical points during NetSuite Implementation.
The second sprint involves the actual migration to NetSuite. The Agile team then helps the future users of the NetSuite ERP to adapt to the new environment by creating user-accounts and setting up user status and account hierarchy in NetSuite. The Sprint 3 and Sprint 4 setups the processes that are to be automated and setting up products that are included in the inventory. The step also includes the integration of vendors and suppliers in the supply chain. Sprint 5 focuses on the automation of business processes like General Account and Budgeting. Sprint 6 and 7 focuses on order to cash and sprint 8 focuses on data migration to NetSuite.
The advantage of using Agile Methodology in implementing Netsuite lies in the ability of the Agile team to move and adapt quickly based on the requirements of the clients. The involvement of the client also ensures that the lessons learned from previous sprints are quickly implemented in the succeeding sprints. The close collaboration of the clients together with the implementation team builds a better business relationship and improves customer satisfaction.
By including the client in the loop gives them the ability to provide crucial insights that help the implementation determine the best approach to the implementation of NetSuite. One of the benefits of agile methodology is that it focuses more on the results than the tedious reporting process that is common in the waterfall system.