Should the PMO be owned by IT or the “Business”?

Neither! We describe the “business” as if it is a single entity. The “business” is a collection of departments whose priorities and objectives frequently conflict. The functions of a PMO are best assigned to a corporate entity which spans the business departments and IT and is closely aligned with the overall business strategy.

The PMO should have oversight responsibilities for the entire life cycle of all projects (including non-IT). This will provide the best chance of addressing conflicting priorities, standarding across the enterprise, and aligning with the “business” objectives.

Motivation, Productivity, and Change Management

Motivation, Productivity, and Change Management are very closely linked. Proper motivation can increase productivity. Attempts to increase productivity can decrease motivation. Change Management can significantly impact productivity and motivation. There must be a balance. Here are some suggestions:

1. Define the meaining of productivity based on organizational goals. Productivity must be measurable and objective

2. Job responsibilities, career growth, and rewards must be defined in a way that directly or indirectly supports the goals of the organization. This increases motivatation and productivity.

3. Organizations should establish a culture of change where changes are both scheduled, expected, and managed. In other words, when Change should be the norm it is expected and there is less resistance. Acceptance of change should be rewarded which increases motivation and productivity.

4. Morale affects productivity, motivation, and Change acceptance. Sports teams undersand the importance of morale in achieving goals. Too many employers and managers are unconcerned with morale.

Application Portfolio Management Tool Cpabilities

There is growing discussion about Application Portfolio Management but there aren’t many supporting tools.  In order to effectively manage Application Portfolios, the following information should be tracked.

- Profile information about each application including purpose, business owner, support team, technology, interfaces, etc.

- Supported business processes and business benefits

- Schedule information

- Component inventory and relationships

- Financial information (Cost to develop/enhance, cost to support, cost to operate)

- Business priority and disaster recovery priority

- Security/confidentiality and types of data

- Long-term strategy and justification (operate, repair, replace, retire)

- Maintenance requirements (e.g. table maintenance)

- Library locations