Writers' Community!
Home
Front Page Page Two Columnists Submit an Article FAQs Contact Author Login
Article Submission
We Need YOUR Articles!
We'll Promote Them for FREE!

Author Login

New Authors
Register Here


Now Serving 5,766 Authors
48,562 Quality Articles
& 5,029 Current Users Online!
Featured Authors
Teresa Ortiz (4,608)
Roschelle Nelson (526)
Tex Norman (4,107)
Ken McCreless (149)
Joel Hirschhorn (379)
Robert Melaccio, Sr. (6,317)
David Pekrul (574)
Camille Strate (1,318)
Lori Radun (830)
Susan Thom (8,705)
David Tanguay (7,694)
Joel Hendon (4,895)
Avis Ward (10,303)
Ira Coffin (461)

View All Featured Authors
Most Recent
The Fair trade Markets

Labor Law Posters, It's the Law!

Am I The Only One?

How to Select Future Business Leaders

How To Leave The Media A Voicemail That Gets You Booked

People Are Not Rungs on the Ladder of Success

Business: Having the courage to use the B word

Electronic Document Management - File Storage and Security

Smart Business Tax Planning for an Obama Presidency

Know Your Core Marketing Strength

Home » Categories » Business » Other Business » How to Projectize People and Adopt a Project Culture » Printer Friendly

How to Projectize People and Adopt a Project Culture

Rated 2 out of 5
No Reader Ratings Available ?
Rate It  /  View Comments  /  View All Articles submitted by John Reiling
Submitted Thursday, July 03, 2008
John Reiling (36)
PMcrunch
Log in to become a member of John Reiling's Fan Club!


Many organizations are "projectizing" and developing a strong and effective project management infrastructure. There are challenges along the way, and a number of approaches. However, regardless of the approach, changing the culture to be aligned to formal project management will involve aligning people, one by one, by empowering them with formalized project management knowledge. To accomplish this, organizations can do well to develop a granular approach to empowering their people through this projectization process.

Background
Projectization is a relatively recent phenomenon and is spreading rapidly. It is nearly synonymous with the idea, years ago, of electrification, where incorporating electricity into the physical infrastructure was taking place. With electrification, assets needed to be changed, thinking needed to be adapted, and people needed to be organized and train as part of a new infrastructure. While projectization is not so physical, it is part of the organizational infrastructure and demands the same amount of adaptation of thinking, organization, planning, and alignment, mostly of people.

Inputs
Organizational culture is one of the first inputs to this longer term process of implementing change to a projectized organization. Organization size is a key consideration. Another is sophistication level within the industry, especially on the part of suppliers and customers. Another key input is the operational structure of the organization: matrix versus hierarchical, process versus project orientation, and more. Another important input is the current skill level from top to bottom within the organization.

Outputs
Outputs of a projectization initiative will include greater alignment of projects with strategy and organizational goals, more purposeful implementation of projects, and more alignment of people. Another benefit may be increased ability to rotate people among various roles, producing cross pollination that helps bridge communication gaps. Other 'fallout' benefits are alignment of people around a common vocabulary and common set of concepts, more purposeful communications, and more aligned reporting.

Approach
A 'layered' approach is a good start at thinking about how to inject projectization into the organizational culture. What I mean by 'layered' is that the organization can be segmented logically into groups that will require certain predetermined levels of knowledge and competency in project management in order to achieve projectization.

In an organizational breakdown, a first step would be to map a new project structure to the current organization structure. In all likelihood, it will need to accommodate portfolio level management of projects and programs, as well as management of the actual programs and projects. Where these might fall within the organizational structure will be somewhat unique in each case, but will provide an early picture that indicates some needs.

Next, it is important to identify the roles that all stakeholders will play within this envisioned project infrastructure. What roles, many of them new, will need to be supported, and what knowledge and competencies will be required. For each competency, there will need to be a strategy, and the overall strategy will represent an integrated approach across competencies. Examples of relevant competencies will include Progam Management, Project Portfolio Management, and Project Management. One strategy is to set up levels of competency within each of these roles, and these could include criteria related to experience as well as certification. Depending upon the organization, more specialty roles can be defined around other competencies such as construction management, IT project management, Business Analysis, Information Technology Infrastructure Library (ITIL), PRINCE2, and a myriad of other areas that might apply in an organization.

The key is to implement interaction and training for the various constituencies, and to make sure that training is aligned as a whole with organizational goals, and with the goal of feeding a projectized organization. Supplemental efforts can include training that helps smooth communication, collaborative sessions around achieving organizational goals, and unified awareness of stakeholder roles within the organization.

Measurement
Measurement of success can be tricky, especially since this is not at the outset an easy thing to measure! My suggestion is to initially measure progress in training or any other metric that you can initially track. As the program unfolds, metrics will emerge for measuring organizational progress. Some examples off the top of my head include: meeting metrics, project success metrics, cultural alignment metrics, project completion metrics, and project portfolio effectiveness metrics. Because clarity will come over time, it is a good practice to acknowledge that and keep the measurement fluid and let it unfold over time.

--------

John Reiling, PMP is a project manager, business manager, consultant, and author. His web site Project Management Training Online provides online training in Project Portfolio Management, Program Management, PMP Certification Prep, and many related areas. John's blog is PMcrunch.com.





Reprint Rights

Log in to become a member of John Reiling's Fan Club!

Comments on this article:
No comments yet.


Was this article helpful to you? Leave a Public Comment or Question:

 

This Article has been viewed 1 times.
Article added to SearchWarp.com on Thursday, July 03, 2008
View other articles written by John Reiling (36)


If you found this article interesting, you may want to check out:

Disclaimer:  All information on this site is provided for informational purposes only! By no means is any information presented herein intended to substitute for the advice provided to you by any health care or other professional or organization.


Today's Most Popular
How to Calculate Your Break-Even Point and How to Use It

Recent Downsizing in Companies as a form of Restructuring

Printable Name Tags

Tips For Buying Wholesale Mexican Silver Jewelry

Dealing with Difficult People: 27 Secrets & Strategies You Can Apply Today

Finding weakness in the competitor strength.

Electrical Test and Tag Frequently Asked Questions

How To Prepare A Modern Meeting Agenda

Selling More Door To Door - Tips For Success

Managing Workplace Negativity: Negativists, Whiners and Complainers

Home  |  Page Two  |  FAQ's  |  Contact  |  Terms of Service  |  Article Submission Guidelines  |  Writers' Contests  |  Privacy  |  Mission / About
Copyright © 1999-2008 SearchWarp.com, All Rights Reserved - SearchWarp.com is an IcoLogic, Inc. Company