Muutke küpsiste eelistusi

E-raamat: Mastering Microsoft Dynamics 365 Implementations

3.00/5 (3 hinnangut Goodreads-ist)
  • Formaat: PDF+DRM
  • Ilmumisaeg: 19-Apr-2021
  • Kirjastus: Sybex Inc.,U.S.
  • Keel: eng
  • ISBN-13: 9781119789345
Teised raamatud teemal:
  • Formaat - PDF+DRM
  • Hind: 37,04 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
Mastering Microsoft Dynamics 365 ImplementationsSuurem pilt
  • Formaat: PDF+DRM
  • Ilmumisaeg: 19-Apr-2021
  • Kirjastus: Sybex Inc.,U.S.
  • Keel: eng
  • ISBN-13: 9781119789345
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

Confidently shepherd your organization’s implementation of Microsoft Dynamics 365 to a successful conclusion 

In Mastering Microsoft Dynamics 365 Implementations, accomplished executive, project manager, and author Eric Newell delivers a holistic, step-by-step reference to implementing Microsoft’s cloud-based ERP and CRM business applications. You’ll find the detailed and concrete instructions you need to take your implementation project all the way to the finish line, on-time, and on-budget. 

You’ll learn: 

  • The precise steps to take, in the correct order, to bring your Dynamics 365 implementation to life 
  • What to do before you begin the project, including identifying stakeholders and building your business case 
  • How to deal with a change management throughout the lifecycle of your project 
  • How to manage conference room pilots (CRPs) and what to expect during the sessions 

Perfect for CIOs, technology VPs, CFOs, Operations leaders, application directors, business analysts, ERP/CRM specialists, and project managers, Mastering Microsoft Dynamics 365 Implementations is an indispensable and practical reference for guiding your real-world Dynamics 365 implementation from planning to completion. 

Introduction xxvii
Chapter 1 Stages of an Implementation Overview
1(10)
What Is Microsoft Dynamics?
1(1)
The Client Journey
2(3)
Implementation Methodologies
5(1)
Waterfall and Sure Step
5(2)
Agile and Scrum
7(1)
Triple Constraints
8(1)
The Bottom Line
9(2)
Chapter 2 What to Do Before You Begin a Project
11(20)
Identify Your Project Team and Stakeholders
11(1)
Executive Sponsor
12(1)
Project Owner
12(1)
Business Process Owner(s)
13(1)
Project Manager
13(1)
Core Team and a Core Team Lead
14(1)
Subject Matter Experts
14(1)
IT Resources
15(2)
Time Commitment by Role
17(1)
Identify Your Processes in Scope
18(1)
Clean Up Your Data
19(1)
Identify Your "Master" Data
19(1)
Develop Naming Conventions
20(1)
Identify System Owners
20(1)
Find and Resolve Duplicates and Incorrect Data
20(1)
Define Your Success Metrics
21(1)
Possible Benefits
22(1)
Building Your Business Case and Securing Funding
23(1)
How Much Should an ERP Project Cost?
24(1)
Costs to Include in Your Calculations
24(1)
Capitalizing Costs
25(2)
Contingency
27(1)
Return on Investment (ROI)
27(1)
Gaining Approval
28(1)
The Bottom Line
29(2)
Chapter 3 Four Keys to Consider When Buying an ERP or CRM Solution
31(16)
Selection Process
31(1)
Selection Consultant
32(1)
Decision Maker
33(1)
The Four Keys
33(1)
Fit
34(1)
Platform
35(4)
Implementer
39(2)
Cost
41(3)
Building Your Scorecard
44(1)
The Bottom Line
45(2)
Chapter 4 How to Evaluate and Buy Business Application Software
47(10)
Buying Process Steps
47(1)
Qualification Stage
48(1)
Discovery and Demonstration Stage
49(2)
Selecting Your Vendor
51(3)
Leadership or Board Approval
54(1)
Moving Forward
54(1)
The Bottom Line
54(3)
Chapter 5 Organizing Your Team for Success and Project Governance
57(16)
RACI
57(1)
Your Project Team
58(1)
Your Partner's Implementation Team
59(1)
Executive Sponsor
60(1)
Engagement Manager
60(1)
Project Manager
60(1)
Solution Architect or Solution Delivery Manager
60(1)
Functional Consultant or Consultants
61(1)
Technical Consultant
61(1)
Development Lead and Developers
61(1)
Integration Architect
61(1)
Data Migration Specialist
62(1)
Project Governance
62(1)
Project Communication
62(1)
Resource Loading
62(4)
Project Schedule
66(1)
Document Repository
67(1)
Budget Tracking
68(1)
Change Requests
68(1)
Project Management Plan
68(1)
The Bottom Line
69(4)
Chapter 6 Sprints and Tools Needed to Run Your Project
73(14)
Definition of a Sprint
73(1)
Length of a Sprint
74(1)
Start and End of a Sprint
74(1)
Delivering Value in a Sprint
74(1)
Backlog
75(1)
Project Backlog
75(1)
Sprint Backlog
76(1)
Allocating Work to Team Members
76(1)
Sprint Success Rate
76(1)
Sprint Meetings
77(1)
Sprint Planning
77(1)
Sprint Review
77(1)
Sprint Retrospective
78(1)
Stand-up Meetings
78(1)
Work Definitions
79(1)
Epic
79(1)
Feature
79(1)
User Story
80(1)
Requirement
80(1)
Research Task
80(1)
Design Task
80(1)
Development Task
81(1)
Test Task
81(1)
Other Task
81(1)
Test Case
81(1)
Test
81(1)
Bug (Defect)
81(1)
Risk
81(1)
Issue
82(1)
Change Request
82(1)
Code and Changesets
82(1)
Azure DevOps
82(1)
DevOps Fields
82(1)
Progress Reporting
83(1)
Analytical Views
83(1)
The Bottom Line
84(3)
Chapter 7 Change Management Throughout Your Project
87(12)
Success Criteria
88(1)
Use of Satisfaction Surveys
89(1)
Nine Steps to Change Management
90(1)
Leadership Alignment
90(1)
Organization Evaluation
91(1)
Outline Your Business Process Change Steps
92(1)
Develop a System Vision that Provides Benefits to All Stakeholders
92(1)
Communicate Effectively
92(2)
Maximize the Team's Time in the New System
94(1)
Train Effectively
94(1)
Set Realistic Expectations for the System Just After Go-Live
94(1)
Support Your Team Members After Go-Live
95(1)
Steps to Business Process Change
95(1)
Importance of Adoption
96(1)
The Bottom Line
96(3)
Chapter 8 Organizing Your Business by Processes
99(10)
Common Language Businesses Speak
99(1)
Operations
100(1)
Sales
100(1)
Finance and Administration
100(1)
Standard Processes
100(2)
Process Hierarchy
102(1)
Process Category
102(1)
Process Group
103(1)
Process
103(1)
Sub-processes, Tasks, Activities, and Requirements
104(1)
Discovering Your Processes
104(1)
SIPOC
104(2)
Core Team Members
106(1)
Rounding Out Your Scope
106(1)
The Bottom Line
106(3)
Chapter 9 Independent Software Vendors--Filling Gaps and Managing Partnerships
109(12)
The Purpose of ISVs
109(1)
Hosting Providers
110(1)
Private Hosting
111(1)
SaaS-Style Hosting
111(1)
Industry ISVs
111(1)
Deciding If You Need an Industry ISV
112(1)
Functional ISVs
113(1)
Missing Functionality
113(1)
Advanced Features
113(1)
Missing Connector
113(1)
Automation
114(1)
Reporting Extensions
114(1)
Deciding If You Need a Functional ISV
114(1)
Working with ISVs
114(1)
Budgeting for ISV Solutions
115(1)
Implementation Partner or Customer Managed
115(1)
Buying the ISV License or Subscription
115(1)
Implementation of ISV Products
116(1)
Manage Your ISV Projects Closely
116(1)
Microsoft's AppSource Marketplace
117(1)
Product Listing
118(1)
Services Listing
118(1)
The Bottom Line V
119(2)
Chapter 10 Factors for a Successful Project Kickoff
121(12)
Pre-Kickoff Meeting Activities
121(1)
Checklist
121(3)
Expectations for the Meeting
124(1)
Outing
124(1)
Kickoff Meeting Content
124(1)
Executive Overview
125(1)
Introductions and Role Review
125(1)
Expectations for Team Members
126(1)
Project Management and Communication Plan
126(1)
Project Schedule
126(1)
Resources
126(1)
Navigation Overview [ Optional]
127(1)
Wrapping Up
127(1)
Executive Message
127(1)
Expectations for the Project Team
128(1)
Time Commitment
128(1)
Decision-Making
129(1)
Power of Positivity
129(1)
The Bottom Line
130(3)
Chapter 11 Designing the Software Collaboratively
133(12)
Joint Application Design Concept
133(1)
Joint Process Design and Other Design-Related Definitions
134(1)
What Is a Joint Process Design (JPD) Session?
134(2)
Happy Path
136(1)
"As-Is" vs. "To Be"
136(1)
Joint Process Design Iterations
137(1)
JPD1
137(2)
JPD2
139(1)
JPD3
140(1)
JPD4
140(1)
Keys to Successful JPDs
140(1)
JPD Output
141(1)
SIPOC
142(1)
The Bottom Line
143(2)
Chapter 12 Requirements Gathering and Staying "In the Box"
145(12)
Staying in the Box
145(1)
Customization vs. In-the-Box Examples
146(1)
Requirements
147(1)
Out-of-the-Box Fields as Requirements
147(1)
Requirements Link to Processes
148(1)
Functional vs. Non-functional Requirements
149(1)
Verifying Requirements
150(1)
Writing Good Requirements
150(1)
Requirements Tips
150(1)
Fit/Gap Analysis
151(1)
Fit/Gap Spreadsheet
152(1)
Trade-Offs
153(1)
The Cost of Customizations
154(1)
Cloud vs. On-Premise Software
155(1)
The Bottom Line
155(2)
Chapter 13 Conference Room Pilots
157(14)
The Purpose of a Conference Room Pilot
157(1)
How to Organize CRPs
158(1)
Common Elements of CRPs
159(1)
CRP Agenda
159(1)
Logistics
160(1)
Issues and Questions
160(1)
CRP Roles and Responsibilities
161(1)
Session Leader
161(1)
Helper/Expert
162(1)
Business Process Owner
162(1)
Users/Students
162(1)
Who Not to Invite
163(1)
CRP Place in the Overall Schedule
163(1)
Can You Do a CRP on One Process Group at the Same Time That You Do a JPD?
164(1)
Entrance Criteria
164(2)
CRP vs. UAT
166(1)
How They Are Similar
166(1)
How They Are Different
166(1)
What to Do Between CRP and the End of the Create Stage
167(1)
CRP Goals
168(1)
The Bottom Line
168(3)
Chapter 14 Dealing with Challenges Mid-Project
171(14)
Managing the Project Status
172(1)
Status Report
172(1)
Colors on a Status Report
173(2)
Managing Your Budget
175(2)
Project Pulse
177(1)
Risks and Issues
177(1)
Risk Register
178(1)
Issues vs. Bugs
179(1)
Common Project Challenges
179(4)
The Bottom Line
183(2)
Chapter 15 Customizations vs. Configurations and How You Manage Them
185(14)
Customizations vs. Configurations
185(1)
Customization V
185(1)
Configuration
186(1)
Integration
186(1)
Master Data
187(1)
Metadata
187(1)
Personalization
187(1)
Reference Data
187(1)
When to Customize vs. Configure
188(1)
Why Choose to Customize
188(1)
Tracking Configurations
188(1)
Configuration Tracker
189(1)
Gold Environment
189(1)
Lifecycle Services
189(1)
Functional Design Documents
190(1)
Overview
190(1)
Modification
190(1)
Testing
190(1)
Development Quotation
191(1)
Revision and Sign-off
191(1)
Updates
191(1)
Design Complete
191(1)
The Development Process
192(1)
Develop the Solution
192(1)
Unit Test
192(1)
Code Review
193(1)
Functional Testing (Part 1)
193(1)
Finishing Up
194(1)
After Code Complete
194(1)
Deploying the Code
194(1)
Functional Testing (Part 2)
194(1)
Preparing for CRP and UAT
195(1)
The Lifecycle of a Customization
195(1)
Managing These Tasks
195(1)
Wrap-Up
196(1)
The Bottom Line
197(2)
Chapter 16 Data Migration--Early and Often
199(16)
Data Migration Plan
200(1)
Proactive Cleaning
200(1)
Before the Kickoff
201(1)
Data Migration Tool
202(1)
Iterations
203(3)
Extract
206(1)
Finding the Data
206(1)
Extraction Tools
206(2)
Transform
208(1)
Mapping the Data
208(1)
Mapping Tools
208(1)
Transforming Mapped Data
209(1)
Load
210(1)
Order of Operation
210(1)
Load Time
210(1)
Validating the Data
210(1)
Technical Validation
211(1)
Business Validation
211(1)
Functional Validation
212(1)
Go-Live Iteration
212(1)
The Bottom Line
213(2)
Chapter 17 Environment Management and Deployments
215(14)
Types of Environments
216(1)
Developer Environments
216(1)
Build
217(1)
Test
217(1)
Sandbox
218(1)
Production
219(1)
Environment Plan
220(1)
Types of Releases
220(2)
Frequency of Code Moves
222(1)
Populating Configurations and Master Data
222(1)
Deploying Code
223(1)
Application Lifecycle Management
223(1)
Environment Flow Using DevOps
224(1)
Rollback
224(1)
Security
225(1)
Definitions
225(1)
How Best to Manage
226(1)
The Bottom Line
227(2)
Chapter 18 Testing
229(16)
Definitions
229(1)
Types of Testing
230(1)
Common Testing Terms
231(1)
Pre-Deploy Stage Activities
232(1)
Testing Strategy
232(1)
Unit Test and Regression Tests
233(1)
Developing Test Cases
234(1)
UAT Entrance Criteria
235(1)
UAT Exit Criteria
236(1)
UAT Sessions
236(1)
Purpose
236(1)
Additional Benefits of UAT Sessions
237(1)
UAT Roles and Responsibilities
237(1)
Executing Your Test Plans
238(1)
Tips for the Sessions S
239(1)
Post UAT Testing
240(1)
Issues List
241(1)
Process Sign-Offs
241(1)
Scenario Recaps
241(1)
The Bottom Line
242(3)
Chapter 19 Training for All
245(16)
Learning During Interactive Sessions
246(1)
JPDs
246(1)
CRPs
246(1)
UAT
247(1)
Learning Modalities
247(1)
In-Person, Classroom Style
248(1)
Remote, Synchronous Training
249(2)
Asynchronous
251(1)
Building Your Training Content
251(1)
End User Training Content
251(1)
Product Help Content
252(1)
Microsoft Learn
253(1)
Recording Sessions
253(1)
Task Recorder
253(1)
How Much to Document
254(1)
How to Manage and Distribute Your Content
254(1)
Learning Management Systems
255(1)
Building Your End User Training Schedule
255(1)
Pre-Training Learning
256(1)
Train the Trainer
256(1)
Synchronous Sessions
257(1)
Advanced Concepts
257(1)
Testing Users' Knowledge
257(1)
Office Hours
258(1)
The Bottom Line
259(2)
Chapter 20 Going Live
261(14)
Go-Live Criteria
261(1)
Cutover Plan
262(1)
Bug Criteria
262(1)
Data Migration and Security Criteria
263(1)
Support Readiness
264(1)
Training Review
264(1)
Communication Plan
265(1)
Go-Live Scorecard
265(1)
Mock Cutover and Final Week Activities
266(1)
Disaster Recovery
267(1)
System Setup Before Cutover
267(1)
Go/No-Go Meetings
268(1)
When to Have It
268(1)
Voting Criteria
268(1)
Meeting Agenda
269(1)
Order and Outcome of the Votes
269(1)
Next Steps
270(1)
Live Cutover
270(1)
Impact of the Cutover Start Timing
271(1)
Completing Cutover Activities
271(1)
Rollback Plan
272(1)
Acknowledge the Team
272(1)
The Bottom Line
272(3)
Chapter 21 Hypercare
275(16)
Go-Live Support
275(1)
Day 1
276(1)
Week 1
276(1)
Project Change Champions
277(1)
Prioritizing Issues
277(1)
Weeks 2-4
278(1)
First Month End
278(1)
Duration of Hypercare
279(1)
Role of HelpDesk
279(1)
Sample SLA
280(1)
Project Team Support
280(1)
Support Levels
281(2)
Refer Users to Training
283(1)
Making the Transition to HelpDesk Later
283(1)
Post Go-Live Releases
284(1)
Planning for Future Releases
285(1)
Hotfix Release
285(1)
Scheduled Releases
286(1)
Project Team Transition
287(1)
Rolling Off the Project Team
287(1)
Documentation
288(1)
Expectations of Support
288(1)
After the Transition
289(1)
The Bottom Line
289(2)
Chapter 22 Support and Enhance Your Project
291(16)
Support After Hypercare
291(1)
Extending the Transition from Consulting to Support
292(1)
Engaging Your Partner for Support
292(2)
Microsoft and ISV Support Plans
294(1)
After Action Review
295(1)
Who to Invite
295(1)
How to Run the Meeting
296(1)
What to Do with the Feedback
297(1)
Ongoing Releases
297(68)
Microsoft Dynamics 365 Release Cadence
297(1)
Release Testing
297(1)
When to Schedule Your Releases
298(1)
What to Include in Releases
299(1)
Future Enhancements
299(1)
New Functionality
299(1)
Usability
300(1)
Guardrails
301(1)
Business Intelligence
301(1)
Incorporating Dynamics Data into Your Daily Business
302(1)
Integrations
302(1)
Machine Learning and Artificial Intelligence
302(1)
Calculating Return on Investment
303(1)
ROI Checkpoints
304(1)
The Bottom Line
305(2)
Chapter 23 Bringing It All Together
307(10)
Align Stage
307(1)
Define Stage
308(3)
Create Stage
311(2)
Deploy Stage
313(1)
Empower Stage
314(1)
Additional Resources
315(1)
The Bottom Line
315(2)
Appendix The Bottom Line
317(36)
Chapter 1 Stages of an Implementation Overview
317(1)
Chapter 2 What to Do Before You Begin a Project
318(2)
Chapter 3 Four Keys to Consider When Buying an ERP or CRM Solution
320(2)
Chapter 4 How to Evaluate and Buy Business Application Software
322(1)
Chapter 5 Organizing Your Team for Success and Project Governance
323(2)
Chapter 6 Sprints and Tools Needed to Run Your Project
325(1)
Chapter 7 Change Management Throughout Your Project
326(2)
Chapter 8 Organizing Your Business by Processes
328(1)
Chapter 9 Independent Software Vendors--Filling Gaps and Managing Partnerships
329(2)
Chapter 10 Factors for a Successful Project Kickoff
331(1)
Chapter 11 Designing the Software Collaboratively
332(2)
Chapter 12 Requirements Gathering and Staying "In the Box"
334(1)
Chapter 13 Conference Room Pilots
335(2)
Chapter 14 Dealing with Challenges Mid-Project
337(1)
Chapter 15 Customizations vs. Configurations and How You Manage Them
338(2)
Chapter 16 Data Migration--Early and Often
340(1)
Chapter 17 Environment Management and Deployments
341(2)
Chapter 18 Testing
343(1)
Chapter 19 Training for All
344(2)
Chapter 20 Going Live
346(1)
Chapter 21 Hypercare
347(2)
Chapter 22 Support and Enhance Your Project
349(1)
Chapter 23 Bringing It All Together
350(3)
Glossary 353(16)
Index 369
Eric Newell is the Co-Founder and CEO of Stoneridge Software, a Microsoft Gold Partner, focused on Dynamics. Prior to founding Stoneridge, he worked at Microsoft for 13 years in Dynamics-related roles including support engineer, IT lead for support systems, Technical Account Manager and as a Premier Field Engineering team leader. He frequently presents on topics related to implementing Microsoft Dynamics 365, and has spoken at Microsoft conferences over a dozen times. He has served as a project management trainer at Microsoft as well as local universities.
Lisainfo e-raamatute kohta Lisainfo e-raamatute kohta
Püsilink: https://www.kriso.ee/db/97811197893452e.html
Märksõnad: