There are core stages to an AX Software implementation which are fundamental to a D365 Project & Programme Management role. Within these stages there will be different sub-activities detailing these within a plan is essential, the form of that plan can vary with Agile and Waterfall methodologies and often a mixed mode ‘Wagile’ approach. However the principle is get these stages detailed, attach milestone tracking points and at the very least plan for the following in your D365 project.
The first stage of a project and programme management activity always has to be a review of the requirements, you may think that you have a detailed set of requirements already well defined but often what can be listed as a single requirement will break down into multiples thereof with tendrils that extend into other departments and functional roles within the business. Each has the potential to create a configuration piece of work and to get an accurate plan you need this detail.
All D365 requirements have to be built into the plan, each will have effort associated with them, will require discussion to determine best approach, will involve system configuration, workshops to proof the solution, documentation, testing etc…
Simply put everything takes time, time costs money and its better to do as much of it upfront than revisit and potentially redesign what has already been done if something was missed.
The planning stage takes all the requirements and provisions time for all the activities and matches these to the people doing the work. If working to deadline and that does not match the plan something has to change, you can change the time line, drop things from the requirement list or increase the resource.
Ultimately the agreed plan will be the output all parties work to, it reflects the budget, the deliverables and timeline, it is the essential backbone of the implementation project. The plan can be in the form of the traditional MS Project form, something more abbreviated or Dev Ops but it has to be controlled with changes agreed by all parties and all workstreams duly informed.
You often hear terms such as Waterfall project plans or Agile, the fact is there are advantages to both and interestingly some workstreams benefit from a mix of the two (HR for example – call and we can explain) but put simply you start with a plan and execute against the latest version of it.
The planning approach is something partners and clients agree upon sometimes there just isn’t the appetite or budget to accommodate the type of approach preferred and we frequently end up with something in the middle ‘Wagile’ been the term there!
Following the plan, the build commences, nowadays Sprints are a typical way in which plans are manifested into configuration and build, following which D365 will be demonstrated to the business showing those key areas of functionality that meet the requirement and how this configuration was achieved.
Identified Gaps in standard functionality are reviewed, potential solutions played back and a decision on how to fulfil any Gaps deemed to important not to address.
If the company is distributed across multiple locations and territories, then discussions will include the functional requirements in the local offices, considering how the existing systems currently operate, the local market demands and balancing this against the advantages of standardisation.
These discussions will also incorporate legal structure and types of entities (incl. branches, JV’s, dormant, earn-outs etc.), management and group reporting.
Build and implement are really one and the same thing, once the D365 configuration has been completed the business is in a position to consider a first round of user acceptance testing – UAT
Go-Live & Hyper-Care
On successful completion of UAT the business is ready to cutover to go-live operations, data is migrated from old systems to new, users provided with security and access profiles, balances and open transactions checked and confirmed. Again all the activities and tasks will reside in the plan and be ticked off as completed.
Hyper-car should accompany go-live where consultants are on hand to sort out those inevitable issues that will arise, a month is normal but the rate at which the issues list disappears is the health barometer here. Click on the hyper-care logo to read more about D365 hyper-care and why we think this so important.
Each of the above stages will have a review phase, essential to monitor the progress of the overall programme. Constantly monitoring progress removes hidden surprises and informs all as to the status, whether further information has come to light, if there are challenges to overcome, impact on timeline and budget.
It has to be clearly understood at all times and by all stakeholders where the programme/project stands in terms of its goals, objectives, timeline and budget.
Summary
The above is not by any means a definitive list of all that goes into a Dynamics implementation but lays out the logical steps in a project.