Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
The Project Management Stakeholder Web
Categories:
Stakeholder Management
Categories: Stakeholder Management
| Web 2.0 is changing the way stakeholders interact and work together within the project team and in the wider community around the project and the organization. Social networking, instant messaging and collaboration tools are overwhelming traditional organization charts, hierarchies and management structures. Here are a few examples of how things might change: Building and maintaining relationships will change. People add their uniquely human value in non-routine processes and creativity and organizations will increasingly use automation or "self-service" systems for the majority of routine activities. There will need to be a balance between pure efficiency (which is often appreciated) and developing meaningful relationships with stakeholders through human interaction. Weak links and extended networks let people pick up information from people who know the people they know. Project managers will need to learn to navigate their personal, professional and social networks to exploit these strong and weak links for the benefit of their project. Work swarming is characterized by a flurry of collective activity by anyone available and able to add value. Using weak links, swarms form quickly, attack a problem or opportunity, and then dissipate. The phenomenon is powerful but not controllable in any traditional sense. Informal groups outside the direct control of the organization often use social media to impact the success or failure of a project. Smart project managers will learn how to live in a social environment they can only partially influence. Virtual environments will become the workplace. People will interact with each other and the virtual environment to reshape the world they're looking at through simulation and experimentation. The challenge facing organizations and project managers is adapting to this environment to obtain the potential benefits for the project, the team and the organization. They must simultaneously maintain appropriate levels of governance and remain focused on the project objectives. Individuals will also need support to manage the complexity created by overlapping demands. Forcing individuals to operate in an over-stimulated state will be detrimental to the person and their performance on the project team. How is Web 2.0 affecting your stakeholder management? |
Project Management Is Shifting Dramatically. What's Next?
Categories:
Career Development
Categories: Career Development
| I have a feeling the nature of project management -- which has sustained my career for more than 20 years -- is changing radically. Two tectonic shifts in the business world made project management an obvious career choice for me back in the late 1980s: 1. Just as I was about to enter middle management, 25 percent of such jobs were eliminated from the economy. 2. Around that same time, organizations began to reorient their thinking and started to define and organize themselves as project-based businesses. Explicitly in response to these two phenomena, I consciously made the decision to leave line management and enter project management. The writing on the wall is certainly clear in retrospect. And honestly, it was pretty clear at the time as well. Now, I see three things happening that give me pause. They're clearly things I need to react to, but unlike last time, I don't know how. 1. Lower-level IT jobs continue to go to emerging markets. As the people who took these jobs 10 years ago mature in their roles, more of them are becoming project managers. They're close to their teams and to the work -- even if the sponsors are elsewhere. 2. The way project work gets done, particularly in the IT industry, seems to be undergoing an important shift. I really don't know what's underneath it, but I do know that PMI has embraced Agile development, even offering an Agile certification. Is this the direction in which IT is headed? 3. As we emerge from the economic crisis, every indication is that the way the global economy will function in the future will be very different. We keep hearing of a "new normal." To me, these three things spell change, and it seems to me I ought to be making some changes as well, but I'm not sure what they are yet. I'd be interested to hear and learn from you. What are your observations? What are your plans? Editor's note: In Project Management Circa 2025, published in 2009, editors David I. Cleland, PhD, PMI Fellow, Bopaya Bidanda, PhD, and 39 experts from around the world share their insights on the future of the project management profession. |
Do You Schedule Time to Stay on Top of Project Plans?
Categories:
Scheduling
Categories: Scheduling
| Scheduling time to execute your work is one thing. But project managers should also schedule time for scheduling. Setting aside a block of time each week lets you review your project plan, timelines and pre-requisites. It also lets you gauge whether you're still on track with deliverables and if you must make any necessary tweaks to your plan. I review all of the planned activities at least a week out and make sure everything is aligned to execute those activities. I recommend creating a two-month view of the project, no matter what the size. With that in place, it's a matter of confirming that you're still on target. At the end of each day, schedule an additional 15 to 20 minutes to look at the next day's schedule. I make sure all the meetings and activities that my team is managing are well-planned, scheduled and confirmed. It may seem tedious but spending time on scheduling will help ensure you stay on top of your plan and know that it's on track. Do you schedule time for your planning? Is it worth it? |
Is Crowdsourcing Most Effective in Doses?
Categories:
Nontraditional Project Management
Categories: Nontraditional Project Management
| In my previous post about whether crowdsourcing was worthy of all the exposure and hype, I asked for people's opinions. Well, you certainly responded, not only in comments on the blog but also through emails and on Twitter. Your responses were very helpful and well-thought-out. After reading your feedback and doing some research, I came to the conclusion that crowdsourcing can be a very effective tool. But only if it's used for a well-defined, focused portion of a project. Crowdsourcing generally works best when you need a sampling of input from a large population. This can include activities such as requirements gathering, securing non-rights-protected content or a resource donation (such as computer bandwidth). Some mentioned software testing as a crowdsourcing activity. In this case, it's no different than what companies have always done when their products go "alpha" and "beta." People are simply slapping a new label on an old activity. In any crowdsourcing scenario, the activities must be considered voluntary. There must be no compensation or contracts. And project participants must have a clear understanding that any contributions - tangible or intangible - are the property of the entity soliciting the input. My rule regarding compensation for work could potentially be broken through a contest approach such as the Netflix Prize project, which focused on algorithms to enhance the company's ratings system. But activities like these would have to be tightly managed. Are you or your company evaluating whether or not to foray into crowdsourcing? What types of projects will you use the activity for? |
Tracking Burn-down Progress
| Agile teams often rely on burn-down charts to show how much work remains in each two-week sprint. The starting point represents the total work to be done and ends at zero when it's finished. There's no detailed plan of how much work is done each day -- teams just draw a line from start to finish. But two problems can arise: 1. Teams get used to collecting data, but forget to interpret and take action on it. 2. Executives may look at the graph and become concerned if the actual numbers don't track precisely to the projected line. So how do you know when to be concerned versus when the numbers are varying normally? An average of 20 percent variance is a good rule of thumb. Anything less is a false alarm. Anything more demands attention. Here are some models I've created of possible scenarios, but in reality, progress is more of a wandering curve. The vertical axis shows how many hours are left and the horizontal axis shows how many days are left. The straight blue line represents the planned amount of work left each day in hours, while the red line shows the actual hours left. Case 1: Under the line The team consistently finished more work than expected. Does this represent an error in estimation or natural variance in the system? Case 2: Above the line -- but okay The team is running behind, but is close enough that it will still complete the work for the iteration. Case 3: Above the line -- in trouble The team is so far behind, it must stop and take action to address the problems or re-plan the work. This progress line is a powerful warning signal. How do you use burn-down charts? |