I developed this guide to share with others the approach I use to gather, document, and manage requirements for a Master Data Management solution, with the hope that they may be able to leverage the approach to formulate their approach. If you are working on requirements for a Master Data Management solution and looking for thoughts on how to approach requirements, you may be able to leverage some of the information contained in the Smartlist or the guide. Take a look!! This Smartlist brings together the content created to support the guide.
Requirements activities are similar, regardless of the type of solution. What differs is the approach to those activities, the sequence and emphasis of specific activities, and the content of the work products.
Even with an agile approach, it is important to take time up front to establish the requirements foundation or blueprint for a complex data integration project.
Some of the keys to successful MDM requirements are also the ways an MDM requirements approach differs from other types of solutions.
A strong requirements foundation, along with a structure to ensure traceability, is essential for a successful project.
Visual Requirements can be used throughout the project lifecycle to complement written requirements and ensure all stakeholders have a clear and consistent understanding and concur with proposed requirements.
Good article by Scott Taylor... Master Data can strengthen strategy, drive innovation, and improve customer engagement; however realize that it's a journey.
Great article by David Nicholson-Jones on how a Data Vault (Analytical Data Warehouse) and Master Data Management solution (Operational Data Store) can complement each other.
Nice video summary of data modeling by Steve Hoberman.
Nice article by Matthew Leach on the importance of getting requirements right. 75% of project failures ... can be traced to ... a lack of business analysis to properly align the IT project with the needs of the company and its customers
Good article by Karl Wiegers and Joy Beatty. Discusses how a developer needs to know the same information to be able to correctly implement the right functionality regardless of the life cycle being used.
Great article by Mark Lines and Scott Ambler which discusses the importance of investing time prior to beginning construction to get going in the right direction.
Nice article by Sven van der Zee emphasizing the importance of Requirements in Agile. Thorough requirements expertise is necessary to bring the essence of requirements engineering into agile teams.
Anyone with solid data management experience will read this with gratitude. I've been working on a methodology closely related to MDM and needed a definitive practical guide for MDM implementation. It was a tall order, as practical advice is usually limited to strategy and scope, however this book delivered in spades. There are detailed examples throughout the book, and you can practically 'paint-by-numbers' when it comes to a MDM implementation from scratch. I can't recommend this book highly enough, for in-house managers, consultant and technical MDM implementers who wish to leap-frog years of trial and error to base their understanding on something concrete and tested. I don't claim MDM experience for my evaluation of these materials, but years of IT implementation validate the logical progress of the material development that evolves throughout the book's presentation.