🛠️ Delivery and Implementation
      Back to home
      1. Help Center
      2. Best Practices and FAQ
      3. 🛠️ Delivery and Implementation

      What Methodology is used to Design and Deliver the Project?

      Following a proven and tested methodology with agile and iterative approach

      In this article:

      We use a framework to enable our customer success managers deliver projects with ease and clarity.  It’s the next-generation project implementation methodology used to implement and deliver innovations and solutions.  Built on agile methodology, it takes an iterative approach to continuously improve and deliver to increase your project quality and success. 

      Together with the customer, we will go through each of these phases from the minute we discuss and decide on the desired program design, to implementing them and using the solution to streamline processes internally.  All these touchpoints are mapped into 4 major phases during our journey to make the best out of the new program and system delivery:
      Prepare --> Explore --> Realize --> Deploy  

      Prepare Phase

      In the prepare phase, we do the enablement and the program design work.  We also provision our test system in the public cloud. We integrate it with your HR test system so you look at something that is familiar.  You will have an initial system, ideally even an executable demo program content. 

      Even though it’s a demo content it is still something that can help us all better understand the product & map it to your desired direction – or where do you want to go from the current state of the programs.  This would really help us define the starting point all the way to understanding the program design details, which need to be defined and refined. 

      During the prepare phase we complete key activities that are crucial to the project success, with mutual consent between us and you as a customer. Your business process owners are identified to provide the right requirements to our implementation team.  A high-level project plan along with roles and responsibilities is finalized, along with the: project team, project governance procedure, escalation matrix & the project is ready to kick-off!

      During this phase, an initial level of requirements and program design definitions are collected. These documents will be used to accelerate the project execution.  Also we need to plan for probably the most important phase in the methodology – the Explore Phase.

      Explore Phase

      In the explore phase, we perform the desired configuration based on the program design and ultimately look at certain solution validation workshops, feedback rounds and so on.  Ultimately, this will lead to a solution that is verified to meet the customers business needs. The explore phase also lays the foundation for the success of our project.  In this phase, we collaborate to finalize the business processes that will be followed by conducting a series of “Fit-to-Standard Analysis” sessions, where best-practice process flow is showcased and discussed with your Process Owners.  We will display a flowchart of the business process and later drive a scope using the initial system that was provisioned. Usually, the project team has a healthy discussion on how the business can map your case to the best practices.  

      One of the best parts of the explore phase is the customer execution of standard processes. What this step tries to achieve is to build an early relationship between the key-users and the system for an easier and accelerated adoption of widely accepted business processes.  

      So, we provide users with the required knowledge base and help run an end-to-end cycle in the system.

      The previously self-enabled users are now familiar with the system, and provide consensus that they executed the business process, into it.  All your requirements in terms of New Programs, Workflows, Reports, Integrations, and Enhancement are noted in a backlog document, which is mutually signed off.   Also, a change impact analysis is done to understand how the new system will benefit the project business and stakeholders, and decide on actions to enable a smooth transition to the new system. 

      Key users are identified, an end-user learning needs analysis is done and a learning plan is prepared for the different group of users, who’ll help drive the success of the system during the project duration.  Once the Explore Phase deliverables are signed off, our project team starts working on the next iteration of configurations and development in the test / quality system.  

      Realize Phase

      The realize phase is going to be the final round of configurations, system walkthroughs custom developments, data migration or extensions. During this phase, we start configuring the system according to the agreed and final document.  This happens in an iterative approach where the project team works based on multiple sprints that had been planned to execute the project, by breaking down the backlog requirements into smaller deliverables, which need to be showcased to the process owners and signed off as completed, once they match the agreed-upon completion criteria. 

      This is the phase where we are in a regular communication with the customer process owners to showcase to them the system we are building, through multiple Solution Walkthroughs that are scheduled through the Realize Phase.

      Roles and Authorizations can be a hectic process especially in large projects.  We provide standard persona-based roles that help business users with tasks through an End-to-End business process. For an example, an HR admin will be provided with standard roles required for a HR Admin in the JobPts system, an IT manager will be provided with the standard role enabling them to perform tasks per our best practices. 

      Very importantly, in this phase, multiple levels of testing are performed to ensure the system is configured according to customer requirements.   Data migration, if required, is also done to ensure the data filled in by the business users is in the correct format and ready to be imported.

      Once all deliverables are satisfied, a cutover plan is made to move the configurations and data to the Production system which will be used in real-time. This signifies the end of the Realize Phase.

      Deploy Phase

      In the Deploy Phase, we prepare the production instance. All the things done in the test system are brought to the production system, we check integration with the customer HR production tenant.  Also the change management gets executed, communication is done, training for the managers is performed, or anything else from organizational preparation aspect and ultimately to be ready for the Go Live.

      In the Deploy Phase, once every checkbox is ticked and everything is ready, the new system is deployed for usage to the business users. This is the culmination of all our hard work being moved into the new recognition and rewards system for the usage of an entire company. 

       

      If this article left your questions unanswered, please submit a Support Form, and we can clarify this topic.