This document outlines how we will manage a cross organization project and work together to deliver a working Kontainers Edge minimum marketable product (MMP) in 4 working weeks.
Kontainers Edge Approach
Once contracts have been exchanged, a dedicated Customer Success manager will be appointed to the customer. The first task of the Customer Success manager is to get up to speed quickly with the Customer and begin the education process.
Once an agreed start date is in place, the Edge project will be broken into four separate weeks of four separate deliverables.
Important: Ideally, the date we agree to start can be planned well enough so that we can have 4 continuous weeks of delivery. However, in most cases there will need to be a design period needed between requirements and delivery to test. In that case we will stagger the effort into 4 separate weeks of effort on a 'theme' so that any work by Customers team that may take time to implement can be delivered ‘just in time’ for the next phase.
Kontainers Edge Timelines
Week 1 Theme is about branding and design
We will schedule five, 1 hour conference meetings for each day of the 1st working week (This can start and finish on any given day of the week)
We’ll provide a set of 'tenancy' documents in advance that can be validated during this first week, they include
- A document to capture the ‘Trips’ you will support from Day 1
- A document to confirm what email messages you want to send and be passed to you from Day 1
- What Equipment you want supported from Day 1
During week 2 and week 3 (and after go live) we can make amendments to these supported configurations if needed.
Meeting 1, we walk you through the current product and help you identify the initial MVP (Minimal Viable Product) based on your target market for day 1
Day 5 of week 1 we will demo your Production facing environment, managed by you that you can configure and learn about your Kontainers Edge site and begin to test operational processes, consult with your support team, train your sales team etc.
We will also present a requirements note based on your desired MMP. This note will be the basis of an estimation exercise that will precede a week 2 exercise that will confirm the proposed MMP integration scope.
Finally, by the end of Week 1 we will have a date for Week 2.
Week 2 is about Tenanting, scope definition, architecture designs and Aha!
We will schedule five, 1 hour conference meetings for each day of the working week (This can start and finish on any given day of the week)
The Tenanting forms and designs from Week 1 will lead to some technical discussions if we are integrating Kontainers into legacy Customer systems. In that case, any Customer SMEs identified will be on hand to support design and planning of data contract, designs etc
By Day 5 of week 2
- We will have agreed data contracts so we can do our Week 3 work and be ready for Integration.
- We will capture ‘delta’ functional requirements from the core product, i.e. any agreed new scope that is not current functionality. Changes to Week 1 designs will be strictly controlled
- We will pre-populate our project management tool (Aha!) with ‘default’ tickets for planning, tracking and governance. We will track deliveries and progress as part of our daily meetings.
- An agreed test plan is in place
Going into week 3, we will have a high level project plan agreed between Kontainers and Edge customer. For customers who have opted for full Integration, we will need to factor in their ability to be ready for an agreed date with APIs, EDI etc. We will also have agreed a date for weeks 3 and 4
Note, we expect that week 3 and week 4 will almost always run into or very close to each other but could be many weeks between week 2 and 3.
Week 3 is about Production Integration and Functional Testing
Depending on the type of engagement, there may be a significant Integration and Testing deliverable.
For these larger integrations, the Customer may need a few weeks to prepare their teams and their data for Kontainers, Prior to Meeting 1 we will confirm with the customer that their commitments are on track.
- Test accounts and any customer production testers will need to be ready for any Integration testing.
- End of week 3 we should have a production ready product with selected trips, rates, schedules, etc in place.
- The best way to test is to get the real customers, UAT teams and support users (at least the Super Admin) to ‘learn by testing’
Regardless of the size of the integration tasks, at the end of Week 3 we essentially have a live system ready for operational training and deployments
Week 4 is Training and Operational Readiness
It’s in week 4 that some scope may change by agreement, we need to prepare for that and be ready to respond.
By the end of week 4 we will have implemented the Release checklist. This Checklist will change depending on the type of Edge contract but for our larger Edge customers it includes:
- This document contains tasks like ‘we have cleaned out test users and test data from Production.’
- Customer has enabled and verified their production data feeds
- All support staff have access and completed training
- Customer URL is enabled and Intercom, Mixpanel, branded support mails etc are configured
By day 5, week 4 we will be LIVE with a fully supported Kontainers Edge site.
Copyright © Kontainers.com All Rights Reserved.