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

Requirement segmentation and ownership


During requirement gathering, an important aspect is to classify it. Classification plays a role in the lifecycle of a requirement and how it gets addressed downstream. An accurate classification of requirements helps project stakeholders to use it adeptly and see it from various sides.

We recommend that you use the following techniques for classifying requirements and tailor-fit them based on the size, complexity, and business situation of your Dynamics 365 project:

  • Ask the question WHAT:
    • What kind of requirement is this? For example, functional process oriented, non-functional security, decision making, and so on      
    • Impact on business (must-have or good to have)
  • Ask the question WHY:
    • This classification is oriented to weigh the importance of a requirement
    • Recommended usage values: must-have, good to have
  • Ask the question WHEN:
    • This classification is oriented to know when the requirement is needed so that it can be taken for solution and deployment...