Why the Project Sponsor Must Attend the Kickoff Meeting

Why the Project Sponsor Must Attend the Kickoff Meeting 331

 

If your project sponsor doesn’t want to star in the project kickoff meeting for whatever reason, your project will be in trouble from the beginning. Bob McGannon and I explain what the sponsor’s role is in a kickoff meeting and we highlight all the ways their absence creates problems. Don’t worry. We provide some tips for convincing the sponsor to show up.

 

 

 

Coming Up

Many different audiences make up a project team, from the project sponsor and customer to numerous stakeholders, to various teams that take on the work in the work breakdown structure. These audiences often need different information, prefer different communication methods and frequencies, and come with unique perspectives and idiosyncrasies. I’m a big believer in effective communication, so I’m looking forward to this conversation with Tatiana Kolovou and Brenda Bailey-Hughes. I hope you’ll join us on Friday, April 10, 2026 at 11am MT/1pm ET. Click here to join!

______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 103,000 subscribers. This newsletter is 100% written by a human (no aliens or AIs involved). If you like this article, you can subscribe to receive notifications when a new article posts.

Want to learn more about the topics I talk about in these newsletters? Watch my courses in the LinkedIn Learning Library and tune into my LinkedIn Office Hours live broadcasts.

_______________________________________

Think People Are Too Busy? Think Again.

Think People Are Too Busy Think Again.“We’re too busy” kills many justifiable projects before they start. Some organizations overcome this resistance, not because they’re less busy, but because they view their business holistically and fit projects into their daily activities, without hiring expensive contractors. Here’s how:

  • Prioritize more than the project portfolio. You might think you’re all set by prioritizing all the projects in your portfolio based on business strategy, objectives, business value, and other factors. But that isn’t enough. To balance workload between projects and day-to-day operational activities, PMs and sponsors need to prioritize both project work and day-to-day operations effort.  For example, a senior help desk analyst might jump off the support line to work on project tasks. If the call queue reaches 20, they go back to taking calls until the queue drops to 10. In another example, financial staff might be assigned to project work for 2 hours every day, except for when they complete month-end accounting. In addition, if there’s an emergency, such as misclassified transactions, they would stop project work until the emergency is resolved. Otherwise, their highest-priority work is completing project tasks for their designated project time.
  • Evaluate the capacity of organizational change agents in the organization. In most organizations, a small number of highly experienced, capable people drive large-scale change. They are typically called “change agents” and comprise a mix of management and expert team-leaders. Instead of focusing on the capacity of all employees, look at the workload and remaining capacity of these change agents. Identify the business impact of their work and prioritize accordingly. See which part of the business they change and check the priority of projects in that area of the business. Then launch the highest priority projects in their area when they have available time to work on it.
  • Use phased rollouts with minimal scope. The Minimum Viable Product (MVP) approach works for several reasons. For justifying a project, the smallest possible scope requires less immediate commitment from operational team members. Start with a pilot that delivers quick wins with a few resources.  This reduces the perceived burden of additional work. It also builds credibility and enthusiasm that makes it easier to staff subsequent phases.
  • Justify and describe project objectives in terms of operational work relief. Don’t focus on the workload that project work creates. Instead, highlight how the projects will ultimately make day-to-day operational work easier and less annoying. When team members see that a process improvement project will eliminate the tedious manual data reconciliation that eats up their Fridays, their resistance might change into enthusiastic support. Connect each project directly to the pain points people feel, and they’ll make time for project work.

 

Coming Up

Many different audiences make up a project team, from the project sponsor and customer to numerous stakeholders, to various teams that take on the work in the work breakdown structure. These audiences often need different information, prefer different communication methods and frequencies, and come with unique perspectives and idiosyncrasies. I’m a big believer in effective communication, so I’m looking forward to this conversation with Tatiana Kolovou and Brenda Bailey-Hughes. I hope you’ll join us on Friday, April 10, 2026 at 11am MT/1pm ET. Click here to join!

______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 103,000 subscribers. This newsletter is 100% written by a human (no aliens or AIs involved). If you like this article, you can subscribe to receive notifications when a new article posts.

Want to learn more about the topics I talk about in these newsletters? Watch my courses in the LinkedIn Learning Library and tune into my LinkedIn Office Hours live broadcasts.

_______________________________________

The Myth of the 40-Hour Work Week

Myth 40 hour work week 317

 

The concept of a 40-hour work week is thrown around constantly. And many project plans use this week to develop a schedule. Sadly, a 40-hour work week is a mythical beast. Bob McGannon and I rant a bit about this obstinately long-lived myth. Then we discuss more realistic work weeks and how to apply them in your project schedule.

 

 

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 103,000 subscribers. This newsletter is 100% written by a human (no aliens or AIs involved). If you like this article, you can subscribe to receive notifications when a new article posts.

Want to learn more about the topics I talk about in these newsletters? Watch my courses in the LinkedIn Learning Library and tune into my LinkedIn Office Hours live broadcasts.

_______________________________________

Personal PM: Managing a Job Search

Personal PM Managing a Job SearchA job search is a project, so what better way to make it a success than to use your project management skills on it? By approaching it this way, instead of passively waiting for opportunities, you’ll lead your own career transition with intention. Anna Anderson and I joined forces to explain how to apply your project management skills to a job search. 

Begin with measurable goals and objectives. Just like any other project, it’s important to know the outcomes you want. Clear objectives support better decisions. With your job search, lay out your goals and objectives. Don’t say, “I want a PM job.” Spell it out. What industry(ies) are you targeting? What level of role? Identify any constraints you have. What salary range do you need? Are you willing to relocate? How much flexibility do you need in your work schedule?

Make your job search goal concrete: “I will obtain an associate project manager role in the healthcare industry with a hybrid work schedule within six months and at a salary range from $X–$Y per year.” Your resume and LinkedIn profile become strategic artifacts, tailored positioning tools aligned to your goal.

Define your job search scope. What are you going to do to successfully snag your next job? Here are typical activities:

  • Update your materials including your resumé, LinkedIn profile, project portfolio, and cover letter templates.
  • Build a target company list.
  • Set up a system to track applications. Set a target of 5 or more companies per week.
  • Network with recruiters, industry or professional contacts, school alumni. (Note: Use the 80/20 rule of 80% networking to 20% applying. You network with people at places where you want to work, so that you apply to the right places with intention.) Hold informational interviews.
  • Prepare and practice for interviews. Practice questions. Prepare your offer negotiation strategy.

Don’t forget to identify what is out of scope, such as jobs that don’t meet your salary requirement, unsuitable location, or short-term freelance gigs.

You can even define personal metrics: number of networking conversations per week, interview-to-offer conversion rate, response rate to outreach messages. What gets measured gets improved.

Build a timeline with milestones. Work backward from your target date. If you want to land a role by July 31, when must you complete all the tasks in your scope? Create milestones for weekly applications, networking, and interview stages. 

Manage your search the way you would manage any initiative. Conduct weekly reviews. Identify risks: skill gaps, confidence barriers, market conditions – and create mitigation strategies. Use a simple Kanban board in Excel, Trello, Asana, or another tool to visualize progress.

By structuring your search this way, you’re not only increasing your chances of landing a role, but you’re also actively demonstrating the planning, adaptability, and ownership that hiring managers expect in today’s project environments.

Add a comment or question to the comments section. We’d love to hear whether you find this approach helpful in your efforts.

 

Anna offers a lot of resources for careers in project management including job searches.  Check these out:

Her program – www.womeninpmnetwork.com/enrollnow to help you learn the steps to your next Project Manager role.

Book your Free 20 min clarity call while spots last: https://PMDiscoveryCall.as.me/ 

Subscribe to her podcast here: https://open.spotify.com/show/4TpOpKXNjFqLb2F8ir2tON?si=b24ba7825ca84546

Subscribe to her YouTube: https://www.youtube.com/@projectmanagerconnectshow

 

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 103,000 subscribers. This newsletter is 100% written by a human (no aliens or AIs involved). If you like this article, you can subscribe to receive notifications when a new article posts.

Want to learn more about the topics I talk about in these newsletters? Watch my courses in the LinkedIn Learning Library and tune into my LinkedIn Office Hours live broadcasts.

_______________________________________

Balancing Technical and Business Requirements in Agile Projects

Balancing Technical and Business Requirements in Agile ProjectsBalancing technical and business priorities in an agile backlog is a constant negotiation between delivering immediate value and maintaining long-term application stability. The goal is to help stakeholders see and understand the trade-offs that must be made between the outcomes that they want and the work to maintain technical integrity. Here are approaches to consider:

  • Tie every backlog feature to measurable outcomes. Make sure that all feature descriptions include business value, technical enablers, and/or risk reduction so every stakeholder understands why a feature matters. It’s a good idea to specify when a feature is a prerequisite to other features that create technical stability or drive business outcomes (so a prerequisite feature isn’t altered because its importance wasn’t clear).
  • Use a scoring model for prioritization. Models that assess the value of each backlog item help achieve the right balance between business and technical needs. Using time and cost data regarding the production of every backlog feature, include an estimate for each backlog item of the value it will deliver to the business or the value for the technical team that maintains the agile project’s deliverables. Data on delivery timeframes can help prioritize features so the ones with the most value and shortest delivery timeframe get the highest priority. also be used to identify features with the greatest value, and the shortest delivery timeframes are at the top of the prioritized backlog. 
  • Plan capacity for technical rework. Even a perfectly balanced mix of business and technical backlog items can result in incomplete or technically flawed features. Set aside a consistent sprint percentage—often 15–20%—for rework, implementing additional automation, or infrastructure work to prevent technical issues downstream.
  • Facilitate transparent trade-off discussions. Stakeholders’ impatience for business-related features often chafes at the time it takes for the IT team to make technical features work properly. Prioritization discussions can get contentious and messy. So, to reduce this contention, the business folks need to understand the technical necessity of IT required features. Bring product owners, engineers, and business leads together regularly to reassess the backlog so everyone contributes to prioritization decisions. Note: Many agile projects stumble because the full complement of business and technical stakeholders who attend early prioritization meetings dwindle as the project progresses. Make sure that everyone needed attends!
  • Assess priorities in the bigger picture. Markets shift, systems evolve, and dependencies change. Look outside the organization and review your backlog from that perspective to ensure alignment with strategy and business objectives in a rapidly changing world.

For more about project requirements, check out Daniel Stanton’s Project Management Foundations: Requirements course.

 

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 103,000 subscribers. This newsletter is 100% written by a human (no aliens or AIs involved). If you like this article, you can subscribe to receive notifications when a new article posts.

Want to learn more about the topics I talk about in these newsletters? Watch my courses in the LinkedIn Learning Library and tune into my LinkedIn Office Hours live broadcasts.

_______________________________________