Search icon CANCEL
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
Implementing Microsoft Dynamics 365 for Finance and Operations

You're reading from   Implementing Microsoft Dynamics 365 for Finance and Operations Implement methodology, integration, data migration, and more

Arrow left icon
Product type Paperback
Published in Sep 2017
Publisher Packt
ISBN-13 9781787283336
Length 562 pages
Edition 1st Edition
Arrow right icon
Authors (3):
Arrow left icon
JJ Yadav JJ Yadav
Author Profile Icon JJ Yadav
JJ Yadav
Rahul Mohta Rahul Mohta
Author Profile Icon Rahul Mohta
Rahul Mohta
Yogesh Kasat Yogesh Kasat
Author Profile Icon Yogesh Kasat
Yogesh Kasat
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Introduction to Microsoft Dynamics 365 FREE CHAPTER 2. Implementation Methodology and Tools 3. Architecture and Deployment 4. Project Initiation and Kickoff 5. Requirements, Business Process Analysis, and Traceability 6. Configuration and Data Management 7. Functional and Technical Design 8. Integration Planning and Design 9. Building Customizations 10. Analytics, Business Intelligence, and Reporting 11. Testing and Training 12. Go Live 13. Post Go Live Support 14. Update, Upgrade, and Migration

Solution blueprint


Solution blueprint is the ultimate visual a project. It's a midway checkpoint, the acceptance of which means that the project now changes its phase from assessment to building. A solution blueprint is always best when represented in an end-to-end flow diagram showing all the solution elements that are envisioned and agreed to be leveraged from here on.

A typical business blueprint must cover everything that the business is going to leverage in their future state operations. The solution blueprint is now the central-most important element when making any key decision and adjusting scope, and going forward, it will be leveraged in almost all the deliverables in the project.

All project stakeholders should have access to it, must have a voice to suggest optimizations, and must be involved in accepting the solution blueprint.

A much detailed document called the Solution Design Document (SDD) is recommended for in-depth documentation of the solution details, using the solution...

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 €18.99/month. Cancel anytime