Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Becoming a Dynamics 365 Finance and Supply Chain Solution Architect

You're reading from   Becoming a Dynamics 365 Finance and Supply Chain Solution Architect Implement industry-grade finance and supply chain solutions for successful enterprise resource planning (ERP)

Arrow left icon
Product type Paperback
Published in Jun 2023
Publisher Packt
ISBN-13 9781804611494
Length 270 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Brent Dawson Brent Dawson
Author Profile Icon Brent Dawson
Brent Dawson
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Part 1: Architectural Considerations and Best Practices for D365 Finance and SCM
2. Chapter 1: Overcoming Challenges in D365 Finance and SCM Projects FREE CHAPTER 3. Chapter 2: Understanding the Microsoft FastTrack© Process 4. Chapter 3: Dealing with Integrations 5. Chapter 4: Efficient Security Design 6. Chapter 5: Planning for Successful Data Migration 7. Chapter 6: Licensing Challenges 8. Part 2: From Solution Design to Deployment – Practical Advice
9. Chapter 7: How to Plan a D365 F&SCM Project 10. Chapter 8: Learning the Client’s Business 11. Chapter 9: Collecting Project Requirements 12. Chapter 10: ALM Tools and Applications 13. Chapter 11: Human Change Management 14. Chapter 12: Building a Blueprint Solution 15. Chapter 13: Deploying the Project Solution 16. Index 17. Other Books You May Enjoy

Where to start?

Every project needs a place to start before a solution can be created, and even before we can start asking people what their requirements are. My recommendation is to start with existing business processes. Sometimes this is easier said than done, but this is where you start.

But what happens if you are assigned to a project and the client doesn’t have any documented business processes? That makes it a bit more challenging. In that case, if I were the SA during the pre-sales engagement, I would suggest recommending to the client that they do a diagnostic. I define a diagnostic as going in and looking at the current system they have and how a given person completes certain tasks. This way, you are not taking time out of the main project to get this information.

In fact, if you can sell an analysis and design phase, you can produce the business processes and start to work on the solution blueprint. Then, you can use this as the project’s starting point...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime