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

Key decision log


Based on our experience, one of the top reasons causes a lot of issues in project delivery is the availability and usage of a key decision log. This is one binding matrix that can streamline communications and expectations, and bring in a lot of delivery efficiency.

Once the solution blueprint and the solution design document are prepared, people seldom go back to the original requirement, that is, the Business Requirement Document (BRD), situation, use cases, and exceptions understand, or people seldom recall what had happened and triggered a particular approach. Hence, it is crucial to always maintain a key decision log that is easily accessible to all the relevant project stakeholders.

Any decision that could alter the course of the project and impact its objectives must be documented. Also, the circumstances of taking the decision should also be noted, as this would complete the entire story for the decision. A decision may impact one or more requirements, and hence...