Typical implementation steps for an SAP MDG project.

A project usually starts with a blueprinting phase.
In the case of MDG, I would recommend starting the project with a "initial configuration" phase. This is particularly true in cases where SAP delivers an out-of-box solution for the master data domain. For instance, if customer is planning a MDG implementation for Material, start with activating the out of box solution with the default data model and simple 2-step approval workflow in a sandbox environment.

Let me elaborate.
Depending on the Master Data that we plan to maintain with MDG, SAP may already provide an out of the box solution. Few such data models are Material, Supplier, Customer etc. But the Data Model, workflow process, rules and validation, UI of these solutions may not fit the customer needs. So the suggested approach is the following:
i. First implement the out-of-box solution. Activate the supplied BC Sets and follow through with rest of the configuration steps.
ii. Once this basic solution is implemented, demo the functionality and train the super users. A baseline solutions is a great place to start the blueprinting. Let business owners use the features

iii. This would let the stake holders compare and contrast their existing solution and processes with MDG.
iv. With this initial exposure achieved, initiate the blueprinting phase. The primary area of requirement gathering are :
          a. Data Model changes.
          b. Process definition (Users, Steps, Actions) to address the primary flow and fallout conditions.
          c. User Interface definition
          d. Validations/Checks and Derivations.
Remember to scope the project across phases.

You can reach me at SAPMDGCurious@gmail.com if you wish to discuss about MDG project, skills needed for MDG implementation, known challenges and risks.

View my images for a visual tour of MDG screens.