ECM Project Management Basics
-
Upload
david-champeau -
Category
Technology
-
view
2.161 -
download
2
description
Transcript of ECM Project Management Basics
ECM Project Management Basics
David ChampeauIBM FileNet Certified Professional
AIIM ECM MasterAIIM BPM Pracitioner
AIIM IOA Practioner
ECM Projects
Start with one or more basic methodologies depending on the size and scope of the project› Zachman Frameworks› MIKE2› PMBOK
Sequence of ECM Projects
•Desired Future State of Organization
•Provides Inspiration
Vision•Program
Level•Informati
on Governance
•Enterprise Architecture
Strategy
•Project level
•On-boarding
•Consistent with Strategy
•Each Project Should Add to the Strategy
Tactics
Project Infrastructure
Stakeholders Communications Plan Resource Plan Geography Priorities Artifact Management
Dual Tracks
Information› Architecture› Governance› Taxonomy› Business Processes› Records› Security
Technology› Architecture› Infrastructure› Operations› Integration
Architectures
Application Infrastructure Network ECM Platform Business Data Operations Support Geography
Situational Analysis
This will determine the next steps› New ECM program
Start from the beginning Leave room for lots and lots of planning
› New project in existing program Same style as other tactical projects or Something new What does it add Impact on infrastructure
Eating an Elephant
Organize the project into the high-level categories or tracks
Break each down multiple times› Get to manageable pieces
Determine dependencies› Begin to see the timeline
Gauge level of effort› Use one of numerous algorithms
Undersell, Overdeliver
If this is all new, start small Use prototypes for
› testing the integration points› automating business processes› experimenting with user interfaces
Plan and Plan Again
Whiteboards help flush out ideas, identify the tough spots
Planning does not have to lead into analysis paralysis
Each project needs someone to drive it forward› This is often overlooked› Someone has to understand how all the
pieces fit together
Keep the Solution Simple
Do not “code for the exception”, “code for the rule”› Keep it at 80-20› Dump the exceptions to the side and let
someone manually sort them out› This is a project killer
Keep the Solution Simple
Try to use out-of-the-box› Lots of good stuff coming OOTB these days› Integration points require customization
Sell the users on “simple first”› Most requirements delivered are rarely or
never used