ECM Project Management Basics

2,917 views
2,714 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,917
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
101
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

ECM Project Management Basics

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

×