Book Image

Implementing Microsoft Dynamics 365 for Finance and Operations

By : Rahul Mohta, Yogesh Kasat, JJ Yadav
Book Image

Implementing Microsoft Dynamics 365 for Finance and Operations

By: Rahul Mohta, Yogesh Kasat, JJ Yadav

Overview of this book

Microsoft Dynamics 365 for Finance and Operations, Enterprise edition, is a modern, cloud-first, mobile-first, ERP solution suitable for medium and large enterprise customers. This book will guide you through the entire life cycle of a implementation, helping you avoid common pitfalls while increasing your efficiency and effectiveness at every stage of the project. Starting with the foundations, the book introduces the Microsoft Dynamics 365 offerings, plans, and products. You will be taken through the various methodologies, architectures, and deployments so you can select, implement, and maintain Microsoft Dynamics 365 for Finance and Operations, Enterprise edition. You will delve in-depth into the various phases of implementation: project management, analysis, configuration, data migration, design, development, using Power BI, machine learning, Cortana analytics for intelligence, testing, training, and finally deployment, support cycles, and upgrading. This book focuses on providing you with information about the product and the various concepts and tools, along with real-life examples from the field and guidance that will empower you to execute and implement Dynamics 365 for Finance and Operations, Enterprise edition.
Table of Contents (23 chapters)
Foreword
Title Page
Credits
Disclaimer
About the Authors
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Best practices in managing requirements


Based on our experiences, we have following recommendations in managing requirements:

  • A business transformation initiative is not a destination; it is rather a journey that must constantly evolve. Hence, one must always keep the requirements up to date. This includes key decisions made in a process/requirement, and it should be easily available in RTM.
  • Always capture the requirements in a SMART format. It should not have abstract details.
  • Never assume any requirement; always get it validated. Validation is the best when documented and signed off.
  • Requirements change over time and how you handle such changes decides the fate of the project. Scope management and change request should be the key levers for a project manager/CRP lead.
  • Requirement collection and documentation is a zero-sum game; both the parties (on the business and solution sides) should participate well and the RTM should be a living document that is easily accessible, simple to understand...