Step #1

Understand the approach and complete detailed planning

Plan your project

We have provided %customer% with an enablement plan, please take the time to familiarize yourself with the activities and schedule.

The following pages of this section also provide an introduction to the Enablement approach, please make key members of your team take the time to familiarize themselves and complete the required information. This will ensure we can all hit the ground running!

Template Plan

As you review the plan please start to plan:

Key dates, including availability for workshops and unavailability
Key project dependencies
Confirm Foundation Workshop attendees
Confirm your team (including list of SME's) with contact details and availability (see page 3 for team structure and roles)

Click here to view the Smartsheets plan

What is Smartsheets & how will it be used?

A Collaborative Project Management Tool. Your Internal Project Manager will own this as it is handed over during the foundation sprint.

Broken into key phases
Embedded with Artefacts to Support Delivery
Provides Granular ability to maintain tasks (including ownership, access, alerts, and full audit trail)

Template Plan

As you review the plan please start to plan:

Key dates that you are unavailable for project work (PTO planned, etc)
Your preferred days/times to work on the PSA project with the project team
After project Kick-off a more thorough schedule will be developed

Click here to view the Asana plan

What is Asana & how will it be used?

Asana & Instagantt provides a collaborative Project Management tool. To view the plan in Instagantt, click here and sign in with your Asana account. We will review this plan with you to confirm a critical path that all stakeholders and contributors are aligned to.

Familiarize yourselves with the Enablement Approach

It is important that everyone is aligned on the overall approach. We take an iterative sprint-Based Approach. The configuration is tested and refined throughout; we might refer to this approach as ‘iterative’. The following section provides an overview of the key phases and activities, which you will see outlined in the provided Smartsheets plan.

Mobilisation / Kick-Off Meeting

Here we set-out both your and our roles and responsibilities for the wider teams. We align your enablement with your core needs & objectives and ensure everyone understands the overall objectives and measures of success.

Foundation Sprint

This is an End-to-End run through that helps bring your core team up to a consistent level of understanding. We review the Operating Model Canvass (see next section for details on this); It helps us build out your configuration as required. We conduct a Policy Review to ensure we understand any existing agreements and constraints that we will have to configure for. Follow-on Sprint content is defined and planned in detail

Sprints: Each Sprint follows the same cadence below with some flex and effort planned around your business outcomes.

Sprint Planning Review – reviews the content of the in- flight sprint
Process Review – Builds-out your business processes from sprint to sprint; sprint one is based on the lead to order process, sprint two will follow the scope to delivery and resourcing path – content is refined based on the number of sprints
Training / Deep Dive – we walk through the business processes and train the core team on Kimble
Functional Definition – we draw on feedback from above and revise any configuration
Configuration – a Kimble activity getting your org ready
Review and Test Configuration – We re-play your process model to you with the new configuration in place; you run your user stories (tests) on our config to support your business model and processes
Sprint Planning Review (late) - consolidate incomplete activities from the current sprint and forms basis for the next sprint

Familiarize yourselves with the Enablement Approach

A closer look at what occurs from sprints:

User Testing: Your User Defined Scenarios for testing are built up from the content of all workshops and sprints. Initial testing Questions and Issues triaged by your Project Team – fed back to the Kimble team for Q&A

The Kimble Project Team run frequent reviews to provide support and configuration refinement where necessary, we might build in some weekly surgeries (30 min – 1 hour calls) to help users.

Design Review An event that invites you to participate in a general Q&A from our Professional Services Leadership Team who analyse your build to date making sure it supports your business requirements and fulfils your needs to operate business as usual. This is your chance to feedback into the enablement process and review your configuration with your Kimble Enablement Team

Quality Assurance: This is a Kimble Internal review of the complete configuration. Client Acceptance Certification based on your testing and adoption to date, you’ll be asked to sign-off the configuration against your Business Requirements

Post Acceptance – what happens next?

Deployment This is a Technical Cutover from any Sandbox Environment into the Production Environment. Here, Data Migration of in-flight projects takes place ready for Business Go Live.

Go-Live Support Prior to Hand-Over to our Support Teams, you will receive System Administrator Training which ensures that you can support your org internally with the fundamentals of running Kimble such as User Maintenance and Creating New Products and Commercial Models etc. Kimble sets-up a Hyper Care team during the first days to ensure that you have immediate access to Professional Services consultants.

Your Customer Success Manager will be with you during go-live to lend additional support to your team and capture any immediate issues previously experienced

Mobilize your team and governance

Start to Mobilize your team : Please provide names for key individuals within the organization who will undertake key roles as outlined in this table. Note people may perform multiple roles, so please update this to reflect your business structure and the people who will work with Kimble on the project.

Prepare the project governance: We recommend regular Steering Committee Meetings, please start to plan who will attend these. We also suggest you start plan for any projects risks.

Team Roles:

Exec Sponsor - Attend Steering Meetings and acts as escalation point and overall champion.
Project Manager - Overall responsibility for managing plan, activities and governance.
SME/Super Users – split across process/region areas - Internal experts/champions. Define requirements, execute testing and UAT. Drive prioritization and make required business decisions.
Subject Matter experts (Business and IT) for relevant External Systems - Subject Matter experts from business and IT for any dependent systems.
Business Analyst - Overall responsibility to support SME’s e.g. user stories, testing and documentation

Testing Lead - Creation, definition and management of Strategy, plans and execution.
Training /Change Management Lead - Define/develop training and change management. Managing all business change.
Trainers - Execute end user training.
Deployment Lead & Managers - Plan and Manage deployments across business units/countries.
Salesforce System Administrator - Provide required environments and support configuration of key aspects relating to the salesforce platform e.g. permissions sets, roles.