What is a PM to do when confronted with an organizational culture that places little emphasis on structured project management principles? In Part 2 of this series, we’ll examine a simpler approach for introducing structured PM techniques into an organization with one-page project plans.
192 items found
We have seen a growth in the emphasis on acquiring, managing, sharing and exploiting information--and supporting individual and collective decision-making. In particular, more mature organizations have the ability to recognize situational change and to adopt the correct management approach required to meet that change: agility. Two standards provide ways of assessing and developing these capabilities--and both are explored here.
Just calling a practice “best” does not make it so. But for many PM practitioners, the term “best practice” appears to represent the business practice equivalent of a “get out of jail free” card--wave it around enough, and critical thinking seems to be banished. It's time for a new outlook on this misused term and concept.
It's easy to find a million ways that software managers can fail with their teams and their projects. This article prioritizes seven practical leadership tips and techniques that can help build great teams that consistently deliver great projects. And these habits are so simple, you can put them into practice immediately!
Understanding philosophical foundations are required for success in managing projects in the “real world”. That will allow you to better pick and choose which methodology (essentially a philosophical framework) to adopt--not adopt or mix and match to achieve project success.
Matrix organizations have inherent weaknesses and pitfalls, but a project manager can transform those weaknesses for the benefit of the project. Here's some help.
Agile adoption outside of software is nothing new--it dates back very close to the origin of today’s agile methods, predating the term “agile”. However, what is new and noteworthy is the rate and scale of non-software agile adoption being witnessed today. Now--as more companies than ever are exposed to agile methods in their IT practices--these methods are being employed beyond the regular IT domain.
Procurement management is one of the knowledge areas in PMBOK, but procurements for large computer systems or multi-year projects can easily take on a life of their own. This article will provide guidelines for issues that are unique to a procurement project. Ensuring that these guidelines are followed (or at least considered) by the appropriate stakeholder will assist the PM in successfully completing the procurement so that the real work can begin.
Risk management on projects has become a doom-and-gloom exercise in finding all of the bad things that might go wrong and coming up with plans of what to do about them. Project budgets inflate and schedules extend as mitigation and insurance strategies grow and contingency budgets balloon. We highlight the negatives to such an extent that we forget to focus on the positives. Time to turn that frown upside down...
What is maturity? Can an organization be considered mature if it does the wrong things well? What if it does the right things in the wrong way? The OPM3 business standard helps organizations become more mature. But misperceptions still exist about what “maturity” means. This issue is not explained in the standard itself and has never been written about by anyone, so what better place to do so than here and now?