This column is the final installment of the five fundamental phases of a project plan to build a meta data repository. This month we will complete the rollout phase.

The rollout phase is the final step of the meta data repository development effort. Three key tasks occur during this phase (see Figure 1). First, and most importantly, the repository is rolled into production and is accessible to both its technical and business users (Task ID 5.1). Second, the meta data repository team, the project champion and key executive management conduct a post-implementation review to compare the meta data repository with the objectives of the original project scope document (Task ID 5.2). If the live repository matches the scope document and any change requests that were approved during the development phase, you should have a very successful project on your hands (assuming you did a good job on your scope document). If there are differences between the scope document and the repository, the review should reveal where and how the discrepancies occurred and determine what positive/negative effects (if any) they had on the ultimate success of the project. Of course, the results of the review should be thoroughly documented; and, if possible, the results of the project quantified. This information is extremely helpful in obtaining funds for subsequent project releases. Finally, this is the time to begin planning for the next release of the repository project using the original project scope document and the meta data integration architecture document as the foundation for the second release.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access