powered by FreeFind

 

spacer
Volume IX - Issue XII - December 2007

Featured Papers

 

UPMM – A Full Model for Portfolio Management

By Stanisław Gasik

What is a project portfolio? May it contain a set of investment project only? But in project-based organizations just commercial projects and their sets are much more important than investment projects. Moreover, in such organizations you may not easily strictly partition projects into investment and commercial. Usually the first commercial project of given type delivered to a customer is to some extent at the same time an investment project as the supplier develops new techniques then. So even the full model of investment portfolios must cover commercial projects.

Should the portfolio management model focus on aligning processes as in PMI Portfolio Management Standard (PMI, 2006) or on executing, controlling, monitoring and closing processes as in Organizational Project Management Model Appendix I (PMI, 2003)? Of course it must cover both of these process groups. After selecting a mix of portfolio components (aligning processes) you have a lot of work to run and maintain a portfolio.

The Unified Portfolio Management Model (UPMM) built over PMS and OPM3 and author’s own experience with managing portfolios in a project-based organization gives an answer to both of the above stated questions. It covers both types of projects and full portfolio life cycle.


Read complete paper in English

 

About the Author:

spacer spacer
Stanisław Gasik

Stanislaw Gasik received his Master of Science degree in Mathematics from the University of Warsaw. Stanislaw moved to Project Management (PM) after working over 15 years as a software engineer, analyst and consultant in the information technology (IT) sector. He began his PM experience with several years of quality management, after which he started delivering his own projects. He has been a lecturer in software engineering and project management at the Warsaw School of Economics and other Polish educational institutions. He was a member of the team that developed the Guide to the PMBOK® 2004 for the Project Management Institute (PMI®). He was active in other PMI standardization projects like the development of the Portfolio Management Standard. Currently he is a board member of the PMI Warsaw Chapter, responsible for education and professional development.  Stanislaw headed implementation of Primavera portfolio management tools at ComputerLand, Poland, which was distinguished with the Primavera Excellence Award in High Tech sector in 2006. His professional interests include portfolio management, PMO, maturity models, knowledge management and supplier-customer relationships in project management. Stanislaw can be contacted at sgasik@sybena.pl.

 

 

 

 

 

Top of Page


Churchill's Team
Churchill the Agile Project Manager - Part 16

By Mark Kozak-Holland

Most people are very familiar with Winston Churchill but may not be familiar with his “agile” approach to project management and his skills as a PM in the summer of 1940. Part 15 looked at how Churchill how stiffened resolve, took the offense with decisive action, and focused on the morality of events. This was very pertinent to Churchill’s long term strategy. This article switches gears and looks at how Churchill’s organization prepared itself for the air battle to meet his short term objectives of staving off the invasion.

For Churchill radio broadcasts were the core to his project communications and used to promote his strategy (Part 10). Combined with his governance framework (Part 11) this would allow his organization to pursue the complex project, the single objective of which was the survival of the U.K. The successes of his public communications after Dunkirk (Part 14) took the pressure off him and his team to execute the project.


Read complete paper in English
Read the previous paper in this series. Churchill the Project Manager (Part 15)
View the entire series at: www.pmforum.org/library/papers/index.htm

 

About the Author:

spacer spacer spacer spacer
Mark Kozak-Holland

Mark Kozak-Holland’s latest book in the Lessons-From-History series is titled “Project Lessons from the Great Escape (Luft III)” www.mmpubs.com/catalog/lessons-from-history-c-4.html. It draws parallels from this event in World War II to today's business challenges. His previous books include “Churchill’s Adaptive Enterprise: Lessons for Business Today”, “Titanic Lessons for IT Projects”, and “Avoiding Titanic Disasters: Project Lessons for IT Executives”.  Mark is a Senior Business Architect with HP Services and regularly writes and speaks (presentations and workshops) on the subject of emerging technologies and lessons that can be learned from historical projects. He can be contacted via his Web site at www.lessons-from-history.com or via email to mark.kozak-holl@sympatico.ca.

 

 

Top of Page


Why do Developers contribute to Open Source?

By Bas De Baar

Whatever your take is on projects, at the end of the day it is just a bunch of people working together to achieve a certain goal. To laugh, cry, pull pranks, play dirty tricks and show all other kinds of behavior towards each other. If you are lucky they even work to reach the final goal. If you take everything away, and put people in the center of what a “project” is, you will see a group of stakeholders interacting with each other, just like any other group of people would do. As a Project Manager it is your goal to herd the project crowd toward the required end result.

If we put the behavior of project stakeholders to the front of a PM’s concern, the most important and essential question we can ask ourselves with the profession is: “Why do project stakeholders behave the way they do?” For the money, the glory and the girls. That would be the quick answer. Humans works for incentives, give us money and we will do the job. We also want to be famous. We do almost everything the get in the spotlights. And there are the girls, or boys, whatever you prefer. Before you expect an answer, this is one of the BIG questions of our species, which we haven’t completely figured out yet. But we have come far enough to shed some light on this topic.  It is a crossing between economics, psychology and sociology. And yes, as a Project Manager you have a broad pallet of aspects to consider.


Read complete paper in English

 

About the Author:

spacer spacer
Bas De Baar

Bas De Baar works as a Project Manager within the financial industry. Since 2001, he has been the editor of www.SoftwareProjects.org, a popular website dedicated to Software Project Management. He holds a masters degree in Business Informatics and currently lives with his wife in the coastal town of Zandvoort, The Netherlands.  His latest book, “Surprise! Now You’re a Software Project Manager”, was published in September 2006 and is available from www.SoftwareProjects.org/surprise.htm or from most book retailers.  Mr. De Baar can be reached at basdebaar@gmail.com.

 

 

 

 

Top of Page

 

 

 

 

 


PM World Today™ is a trademark of pmforum.org, Inc.
PMWT™ is a trademark of pmforum.org, Inc.

The information on this web site was checked for accuracy and authenticity when last updated. If there is any accidental infringement of copyright, the publisher of this site apologize for their actions, and would like to be notified. In addition, the publisher of this site cannot bear responsibility for the actions or the results of action of individuals or companies arising from use of information and advice contained within it.

PM World Today Privacy Policy Terms and Conditions.

© Copyright 2007 PM World Today

 

 

gipoco.com is neither affiliated with the authors of this page nor responsible for its contents. This is a safe-cache copy of the original web site.