Proven Leading Practices for Master Data Management Operations
Master Data Management Best Practices Guide
Learn MoreSchedule Time to Plan Developer Activities to Improve the Quality of Database Development
Best Practice (Good)
Set aside enough time to address data and process requirements before developing (i.e., coding) any requested software. Enough time and effort should be spent planning developer activities to not only allow software developers to understand how the company will use data, but to also ensure that the database itself is properly developed and capable of incorporating the future data needs of the company. To that end, use meetings with Enterprise Architects, IT managers and other management staff to fully discuss and understand both the technical specifications required and the business processes that the database will be supporting.
Typical Practice (Bad)
Forego data modeling and database creation planning, and instead, start the coding process in an effort to meet deadlines. Use checklists to track any shortcuts taken and ensure that they are fixed before database completion.
Benefits:
Software developers often begin coding and creating databases without taking into account how the data will be used, instead choosing to focus on rushing through the development process in order to meet deadlines. This not only causes a high potential for errors (especially when developers take shortcuts), but also potentially drives the database to become misaligned with the needs of the company. Scheduling time to plan developer activities, on the other hand, reduces the need to rework, replace or scrap constructed databases by allowing developers to have enough time to address any issues that pop up. Attending meetings with Enterprise Architects, IT managers and other management staff during the planning phase, furthermore, ensures that software developers are able to consider the future data needs of the database during its creation.
Build a Data Steward Team of SMEs from All Business Areas to Ensure Company-Wide Database Policy Compliance
Best Practice (Good)
Identify and build a data steward team that includes subject matter experts from all business areas so as to ensure effective company-wide control and use of data assets. Build an incentive-based reward system (financial, formal and informal recognition, etc.) that links performance to participation so as to re-enforce company database policy compliance and gain more sustained commitment in participation from all relevant parties.
Typical Practice (Bad)
Select and train employees to become data stewards to control the storage and use of data within a company's database. Training these employees, furthermore, ensures that they are aware of the intricacies behind the company's data policies and procedures. Ensure that there is a clear line of communication between employees and managers, should a topic appear that the data stewards are unsure of.
Benefits:
Since business units often vary significantly on how they allocate their resources, taking time to identify and build a data steward team of subject matter experts from all business areas ensures effective communication and compliance with company policy and procedures that focus on the structure and flow of data within a company's database. Furthermore, by providing data stewards with incentives (financial, formal and informal recognition, etc.) to continue their participation, not only will enthusiasm for the position be sustained, but it will also promote desired cultural changes within the organization through active engagement with all other business area employees.
Develop a Communication Plan to Encourage Business Alignment and Ensure Business Stakeholder Sponsorship
Best Practice (Good)
Use various mediums of communication (intranet, report handouts, meetings, on-on-ones, etc.) to engage business stakeholders (departmental managers, C-suite level managers, etc.) and encourage collaboration on the applications, processes or business capabilities that directly affect them. Ensure that the Enterprise Architecture (EA) Group analyzes the needs of each stakeholder group before developing a communication plan to specifically address those needs and align the business goals of the company and the EA Group.
Typical Practice (Bad)
Develop a communication plan, focusing on report handouts, that describes, in detail, how the EA Group's business agendas align with those of the business as a whole, including the justifications behind the architecture and technologies used. This not only provides the business stakeholders with enough information to make a decision, but it also ensures that the company's needs are being met.
Benefits:
Without an effective communication plan (these plans must be clear, concise and highly focused on resolving the needs of the business group and the company as a whole), the EA Group will find themselves hard-pressed in convincing business stakeholders to support the agendas that are put forth. To ensure business stakeholder sponsorships, EA communications should include the scope and objectives of the architectures being built, the decisions that are made (with justifications) and the benefits that are derived from the EA process. An effective action plan, focused on each business group's needs, with timelines and responsibilities should also be identified and presented. A feedback process that engages the business stakeholders should, furthermore, be put in place to ensure that the communication plan is effective. In the end, the quicker the EA Group can get stakeholders on board the business strategies put forth, the faster the EA Group can move through the strategic planning process and into plan execution.