logo for information-management-architect.com
leftimage for information-management-architect.com

Information Management Methodology

Improve roadmap planning process with David Bowman’s guidelines for information management methodology assessment

This site is designed for Information Technology professionals who need to improve service and require guidance and direction to help teams consistently produce error free results.

It provides a checklist of information management guidelines for information management methodology assessment.

What is Methodology?

Methodology covers a wide range of processes, including development and change management methodologies.  It governs the development process, including both custom development and package implementation, and facilitates the transition into production operations. 

Information Management Methodology Assessment Process

Should determine what, if any, changes are required to ensure that  information management methodology can support solution development, quality assurance and change management by comparing the current data warehouse management situation with the following checklist of information management guidelines.

Solution Development Methodology
  • Should be based on data warehouse project management best practices;
  • Should define roles, responsibilities, tasks and deliverables;
  • Should provide deliverable templates;
  • Should be SOX-compliant;
  • Should include specialized data architecture, data integration and business intelligence components;
  • Should include a data profiling process; and
  • Should have a group responsible for ensuring adherence to methodology standards and best practices.
Quality Assurance Methodology
  • Should be based on software testing best practices;
  • Should include an software quality assurance plan to define roles, responsibilities, tasks and deliverables;
  • Should include a test plan for unit, system, integration, quality assurance, user and release testing;
  • Should include a test data strategy; and
  • Should ensure separate environments for development, test and production.
Release Management (Transition to Production)
  • Should be based on release management best practices;
  • Should include a release plan to define roles, responsibilities, tasks and deliverables;
  • Should include a release test plan;
  • Should include robust, well-understood production operations procedures in place;
  • Should ensure that transition to production is part of most project plans; and
  • Should ensure that all systems follow software testing best practices before deployment to production.
Change Management
  • Should be based on an approved change management methodology;
  • Should include a release plan to define roles, responsibilities, tasks and deliverables;
  • Should include a release test plan;
  • Should include robust, well-understood production operations procedures;
  • Should ensure that transition to production is part of most project plans;
  • Should ensure that all systems follow release management best practices before deployment to production;
  • Should have well defined change management sign-off on changes before they go into production; and
  • Should include a separation of roles between development, testing and production.
Key Roles and Responsibiltes

Solution Delivery Methodology
  • Should define program manager roles and responsibilities;Should determine the organizational readiness for data governance strategy by comparing the current situation with a checklist of information management guidelines.Should determine the organizational readiness for data governance strategy by comparing the current situation with a checklist of information management guidelines.
  • Should define project manager roles and responsibilities.
  • Should define solution architect roles and responsibilities;
  • Should define data architect roles and responsibilities;
  • Should define data integration architect roles and responsibilities; and
  • Should define business intelligence architect roles and responsibilities.
Quality Assurance Process
  • Should define test manager roles and responsibilities;
  • Should define quality assurance roles and responsibilities; and
  • Should define defect manager roles and responsibilities.
Change Management Methodology
  • Should define release manager roles and responsibilities; and
  • Should define change manager roles and responsibilities
Summary...

Methodology covers a wide range of processes, including development and change management methodologies.  It governs the development process, including both custom development and package implementation, and facilitates the transition into production operations.

This site provide a checklist of information management guidelines for information management methodology assessment.