This column is the fourth installment in a walk-through of the key tasks in each of the five fundamental phases of a project plan to build a meta data repository: orientation, feasibility, design, construction and rollout. In last month's column we walked through Tasks 3.1 and 3.2 of the design phase for a meta data repository project. This month we will complete the design phase (see Figure 1).
The back-end program specifications and the repository's front-end report specifications are also constructed during the design phase. While the process for capturing detailed designs has been around for a long time and is well understood, I want to share a couple of techniques to reduce the likelihood of extending this process longer than necessary and to avoid scope creep. Always bring a copy of the project scope document to each design session with the end users to ensure that all design work relates directly to the business and technical drivers listed in the project scope document. When the design documents are complete, obtain signature approval from the end users who have attended the design sessions.
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
Already have an account? Log In
Don't have an account? Register for Free Unlimited Access