Book Image

Becoming a Dynamics 365 Finance and Supply Chain Solution Architect

By : Brent Dawson
Book Image

Becoming a Dynamics 365 Finance and Supply Chain Solution Architect

By: Brent Dawson

Overview of this book

Implementing an ERP project is a daunting task, and it can often get derailed due to several reasons, including but not limited to inefficient planning, inadequate resource scoping, insufficient working knowledge of ERP systems, and more. Becoming a Dynamics 365 Finance and Supply Chain Solution Architect helps you understand the intricacies of ERP project implementation for seamless deployment. This comprehensive guide helps you gain a deep understanding of how to implement and optimize robust business applications that meet the evolving needs of organizations. You’ll discover various integration methodologies to integrate different software applications and plan successful data migration seamlessly. By leveraging the author’s expertise, you’ll explore different challenges that can lead to project failure or cost/time overruns, along with customized solutions to maneuver past those issues for a successful outcome. By the end of the book, you’ll be able to identify potential issues that can negatively impact the delivery of the project and make design decisions that will prevent any potential negative impact on the design and functionality of the system at go-live stage.
Table of Contents (18 chapters)
1
Part 1: Architectural Considerations and Best Practices for D365 Finance and SCM
8
Part 2: From Solution Design to Deployment – Practical Advice

Governance

Another task that we need to complete early on is how we govern the project. Governance is the framework we agree to follow. Part of this has already been completed as part of the pre-sales process, where we agreed to follow Success by Design and a hybrid project management method. One of the other outputs of this exercise is creating a success checklist. We need to have a list of successes that we can measure. This will help to get the project to a point where we can legitimately say, yes, the project fulfills our requirements.

The following is an example of some measures we can use to track success:

Architecture

  • Data migration
  • Data model
  • Functional design
  • Integrations
  • ISVs
  • Performance
  • Security

Implementation

  • Life cycle
  • Business continuity
  • Change management
  • Cutover
  • Fit/gap...