Dynamics 365 Business Central Project Management
As a cloud focused, Australian owned Microsoft Cloud Solution Provider Partner, our business has grown based on our track record and reputation for putting ourselves in the shoes of our clients and delivering the most appropriate advice when it comes to considering a future technology landscape based on Microsoft Dynamics 365.
Our Approach and Methodology
Our methodology is an agile approach. Our starting point on all projects is to understand and clarify the scope of your business and map it to Microsoft Dynamics 365.
During the project we will run weekly sprint cycles so that you are always in control of your implementation. Track progress and watch your solution come to life. Each week we will play back what has been configured and setup as part of your new business application. We work directly with your team and take them through the business process and system solution. Where needed, CoreBiz will provide support to our customer in their attempt to cleanse the data prior to being migrated into D365. There will be opportunities to validate the migrated data in a D365 environment prior to going live.
This as an opportunity for our customer to reengineer their business processes by leveraging the opportunities that are provided by Microsoft’s ERP cloud solution. An opportunity to rethink and redesign the way work is done to better support the organisation’s mission with the benefit of cost savings.
Our work progresses through 4 key steps as follows:
Project and Solution Governance
Recommended Governance Structure:
- Identify the Project Sponsor a. The sponsor is the owner of the project
- Identify and assign the Business Process Owners (BPOs) a. The role of the BPO is to understand the current business process in their area of the business
- The establishment of the Executive Steering Committee
a. Purpose is to provide support, guidance, direction and oversight of progress. This board will make decisions, provide the funding and control any changes (change request approval). This is the final layer of any escalations.
b. The Project Sponsor is the chair of the Steering Committee.
- Design Authority
a. This design authority will be the collection of all the business process owners. All design decisions and the alignment across all business functions will be served by this group.
- Formal Project Tracking a. Project Charter for all the roles and governance forums above
b. Main objective:
i. Project Quality
ii. Project Cost
iii. Project Timeline
iv. Project Resourcing
b. Be the decision maker for their business area
c. Provide the business requirements in the design phase
d. Become the change champion moving forward into the implementation phase
i. Train their team to enable readiness for go live
ii. Provide cutover activities
iii. Support the business post go live
iv. Enable ongoing improvements
b. Project Management plan outlining the change control, risk and issues management processes
c. Establishment of a detailed project plan (updated weekly)
d. Formal roles and responsibilities
e. RAID Register
Issue and Risk Management
During the project a formal Risk & Issues register will be enabled to keep track and mitigate any risks. At the commencement of the project an initial risk workshop will be held to identify all the initial risks and put mitigations in place. This register is reviewed at the weekly project meeting and presented to the Project Steering Committee as required.
Measure of Success
Considering the motives for each project a listing of the measures to prove the project was a success will be agreed upfront and managed throughout the project.
Examples are listed below;
- Dynamics 365 replaces all operations/functions performed by the legacy system to the point where users no longer have to login to the legacy system to perform day-to-day tasks.
- We eliminate at least 50% of the currently identified Manual Processes.