Reporting the results of what your PMO achieves helps define the value that your PMO provides. This article has some tips on how to produce meaningful reports for a variety of audiences. In this article, "PMO" can mean project, program or portfolio management office.
559 items found
The goal of this article is to offer practical strategies that will help you manage change effectively. The background and examples in this document have an IT bias, because the author took many ideas and examples from recent experiences managing change for 2 years in a $US20 million dollar database migration project. This project had it all-extended duration, large number of critical business intelligence applications in scope, two external vendors, and several other "critical" projects taking place in the same time frame. Change had to be managed or change would have devoured the project.
Why do design changes, mismatched parts, repetitive safety problems, or high rates of returns allow some businesses to continue "in the pink," while other similar businesses suffer the blues? If problems like these are getting you down, you may have the "configuration management blues." Good configuration management is necessary to keep your products good, your projects on track, and your whole group playing together.
Visual Ishikawa Risk Technique (VIRT) is a technique that is consistent with the Identify Risks process group of the PMBOK® Guide and uses a risk breakdown structure as its main principle artefact. However, it differs in that it uses the Ishikawa diagram (commonly also known as a fishbone, or cause and effect diagram), for the risk structure, to create a graphic view, as opposed to being text based or tabular.
Most relief and rehabilitation work following earthquakes begins as projects. The application of project management principles in these projects helps channelize the work into a systematic and coordinated effort having maximized output and expeditious delivery. This article discusses telecommunication restoration projects in earthquake-affected areas.
Ask most project mangers whether they use configuration management, or even what it is, and you'll most likely get a blank stare in return. How does CM actually contribute to change control? What value does CM add that would make a project manager want to use it? Should CM be used for all sizes and types of projects?
This paper is a "lessons learned" from a successful certification of organizational project management practices to the ISO 9001:2000 quality management standard in 2007. It provides an impression of the challenges and approaches taken to achieve certification to the standard.
The author presents the three critical factors to a project manager’s career development, (1) Belief, (2) Strategic Commitment, and (3) Reputation. Focusing on these can help ensure that career development is managed as well as projects.
The author recently had an opportunity to switch into a technical project manager role after being a business project manager for over 12 years. She traces her 18-month journey to learn what skills are easily portable and which ones needed refining or, worst case, acquiring. She focused on two main areas: communications and teamwork.
In a customer-service provider relationship, there is a great deal that the service provider can do to make the relationship productive and vibrant from a project management perspective. Dedication to understanding the customer is key. This means understanding not only the customer's needs, but also the customer himself or herself. Understanding the customer requires thinking about what a requirement means to the customer. And requirements might not mean the same thing to the customer as it does to the project manager.