Client Artifacts Deliverable Template

From MIKE2 Methodology

The gathering of existing client artifacts is a critical part of a successful project as the current-state shapes what can be done in the future.

Examples

Examples of Client Artifacts are shown below:

Client Artifacts typically collected for Information Strategy

Example Client Artifacts to be gathered for a information management strategy project would include:

1. A summary of the overall Business Strategy as it relates to the project
2. Subject Matter Experts that can talk to each aspect of in-scope system functionality (at a high level)
3. A documented set of high-level, current-state business processes that are in scope for this project
4. A current-state architecture model of in-scope systems that shows source systems, data flows, sourcing frequencies and technologies
5. Strategic drivers for the project: Change Drivers, Success Measures, Key Performance Indicators
6. A list of major issues that have taken place over the last few years with the current environment (data quality, data loads, system performance, system failures)
7. Documented risks or issues (that may or may not have occurred) with the current-state environment or projected future-state environment
8. Vendor shortlist options, e.g. preferred vendors or excluded vendors
9. An overall programme timeline for implementation