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

Hierarchy of business processes and subprocesses 

There must always be an explicit link between business processes and the requirements.

It should start at a high level for the coverage perspective, but the requirements must be collected in detail. Asking the five Ws is always a good idea to ensure that enough details are collected.

Five Ws: Why, What, Where, Who, and When
When solution envisioning is performed, another crucial question, How, gets answered.

All the business processes that will be part of the initiative and each of their subprocesses must be considered for preparing the requirements list. There should never be a requirement without being linked to one or many processes; alternatively, there should not be any process/subprocess that does not have any requirements. Any such situation, wherein a requirement does not belong to any business process...

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