Pending work to be done
- Create
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. This article assumes the project products (hereafter: Epics) are defined and the project plan is made.
General approach
Because the project is broken down into epics and phased over time based on priority, for each epic the same process can be followed as visualized above. This means, different epics can be implemented in parallel and epics can be in different steps of the process.
Step | To do |
|---|---|
Know the client’s business | In addition to the general understanding of client’s business documented in the business profile, now focus on the epic specifics to make sure the advised approach can be accepted by the client. Update the detailed knowledge and target goal in Epic description. |
Setup functioning prototype on test environment | Setup the functioning solution on a test environment for the client to experience and validate. Make as much as possible use of default MXTS import sheets where available, so they can be handed over to the client as part of user training. Embed Maxxton’s best practices rightaway in the advised setup needed to deliver the epic. |
Solution refinement for client acceptance | Validate, refine and confirm the solution on test environment to meet client’s acceptance criteria. |
Data entry on Live environment | Get the required data on Live environment. Handover and/or re-use any earlier created importsheets to the client for Live population. |
End2end testing | Take a holistic approach when testing met (typically) MXTS configurations. Identify, clarify and conclude any impact on related relevant solutions like Guest Environment, guest communication, API |
Go Live | Take epic into live usage |