We now look to PMOs to take more of an active role within the entire lifecycle. For that expanded role to be successful, the PMO needs to be more than simply the guide and controller for project execution; it needs to be accepted into a leadership role within the organization--partners with business units and accepted experts on portfolio execution.
You can put as many management and oversight layers in place as you like, but ultimately the frontline of project execution is made up of project managers and their teams. The first Thursday of November is almost here again--International Project Management Day--so let’s celebrate PMs (but let’s plan that celebration properly first...).
One of the most important things to have is self-awareness--we have to recognize when it is us as project managers that are causing the problems, and when our team members are telling their colleagues about horror stories where we are the bad guys. Here are three swivel-eyed demons to watch out for...
The waterfall methodology for projects is aptly named, because it is equally painful to try to go back to prior phases of a project once the effort has advanced to the next phase. This article will outline two reasons to avoid waterfall, and three ways to approach software projects that are more useful.
Is "consultant" a dirty word? Many consultants get a bad name from the fact that they become indistinguishable from the organizational employees that they work alongside. How do you know that hiring a consultant is a good idea?
Some studies have indicated that the real benefits of offshore outsourcing can be diminished by issues in communication, skill sets and accountability. But if managed properly, offshore IT projects can reap substantial rewards.
Many consulting engagements see frustrated consultants because they are not allowed to do what they feel is needed to maximize the chances of success. Here, we look at how these scenarios can be avoided--something that starts with trust.
Choosing the best framework or methodology requires thought, but be careful not to overanalyze it. PMs can gain valuable insight from Bruce Lee’s philosophies, which offer a sound approach to achieve success in any area.
How strictly should an organization enforce its process methodology? In this article, we look at ways that organizations can provide flexibility to their project managers without damaging the effectiveness and credibility of their project approaches.
If the schedule only exists to track what happened, it is a fairly useless tool. It will be glad to talk to you about the project and tell you how horrible things are, but that is not what project managers need. Here are some ideas for using the schedule to help the project instead of just using it to document failure.
In the journey to PMP fitness, you have taken three decisive steps. But many PMs have not had the opportunity to participate in a suite of courses where most knowledge areas are explored from a combined approach of PMI theory and real-world application. While this can put you at a real disadvantage, it’s still possible to be successful. In out latest installment, we cover Project Integration Management.
While many projects may not have to adopt the elements of the Federal Incident Command System, some are set up to resolve a certain time-bound resolution of organizational priorities and can reap the benefits.
With the ever increasing use of technology, how are processes impacted? Our writer feels that technology should be an overlay to the process work--we should start with a solid process and then look for ways that technology could make life easier in the execution of the process. But a colleague doesn't agree...
Every project has an issues log. But what about the PMO? Does your PMO manage issues and maintain an issues log? Do you look for trends across the issues of different projects and take proactive steps to address them? Do you attempt to prevent issues through good communication? In this article, we look at a model for PMO-level issue management and suggest ways that it can improve the quality of projects that your PMO is responsible for.
If governance is designed to ensure that project execution occurs appropriately, then who ensures that governance occurs appropriately? To try and avoid conflict, an organization needs to ensure that governance committees operate with a series of guidelines.
While “blame” is not a constructive term to use in establishing where things went wrong, every element of a project should have clearly defined owners. If it isn’t clear where that ownership lies, there's a fundamental problem in the way your project is structured. Here we look at how we can establish that ownership--and ensure that the model is applied effectively.
Managing issues on a project takes strategic planning and a little finesse so that issues do not turn into show stoppers. Do you have an issue management plan that can handle any problems and still keep the project on track?
The PMO must have an easy time of annual planning, right? It's a service function that provides resources based on the overall project portfolio, and the organization determines which projects to approve. Based on those decisions, the PMO knows how it needs to adjust its resource model. But life’s not quite that simple...
We all know that process improvement is important, but who should deliver it? Whoever owns a process should also be accountable for the improvement of it--and when we are talking about PM processes, that frequently means the PMO.
Information is not knowledge,
Knowledge is not wisdom,
Wisdom is not truth,
Truth is not beauty,
Beauty is not love,
Love is not music
and Music is THE BEST