Executives and other plan sponsors often have difficulty gauging how well a project is faring. From their somewhat removed vantage point, they likely don’t know if everything is on track at any given time. They don’t typically have detailed insight into how each of the critical paths is being managed from day to day, for…
project management consulting
Projects that have clear and ongoing project communication issues eventually become plagued with problems. You’ve probably seen it before: The people responsible for managing schedules and monitoring progress are seen huddled in a corner solving problems, but the issues they’re working on and the solutions they’re developing to address them aren’t always communicated outside the…
When time is tight and there’s pressure to get a project underway as quickly as possible, it might be tempting to ignore concerns that might keep you from revising a project plan that is out of whack. You probably know the feeling—you’ve seen the plan but you don’t think it can possibly be executed as…
Project managers can usually spot scope creep once it appears, but by that point the damage has already begun and it’s a challenge to get things back in line. Sometimes the hardest part of fixing a problem is knowing why it happened in the first place. That’s the case with teams that find themselves hindered by a scope that has grown out of control.
Your team may occasionally execute projects that will have unwelcome effects on an organization’s workforce. Most impacts are intended to be positive, such as workflow and machinery updates that improve safety for staff. But in other cases, employees may learn their jobs are scheduled for relocation or that their positions are being eliminated entirely.
Most project teams have a standard repertoire of projects they execute on a regular basis. With a few variations here and there, your routine may consistent mostly of developing new software or retooling manufacturing processes. But companies occasionally encounter firsts—bringing their debut product to market, for example, or adding a function they haven’t supported before.
Time is an important component in every project. From scheduling sought-after craft labor resources to meeting key task deadlines, PMs must remain focused on time throughout the effort. But some projects are more time-sensitive than others. If your team is working on initiatives that require tight timeframes or have fixed completion dates, keep these helpful strategies.
One hallmark of nearly every project team is constant activity. Everyone is engaged and occupied with their tasks. They’re adjusting their workloads to ensure nothing falls behind and they maintain proactive communications across the various cross-functional sub-teams to move the project forward. But while these day-to-day efforts are an important component in success, PMs must be careful that they don’t confuse effort with the real bread and butter of project management: results.
Every project stems from an organization’s need to accomplish something—to increase production capacity, for example, or to reduce costs across a process or within a department. No matter the type of need that launched it, each effort is expected to return some kind of value back to the company.
The on-deck project. It’s there, waiting in the wings, ready to go as soon as your team wraps up its current efforts. You and your stakeholders are probably excited to get going on it. It may be a garden-variety project, or it could be a one-time, strategically important initiative that will catapult the company forward. Either way, if its start date hinges on completing other tasks, it’s in a precarious position, because if something—anything—goes wrong with your present schedule, that on-deck project will almost surely be bumped.