Project products
- Frank Louwerse (Deactivated)
What is it?
A project product can be defined as something which is to be delivered by the project and can be taken into operational use by the client. It should be considered as the combination of configurations, features and tools that together form a solution which a client can start using in Production.
Examples:
Poorly defined project products:
Content Manager
Owner Manager
Templates
Better defined project products:
Creating touristic reservations
Creating reservations via third parties
Managing access control (barriers and doorlocks)
Defining the products is forcing us to take a client’s business point of view on implementations and hence improves our understanding of what the clients business entails and what the project should deliver. In addition, concluding the (typically) 10-15 project products will help the team with scoping, planning, phasing and focussing activities over time.
Project product defaults
Below is an overview of project products which can be ran into in our market. It depends on a clients characteristics which products are applicable, but the (non-exhaustive) list below can serve as suggested standard list to consider for each implementation. Detailing the products is not exact science, but this overview is intended to trigger the thinking and sharpen the project definition.
Project product | Description |
|---|---|
Creating touristic reservations (accommodations) | Entails all configurations needed to end2end support creating reservations in accommodations, including prices, offers, guest communication etc. |
Creating touristic reservation (camping pitches) | Entails all configurations needed to end2end support creating reservations in camping pitches, including prices, offers, guest communication etc. This product is isolated from accommodations, as camping content often requires different requirements in setup and bookflow. |
Creating seasonal bookings | Entails all configurations needed to end2end support creating seasonal pitches, including guest communication and energy settlement. |
Creating yearly bookings | Entails all configurations needed to end2end support creating yearly pitches, including guest communication and energy settlement. |
Creating touroperator bookings | Management of touroperator bookings (both via API or direct integration) including guest communication |
Support Booking-related other scenario’s | All other booking related scenario’s like cancellations, reallocation, upgrades, addon-reservation, sleep-overs (logé), group bookings |
MXTS Web solutions | Includes solutions to be delivered by Web Manager team, like website and/or booking funnel and/or guest portal and/or owner portal and/or paymentlink landing page. |
Processing payments | Ability to manage incoming and outgoing payments (repayments) |
Financial output from MXT to Accounting system and vice versa | Management of importing bank statements, accounting for revenue, reconciling financial data, year-end closing |
Customer data management | Importing customers, de-duplication logic |
Manage on site checkin-checkout | Everything related to the checkin- and check-out of customers, including reports and exports to support these processes |
Manage on site cash management | Cash register, payment for reservations, cash clearance, receipt printing |
Manage on site housekeeping | Housekeeping tasks, planning |
Manage on site maintenance | Maintenance tasks |
Business supporting connections | Any required data-flow to support operational processes, which could entail (for instance):
|
Managing owners | Could entail charging costs via yearround reservations, invoicing workorders, owner settlement |
Utilizing BI solution | Could include setup of MXT BI solution or expose needful data to feed external BI solution. |