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

Project management

I’ve been doing this for many years, and I can honestly say that using straight Agile for an ERP project isn’t a good way to manage a project. Because of the way that Agile completes its effort in sprints, you never really get the whole solution before you start to deploy. You only need to solution what you’re going to complete in that sprint. So, as far as I’m concerned, Agile is out. Waterfall is much better for ERP projects because you know the entire solution prior to starting the deployment part of the project. The downside of this method is that you don’t know how anything works until you get to the end of the project. That is not optimal, as you can’t get on top of any issues that may pop up before you’re ready to go live.

I prefer to go with a hybrid of waterfall and agile. The hybrid mixture works well because you get to bookend the project with waterfall methods, and in the middle of the project, you use...