Monday, December 06, 2010

Store and share more project metadata

Many professional services companies list their clients and projects on their website for marketing purposes. For example:

  • Painless Programming: http://www.painlessprogramming.com/samples . Ben does a good job with classifying projects by Languages, Frameworks, Techniques, Servers, and Operating Systems. This is a very IT/technology-centered view and doesn't really get at business problems, objectives or similar.
  • Extended Results: http://www.extendedresults.com/portfolio/default.aspx. They classify their projects by category (SharePoint, Scorecard, Reporting, Custom Dev, Data Warehousing) but not by business process / need either.
  • Cap Gemini: http://www.capgemini.com/. Classified by Industry and Business Need…now we're getting somewhere.

What about bridging the gap between the worlds of business and technology. Let's be somewhere in between. I'd classify projects by:

  • Geo Locations – Show where you did the work and/or what regions were impacted. Display this on a navigable map.
  • Links – Tie your marketing site into Delicious.com, SharePoint or similar and list links that the project team used as references. This is useful for the community and for knowledge management.
  • People - Who worked on the project? Keep resumes…
  • APQC Processes – See the APQC Process Classification Framework. Use this to describe what type of work you did. Describe which APQC business processes were impacted by the change from the project. Show what you did by highlighting parts of this graphic.
    • KPIs – Which Key Performance Indicators did you impact / affect?
  • Technologies - Which technologies (and versions) were used on the project? Use this to keep track of what technology experience you have specifically.
  • Resource Types / Roles - Which roles were critical to achieving the outcomes? BAs, PMs, Developers, Testers? Also provide a general description of the roles that you typically use for each project.

No comments: