Posts

Prioritize your PM Work

There are hundreds of things you can do as a project manager to deliver a project. How do you prioritize what’s on your project management to-do list? Here are tips from the pros:

Let the environment guide you. Monitor your project environment and respond to concerns that arise. Things change day to day in a project. Teams can get stressed. Key staff can argue. Stakeholders hear rumors and get fearful. Unexpected issues arise. Ensure you address these concerns, and you’ll create a positive environment for project delivery.

Accommodate your senior stakeholders. Design your to-do list around what your stakeholders need to trust in your project management. Understand their desires. Are they detail oriented? Do they want frequent status updates, or alerts only if there’s a problem? The last thing you want are worried senior leaders, so accommodate their needs – but don’t hide bad news from them!

Focus on risk. Keep risk monitoring in the forefront. Talk about risk often with your team. Watch for risk triggers and be proactive with your response strategies. Supporting a risk management mindset is powerful – make it a significant part of your to-do list.

Complement your project team. Every project team has strengths and weaknesses. Use your experience to make up for team shortcomings.  When appropriate, offer your help and teach your team members. Ensure you aren’t taking over their responsibilities —  you already have enough to do as the PM!

Support your team. Your team is crucial to project success. Take care of them. Pay attention and support their needs. Thank them when they do well and guide them when they go astray. It’s easy to forget this in hectic project environments, so ensure supporting your team is a to-do list priority.

For more info, watch my course Project Management Foundations.

Managing the critical path isn’t enough

You manage your project schedule by focusing on the critical path. But don’t stop there! Project time management requires examination of other items. Here are things to check to proactively manage your schedule:

Examine “near critical paths.”A path with a small amount of slack means you have a near critical path. These tasks with very little slack should be monitored with the same diligence as your critical path, because almost any task delay could shift your critical path. 

Watch resource work time. Monitor variances between forecasted and actual work hours on your project. Consistent under-allocation of actual work time on project tasks could lead to schedule slippage. Ensure you understand why resources aren’t working as much as planned. Work with management if a reallocation of project tasks is necessary to keep things on track.  

Look for convergence tasks. Successor tasks with multiple paths leading into them are prone to delay, because many predecessor tasks must complete on time to keep the convergence task on schedule. Monitor progress leading up to convergence tasks and proactively respond if delays seem likely. Note: convergence tasks are candidates for contingency because of the likelihood of delays.

Note upcoming risks. Understand your risk triggers. Explore additional resourcing, fast-tracking or crashing alternatives if risks appear poised to come to fruition. Examine the possibilities for other risks due to delays to your schedule, such as losing staff to other initiatives or contractor agreements expiring.

To learn more, check out my Project Management Foundations course.

 

Less Wrong Estimating

It’s irresponsible to promote early estimates as being accurate. Early on, there are too many unknowns. A responsible approach focuses on communicating our estimates as gradually more accurate. Here’s what you can do to produce responsible estimates.  

  • Label your estimates. An estimate without a label implies the value is accurate. Label your estimates to indicate their accuracy, such as rough order of magnitude, budgetary, or definitive. Define the accuracy range for each label, such as -20% to +50%. Then, indicate when a more accurate estimate can be produced.
  • Re-estimate at key points in the project. Events like finalizing a contract provide significant information to improve your estimates. Produce refined estimates after each of these events. Develop and communicate a schedule for re-estimating, tied to the events, to demonstrate a clear rationale for how you intend to incrementally improve your estimates. 
  • Keep refining estimates during project execution. Don’t stop estimating after planning is complete. As major deliverables are produced and costs become known, continue to refine your estimates. This further demonstrates that estimation accuracy evolves, and reflects your concern for the money and time you spend.

Project management entails managing expectations. You can set expectations about estimating by creating an estimating schedule and estimating to that schedule as your project progresses. That’s a responsible and rational way to manage estimating.

To learn more about estimating, check out the estimating movie in my Project Management Foundations course.

#projectmanagement #projectpointers

Choosing the correct task dependency is easier than you think

Each task has a start and finish, so there are four types of task dependencies: finish-to-start, finish-to-finish, start-to-start, and start-to-finish.

In most projects, most (90% or more) dependencies are finish-to-start (FS). When one task finishes, it triggers the start of the next, like when cooking dinner is finished, eating dinner begins (assuming you don’t sneak bites while you’re cooking). That means you’ll check if FS is the right one first.

For the rest of your task dependencies, finish-to-finish (FF) is probably the one you need. This means, the finish of one task controls when the other task finishes. Hauling trash away from a job site doesn’t finish until construction is complete.

Start-to-start (SS) and start-to-finish (SF) don’t show up often.  Start-to-start can cause problems if the predecessor task runs late. And start-to-finish simply doesn’t arise very often.

The bottom line: You almost always use two of the four dependency types. To learn more about dependencies, check out my Project Management Foundations: Schedules course or see how to create dependencies in my Learning Microsoft Project course.  

#microsoftproject #projectpointeres #projectmanagement

Can you have too much authority as a project manager?

Bob McGannon and I talk about whether a project manager can have too much authority. We also talk about what to do to make sure everyone understands the authority the project manager does have.

https://youtu.be/oz7ydHpboVc

A tip for introverted project managers: Your team probably likes you that way.

Many of your team members are introverts. Engineers, developers, technical folk of all ilks tend to introversion. They usually want clear, rational reasons why the project is important and how they fit into the project picture. They almost always dislike sales pitches and hype.

As an introverted project manager, you are probably most comfortable organizing the project environment and making sure the work gets done. You also understand the importance of the project, the makeup of the players, and lots more. You are the perfect person to help your team members grasp the info they need, because you can talk in their language.

What’s more, you don’t have to be a cheerleader to lead a team. Introverts can inspire and motivate people just fine. Think leading by example. Or guiding and growing your team members behind the scenes. (As an introvert, you’re likely to manage people with a lighter touch than extroverts use.) And using thoughtful, yet powerful persuasion to convince people at all levels to do what’s needed.

To learn more about leading, check out the courses in the LinkedIn Learning Become a Leader learning path.

Using milestones to track progress

Tracking project progress is part of a project manager’s job. Gantt charts aren’t always the best way to report progress–they provide too much detail for busy leaders. Using milestone charts are better for reporting progress. Here are my recommendations.

  • In your project schedule, create at least 2 milestones per reporting period. Capture dates the milestones were completed and share the rationale for early or late completions. The milestones don’t have to be significant events, just tangible partial or full deliverable completions. If necessary, break down longer tasks into shorter ones to allow for these milestones.
  • Don’t abandon the Gantt chart! Manage your schedule and share details with a Gantt chart. It’s your best management tool. Use it whenever detailed tracking information is requested.
  • Create “super milestones” for major project events. Identify significant events with milestones in bold or capital letters. Use these to share high level progress. Continually track planned dates, and revised projections for completion of super milestones to show overall progress.
  • Update your milestones as the project progresses. As task completion actual dates can vary your schedule, ensure you continue to have 2 milestones per reporting period. Add new milestones if necessary. Also, add or revise dates for all your milestones as any project change requests are approved and added to your schedule.

Tracking progress isn’t the traditional way to apply milestones, but they create two levels of project tracking detail with minimal additional work. Share your intent to use milestones for tracking with leaders, especially if they have only seen milestones used for significant events.

To learn more see the “Learn to use milestones” movie in my course Project Management Foundations.

ProjectManager.com goes into more detail about what you need to track project progress. Check out Project Tracker: The Ultimate Guide for another take.

Should I pad my estimates?

Q: Everyone tells me to pad my project estimates. Should I follow their advice?

A: No! You should share your best, most accurate and non-altered estimates with your sponsor. Padding your estimate is adding contingency without justification. Be transparent. Share estimates with your sponsor, emphasizing that they don’t include contingency.  Then, share your recommendations for how much contingency to add based on specific risks associated with the project.

For more on project management, check out the Become a Project Manager Learning Path at LinkedIn Learning.

What’s the best style for a project manager?

Bob McGannon and I talk about project manager styles and the best one to choose in this video

To learn more about project management, check out the Become a Project Manager learning path at LinkedIn Learning.

Can there be too much collaboration on a project?

Collaboration is gold in projects. Collaborative stakeholders produce better requirements, provide support for your solution, and rarely raise issues when accepting deliverables. Even with these benefits, there can be too much collaboration. Here are symptoms of too much project collaboration and how to correct them:

  • You have more stakeholders than necessary. Environments that are extremely collaborative can bring a wide variety of hopes, expectations, and opinions – more than needed for success. When many stakeholders want to collaborate, assign primary stakeholders and secondary stakeholders (more like interested parties). Restrict project authority like submitting formal requirements or decision-making to your primary stakeholders.
  • Decisions take too much time.  As stakeholders seek to include others, decision-making can get dragged out. While including everyone can help produce better decisions, timeframes for reaching those decisions can be too long. Lack of consensus can cripple a project. To address this, include review time and decision-making tasks in your project schedule. Emphasize when decision-related tasks are on your critical path and discuss the impacts of extended decision-making time.
  • Scope increases. As stakeholders participate in requirements sessions and your solution comes to fruition, new ideas for adding business value can arise. The more the collaboration, the more this will occur! While business value is a good thing, your scope might grow beyond your “minimum viable product.” Ensure your change approval process focuses on limiting project scope to what’s needed to deliver business value. Remind stakeholders that Phase 2 of the project can be evaluated and cost-justified to accommodate the new business value ideas.
  • It’s difficult to get approval to proceed or implement your project deliverables. If you hear lots of “it’s ok with me, but please check with x” responses, you may have an approval process issue. Ensure you have agreed upon processes for approvals built into your Project Charter, including who has final approval.

To learn more, see “How organizational culture affects projects” in my LinkedIn Learning course, Project Management Foundations.