...
...
| Table of Contents | ||
|---|---|---|
|
Pending work to be done
- Create best practice page with solution and configuration advises
- Improve setup new concern process based on MOL-6 + identified improvements based on other insights (journals, journal periods, DC hierarchy, default scripts to run, default roles & rights, default templates etc)
- Review standardized ticket list and add all kind of detailed small knowledgable tasks which you run into during implementation, if they cannot be included/improved in the setup new concern process (configuration of internet user, fiscal year, enable cleanup script initial bookings, enable customer deduplication, enable cash register toggle at addon type level, TS plus accounts if needed etc)
- Update standardized ticket list regarding ticket descriptions. Update legacy and add MXT Academy links where possible
- Create library of standardized data migration + validation scripts. Could entail customers, owners, reservations, ledgers. (Or re-develop / improve MXTS Implementation Manager now content manager team is mature?)
- Create list of default templates. Ideally a sub page with files which can simply be imported by the user or even added in new concern scripts.
What is it?
This article provides concrete tips & tricks when the project must be delivered. For this article to be useful, it is relevant the project is approached and prepared in accordance with the tools provided by the overarching implementation framework and general understanding of client’s business in there. This article assumes the project products (hereafter: Epics) are defined and the project plan is made.
Get a new concern in place
Starting point of getting our hands dirty in the system is to get a new MXTS concern in place, both a Live and Acceptance environment. This is purely an internal task, but in order to smoothen the process and kickstart the setup it is wise to consider the following during this step:
Tailor the internal request already to the new client (correct languages, currencies, base currency, default language etc)
Add as much default configuration for future use, if not already added via the new-concern-script. This refers to basic configuration required for an MVP functioning system, but which is often only stumbled upon when things are not working as expected rightaway (fiscal year, internet payment methods, cash account, front office configuration, reservation manager configuration)
Add default email templates so flows can be setup van validated end2end including guest communication
Add default user roles and rights to easily explain the concept and provide a plug&play standard setup
By including the above mentioned items in this step of the implementation, a high quality setup is ensured reducing disturbances down the road.
General delivery approach
...
Focus on project products
Closing tickets in itself does not lead to a successful implementation
Implementing is all about making sure the solutions can and will be used in Live production by the client. It would not be the first time all Jira tickets are closed, we think we are done and some time later the client gets back at Maxxton about something missing, not working as expected, not really clear etcetera. Avoid this situation by continuously making sure the proposed solution is complete, understood and accepted by the client.
...