From MIKE2 Methodology
Proposed Changes to Overall Task List
Possible Changes related to EPM Solution Offering
The following points relate to the relevance of the activity list to EPM (per Nina Afshar, 11/15/2007)
Phase 1
The activities and tasks list would be relevant to EPM with the following changes/considerations: Activities 1:3 and 1:5 - we would need to remove the words 'for Information Management' as these activities and tasks would relevant not only for IM, but to set the direction of what the business wants to accomplish relative to managing its performance, of which the information to do that is one aspect. Suggest we name 1:3 Overall Business Strategy and 1:5 Future State Vision. Also make the change in tasks 1.1.5 and 1.3.6 Additionally, the IM quickscan would need some additional questions/section to be useful on an EPM initiative. We have been developing a separate quickscan for EPM, need to discuss how to integrate into the IM in order to minize changes to the activity list, etc
--Sean.mcclowry 09:37, 16 November 2007 (EST) MIKE2.0 is fundamentally providing Information Management competency (starting with an Information Management strategy) based on a business strategy.
- --Sean.mcclowry 09:37, 16 November 2007 (EST) * If the EPM QuickScan is often relevance to a number of other solutions it may make sense to add it as a new task within the Organisational QuickScan activity, otherwise it should be a Supporting Asset of this specific EPM solution.
Phase 2
Many of these activities and tasks are relevant; although not every EPM initiative has a software selection or new technology aspect, we would evaluate the technology environment and existing information sources, so will identify with those in the article text.
- --Sean.mcclowry 09:37, 16 November 2007 (EST) The Usage Model will always be a best guess to a degree with discretion left to the user of the methodology
Phase 3
Suggested changing the name of the phase from Information Management Roadmap and Foundational Activities to Roadmap and Foundational Activities; same issue as in Phase 1; again, most tasks relevant when new software is in scope, otherwise a portion of the tasks are relevant. Most relevant around defining a common data model and common views of data, etc.
- --Sean.mcclowry 09:37, 16 November 2007 (EST) This phase of MIKE2.0 is specific to an IM worksteams and would work in conjunction with others streams around strategy, process, infrastructure and application development.
Phase 4 and 5
No changes (so far)