This document provides an overview of key considerations for ECM project management. It recommends starting projects with established methodologies and outlines important initial steps like defining stakeholders, communications plans, and infrastructure needs. It emphasizes the importance of information architecture, governance, and keeping solutions simple. The document stresses the need for thorough planning, breaking large projects into manageable pieces, and underpromising and overdelivering on objectives.

1. ECM Project Management Basics David Champeau IBM FileNet Certified Professional AIIM ECM Master AIIM BPM Pracitioner AIIM IOA Practioner

2. ECM Projects Start with one or more basic methodologies depending on the size and scope of the project Zachman Frameworks MIKE2 PMBOK

3. Sequence of ECM Projects

4. Project Infrastructure Stakeholders Communications Plan Resource Plan Geography Priorities Artifact Management

5. Dual Tracks Information Architecture Governance Taxonomy Business Processes Records Security Technology Architecture Infrastructure Operations Integration

6. Architectures Application Infrastructure Network ECM Platform Business Data Operations Support Geography

7. 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

8. 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

9. Undersell, Overdeliver If this is all new, start small Use prototypes for testing the integration points automating business processes experimenting with user interfaces

10. 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

11. 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

12. 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