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

Chapter 5. Perform Business Solution Modeling

Requirements validation is usually too little and too late.

Historically, the majority of packaged business software implementation methodologies are variations on the waterfall software development lifecycle. The waterfall model is a sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of planning, requirements, design, development, testing, and go-live. One phase is completed before moving on to the next implementation phase.

A key challenge when using the waterfall approach is requirements management. Simply stated, requirements management is not only requirements gathering but also requirements validation. Missing a requirement or not understanding a requirement's impact during the Requirements phase can be a costly mistake because validation is not completed until the end of the implementation cycle (Testing). This late finding will result in additional rework...