What are the Characteristics of a Project Management Information System? Saving Changes...
Sort By:
Mark Price PerryBusiness Driven PMO Evangelist| BOT InternationalOrlando, Fl, United States
Many folks view the term Project Management Information System (PMIS) and what has been done in the past terms of creating a PMIS as obsolete and ineffective. About a decade ago, the PMO Architecture approach emerged. In this approach, and at a very high level, there are three key components; (1) a project management system of some kind such as Microsoft Project Server or any of the other fine vendor tools, (2) a platform for collaboration and document management such as Microsoft SharePoint or any of the other fine vendor platforms, and (3) PMO content asset framework such as Processes On Demand or any of the other fine frameworks of PMO content whether acquired and customized for fitness of use or developed from scratch. PMO Content Assets, a highly important component of the PMO Architecture represents all of the non-application kinds of PMO content that exists and is needed such as processes, policies, guidance, templates, SME tips and self-learning resources, executive dashboards, and the like. With a well designed PMO Content Asset framework, all those involved with projects and the PMO speak a common language, follow a common set of guidance, and access a singular place of management vetted and approved information. Without a PMO content asset framework, it can be difficult to keep everyone on the same page and many pieces of valuable content will likely become orphaned and lost over time. Saving Changes...
Don KimPROJECT-TO-PORTFOLIO MANAGEMENT EXPERT| Seeking opportunitiesSacramento, CA, United States
This definition from the PMBOK 4h Ed. sums it up pretty well: "An information system consisting of the tools and techniques used to gather, integrate, and disseminate the outputs of project management processes. It is used to support all aspects of the project from initiating through closing, and can include both manual and automated systems." (Page 443) Saving Changes...
We tried the traditional approach to our PMIS, per the PMBOK definition, and found that it (the idea of a PMIS) doesn't work and is confusing to our users. We quickly moved to the PMO architecture approach and rather than combining tools and non-application knowledge into a PMIS - we separated these things. Our PMO content asset framework houses all of our non-application kinds of information such as processes, guidance, templates, dashboards, SME techniques, and learning and mentoring information as well as policies/guidance for tool usage (Project Server, SharePoint and a wide variety of point tools) including URLs to link to the tools in the context of following our PMO processes. Not only is the PMO architecture approach more elegant and technically correct, everyone understands and is much happier with the PMO. Saving Changes...
