Book Image

Maximize Your Investment: 10 Key Strategies for Effective Packaged Software Implementations

By : Grady Brett Beaubouef
Book Image

Maximize Your Investment: 10 Key Strategies for Effective Packaged Software Implementations

By: Grady Brett Beaubouef

Overview of this book

Using packaged software for Customer Relationship Management or Enterprise Resource Planning is often seen as a sure-fire way to reduce costs, refocus scarce resources, and increase returns on investment. However, research shows that the majority of packaged or Commercial Off-The-Shelf (COTS) implementations fail to provide this value due to the implementation approach taken. Authored by Grady Brett Beaubouef, who has over fifteen years of packaged software implementation experience, this book will help you define an effective implementation strategy for your packaged software investment. The book focuses on Commercial Off-The-Shelf (COTS) implementations, and helps you to successfully implement packaged software. Using a step-by-step approach, it begins with an assessment of the limitations of current implementation methods for packaged software. It then helps you to analyze your requirements and offers 10 must-know principles gleaned from real-world packaged software implementations. These 10 principles cover how to maximize enhancements and minimize customizations, focus on business results, and negotiate for success, and so on. You will learn how to best leverage these principles as part of your implementation. As you progress through the book, you will learn how to put packaged software into action with forethought, planning, and proper execution. Doing so will lead to reductions in implementation costs, customizations, and development time.
Table of Contents (19 chapters)
Maximize Your Investment: 10 Key Strategies for Effective Packaged Software Implementations
Credits
About the Author
Acknowledgement
About the Reviewers
Preface
Summary of Challenges

Who is covering business processes?


Traditional packaged software implementation approaches would try to cover all five levels of the solution by the following roles:

  • Project manager

  • Functional lead

  • Architect lead

  • Technical lead

The project manager and the functional lead(s) have to be able to represent, evaluate, and communicate across all five levels (i.e., solution, business process, software product, product feature set, product feature) concurrently. This is quite a load to carry by two roles whose primary function is to focus and operate below the business process level. The technical lead and architect lead focus on the technology infrastructure across the business solution. These roles might address the technology conflicts but may not be totally effective in identifying business functional requirements and configuration conflicts. Also, consider the natural tendencies to become only focused on one's individual task assignments and responsibilities during the implementation.

As we move...