- Microsoft Dynamics AX Implementation Guide
- Table of Contents
- Microsoft Dynamics AX Implementation Guide
- Credits
- About the Author
- Acknowledgments
- About the Author
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Preparing for a Great Start
- 2. Getting into the Details Early
- 3. Infrastructure Planning and Design
- The Dynamics AX components and architecture
- Planning the system topology
- Cloud deployment
- Industry best practices and recommendations
- Summary
- 4. Integration Planning and Design
- Integration planning
- Integration technologies
- Integration design and development
- Best practices and recommendations
- Summary
- 5. Data Migration – Scoping through Delivery
- Managing scope – simplifying data migration through rightsizing the scope
- The design and development phase
- Data mapping and transformation
- Planning the data migration
- Selecting the tools for data migration
- The Data Import/Export Framework
- Data migration execution tips
- Initial templates for business
- Extracting source data into SQL tables
- Never rename/repurpose fields
- Considering premigration steps
- Considering postmigration steps
- Changing SQL to simple recovery mode
- Multithreading and max DOP
- Index and statistics maintenance
- Disabling the AX logging
- Considering SQL updates on migrated data
- The SQL import – through caution and expertise
- Managing configurations
- Configuration management simplified with DIXF
- Reviewing and deciding on the configuration
- Data validation
- A classic example of a data migration issue in projects
- Summary
- 6. Reporting and BI
- Gathering BI and reporting requirements
- Knowing about reporting tools
- Mapping reports and identifying gaps
- The custom report development
- Summary
- 7. Functional and Technical Design
- 8. Configuration Management
- Configuration planning
- Collecting the configuration data
- Configuration tools
- Configuration data management
- Summary
- 9. Building Customizations
- Getting ready for development
- The development process
- Conceptualization
- Data design
- The business logic
- The user interface
- Security
- Coding best practices
- The Application Lifecycle Management (ALM)
- Summary
- 10. Performance Tuning
- 11. Testing and Training
- 12. Go-live Planning
- 13. Post Go-live
- Initial stabilization
- Proactive preparation – what's coming
- Post-implementation review
- Why post-implementation review?
- Key factors to get the most out of PIR
- Preparing for PIR
- Pain points from experience
- Post-implementation review – an AX 2012 customer
- Current state – key challenges
- The unused potential of Dynamics AX
- Improvement opportunities – processes and systems
- New features from the next release
- Summary
- 14. Upgrade
- When to upgrade
- Upgrading options
- The Dynamics AX upgrade process
- Summary
- Index
With Agile becoming more and more popular, many customers have adopted it as it allows you to react quickly to changing business needs. In my experience, I have seen Agile ERP projects being more successful than the waterfall method. Every customer has his/her own version of Agile though. Understand the customer's current process, and tweak it to the version that would work for the ERP project. For example, if they are creating all the tasks on the board and physically writing them down, you may want to switch to the electronic format for better collaboration with remote teams.
The following are some recommendations if you plan on implementing Dynamics AX via an Agile methodology:
- Plan the tasks 4-6 weeks ahead, and build a backlog of things to be done after the requirements or Gap/Fit sign off.
- It is very important to have unified tools and processes across the board.
- Generally, there is misconception about Agile; Agile does not mean no documentation. You need to enforce using standard templates for all the deliverables (for example, functional design, technical design, and so on), and do not take any shortcuts using the Agile methodology as an excuse.
- Schedule frequent reviews (demos) with the business owners for each sprint cycle.
- Break the implementation team into smaller scrum teams by relevant areas. You would have cross-functional dependencies across the teams.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.