Posts

Focus on What’s Important

One of Stephen Covey’s 7 Habits of Highly-Successful People is to put first things first – that is – put your time and energy into what’s important and say no to what isn’t. Let’s look at common project manager habits that you might want to break in order to have time to focus on what’s truly important in your projects.

  • Attending repeat meetings routinely. Meetings are often pre-scheduled every one or two weeks. It’s a handy way to carve out time to keep stakeholders up to date. What if there’s no significant project news or risks to talk about? There’s no need for a meeting!  New habit: Work with your team to determine whether a meeting is necessary. Then, skip or cancel it if there isn’t anything relevant to cover.

  • Answering emails in order of receipt. Many project managers answer emails in the order they were received to reply in a timely fashion. Timely communication is important, but not every email requires an immediate response. New habit: Set specific times in your day to respond to emails. Review all new emails and prioritize responding to them based on their urgency and importance. (Give people another communication method for emergencies.)

  • Getting administrative tasks out of the way. Everyone has administrative tasks to do and seeing them on our desks can be annoying. (This is so me!)  Many people will finish these low-priority tasks up front, so they aren’t nagged by the piles of paperwork. Most of the time, you can postpone these activities until things calm down. New habit: Set aside time in your schedule when it’s usually quiet to handle your admin tasks.

  • Worrying about non-critical-path tasks. Keeping the project schedule on track is important. But you don’t have to scrutinize every task in your project. Don’t get distracted by issues with tasks that aren’t on the critical path. Instead, focus on critical tasks – the ones that affect your project timeline. New habit: Focus on critical path tasks and tasks with very little slack. Leave the management of other tasks to your team members.

  • Wasting time on time-consuming reporting processes.  Reporting is important — and time-consuming. You can streamline reporting, but that usually takes time. So what? Take the time to automate or delegate reporting. You’ll recoup it many times over during your project management career. New habit: Spend time up front to streamline reporting. Consider restructuring your project reports to make them easier to create.

  • Wasting time on any process. Just like reporting, there are lots of project management activities that are important, but chew through your workday. Think about ways to perform these tasks more efficiently. Prioritize them by how much time you can save. Then, spend some time each week making your efforts more productive: build templates, implement new tools, harness AI, and so on. New habit: Set aside some time each week to work on ways to make your work more productive.

  • Interrupting your focus by answering the phone. Phone calls interrupt your work and distract you. But they aren’t necessarily important or urgent. Don’t answer the phone unless you know it’s important. New habit: Don’t answer the phone unless you’re expecting the call. Set up a communication method (I recommend texting) for immediate and important communication. Commit to answering other forms of communication within a specific timeframe, such as 24 or 48 hours.

Do you have habits that you know aren’t effective? Do you have ideas for how to focus on what’s important? What is the one thing you could do differently that would help you focus on what’s truly important? Share with us in the comments section.

For more about being effective, check out Dave Crenshaw’s Time Management Fundamentals course. Or look at Chris Croft’s Five Ways to Control Your Time course.

Coming Up

Marlene Chism is an expert in conflict, anger management, working with difficult people, and having difficult conversations – things most of us want to avoid. Despite the tough topics, she’s a truly lovely person. In this LinkedIn Learning Office Hours, we’re going to dig into some of the concepts she teaches for dealing with conflict. We’ll spend the rest of the session providing practical advice for dealing with conflict and other difficult situations. Bring your questions about the conflict you need help with, and we’ll provide advice for as many as we can fit in!I hope you will join us on Wednesday, January 17, 2024, 11am MT, 1 PM ET for this no-nonsense, advice-packed session on dealing with conflict with composure.

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 57,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.

_______________________________________

Acronyms for Project Managers

If you use social media to manage your projects, why not reduce your typing with a set of project management acronyms? Bob McGannon and I decided to jump start the list with these (mostly) tongue-in-cheek acronyms. If you have suggestions to add to this list, share them in the comments!

SOS – Sponsor Over Shoulder – Can’t share truthfully in this message. 

Example: Talk later, SOS.

DT – Disappearing Team member – The issue that arises when team members’ work gets reprioritized, and your schedule suffers.

Example: My head hurts. My schedule has the DTs.

MIA – Methodology in Advance – Choosing the methodology to deliver a project before understanding what the project is for or what its outcomes are supposed to be.

Example: We’ve decided the MIA, so fingers crossed that it will work. 

RSAP – Ready Shoot Aim Project – Project deliverables were defined before needs were identified, understood, or confirmed. 

Example: It’s an RSAP. The stakeholders will never fund this!

LOL – Lousy Outcome Limit – The project’s performance has reached the point that it will definitely be cancelled. 

Example: We’re at LOL. I’m looking for a new job!

BTW – Behind Task Waffling – A string of excuses for why a task is behind schedule.

Example: That team gives me no deliverables, just BTW.

ASSER – Assuming Requirements – The requirements aren’t sufficient because the project team assume they know what stakeholders need.

Example: Our requirements are nothing but ASSER.

DITY – Do It to Yourself – Moving forward with a project despite knowing that fatal issues exist.

Example: It’s a DITY. This project won’t be pretty!

IOB – Incredibly Obscure Benefit. A questionable business justification for moving forward with a project. (Related to the essence of political campaign advertising)

Example: It’s an IOB business case. We’ll never deliver those outcomes!

FAQ – Frequently Altered Quality – Repeatedly watered-down quality levels from the original level as the project progresses.

Example: We keep FAQing this project, so we’re going to end up with a Dollar Store-quality product.

Stat-they – Status of They (Versus stat-us) – The make-believe status that key stakeholders (they) want you to share versus the accurate statUS that the project team reports.

Example: We gave them our status, but they really wanted a STAT-THEY.

UNCLES – Unrealistic Constraints Leaving Everyone Stumped – Project constraints that are unrealistic but senior management won’t change them.

Example: This project’s impractical and plagued with UNCLES.

OMG – Overly Modified Goals – Changing the project’s success criteria to keep it going despite diminished outcomes.

Example: OMG is the only reason this project is still alive.

SHOT – Sponsor Hung Out To-Dry – When politics or a powerful key stakeholder commandeers your project and sends it in a totally ludicrous direction.

Example: I have a sponsor, but he is SHOT.

POV – Point of Variance – The degree of variance from plan that can best be described as “This is when the screaming started.”

Example: We hit our POV, and the management review turned into a shouting match.

WARNS – Warnings Repeated with No Support – Sharing the reality of the project that management just won’t accept (or can’t handle), 

Example: I’ve tried WARNS, but management isn’t listening!

SPOC – Singular Point of Crisis – Your project’s point of no return. (Similar to LOL.)

Example: We’ll never deliver this; we’ve hit our SPOC.

TBA – To Be Admonished – The penalty project managers receive for trying to tell the truth.

Example: Management isn’t helping. They’re planning to TBA me.

TGIF – Thank Goodness It’s Finalized – The cheer a project manager shouts when they mistakenly believe project planning is finished.

Example: I yelled TGIF, but then reality hit.

CRISP – Crisis Right Inside Simple Project – When a project looks simple but has hidden complexities.

Example: I thought this project would be easy, but now I’m in  CRISP.

WTF – Wobbly Time Forecast – Very questionable estimate for completion of a critical task.

Example: My project schedule is a mess, its full of WTFs.

WOAA – When Objectives are Achieved – The surprised exclamation the team shouts when project objectives are achieved. 

Example: WOAA, we got an award!

GOFWOP – Going Forward Without a Plan – When insufficient planning will doom a project. 

Example: Management is in a hurry. This project will definitely GOFWOP.

STAIN – Stakeholder indecision – Sponsor and stakeholders don’t make decisions and delay project progress.

Example: Our project status is STAINed. We’re twiddling our thumbs until the stakeholders make up their minds.

SWAG-E – Somehow, we are gainfully employed.

Example: This project is a mess, but at least we’re SWAG-E.

Coming Up

Thank you for subscribing to my newsletter. I’m happy to know that you have found it helpful and enjoy seeing your comments and questions.
I am taking a short break, so this is my last article for 2023. My articles will resume the week of January 8th, 2024. The end of the year is a great time for renewal, so I hope you enjoy this time and start 2024 with energy, motivation, and enthusiasm!

 

Marlene Chism is an expert in conflict, anger management, working with difficult people, and having difficult conversations – things most of us want to avoid. Despite the tough topics, she’s a truly lovely person. In this LinkedIn Learning Office Hours, we’re going to dig into some of the concepts she teaches for dealing with conflict. We’ll spend the rest of the session providing practical advice for dealing with conflict and other difficult situations. Bring your questions about the conflict you need help with, and we’ll provide advice for as many as we can fit in!I hope you will join us on Wednesday, January 17, 2024, 11am MT, 1 PM ET for this no-nonsense, advice-packed session on dealing with conflict with composure.

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 55,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.

_______________________________________

 

Warning Signs that Your Project Schedule Isn’t Feasible

As a project manager, you must be able to recognize that your project schedule isn’t feasible. That way, you can proactively address issues, mitigate risks, and increase the likelihood of project success. Here are common warning signs that your project schedule needs work.

  • Building and sharing a schedule before scope definition is stable. When project objectives and scope are still in flux, a schedule is nothing more than a rough guess. Teams may be anxious to get to work, but it’s too soon to share a schedule if scope continues to change. This schedule will mislead people about when deliverables will be available. It also makes life miserable for the managers who allocate people to the project, because they have to replan staffing for the viable schedule when it’s available. Best practice: Ensure your scope is stable before distributing a schedule.

  • The schedule depends on heavy workloads. Team members often juggle multiple tasks on a project. And many have day-to-day business support responsibilities that aren’t tracked by the project. This combination can produce an excessive workload for a team member, which leads to burnout, decreased productivity, and increased risk of errors. Best practice: Understand the percentage of time each team member can dedicate to the project and schedule accordingly.

  • The schedule doesn’t consider competing priorities. The most critical project team members often deal with competing priorities (in addition to day-to-day bustiness duties), such as working on other projects, resolving business issues, reviewing project change requests, and taking on work delegated from their managers. These other duties take time and can affect the person’s availability on your project. Talk through what your crucial team members do in the organization and allocate their time to project tasks with this in mind.

  • The schedule was built on unrealistic estimates. Overly optimistic estimates plague a lot of project schedules, which means trouble. The uniqueness of project work makes it difficult to estimate. Plus, people might not be trained on estimation techniques. One way to improve estimates is to use PERT (Program Evaluation and Review Technique) estimation. Estimators provide three estimates for a task: optimistic (O), most likely (ML), and pessimistic (P). People don’t pull these numbers out of the air. They think about the work and consider what might happen (good and bad. This analysis improves the accuracy of the estimate. The typical formula for calculating PERT estimates is: (O+(4*ML)+P)/6.

  • Note: There is another way to improve estimates. Get into the habit of comparing final actual effort to your original estimates. These comparisons help project team members understand what happens in projects and how much effort different types of tasks take.

  • Stakeholder managers don’t buy into the schedule. Managers who allocate their people to a project have a big impact on the project schedule. If managers don’t think the schedule is realistic, they aren’t likely to allocate their people to work on the project. Review your project schedule with the managers whose people are needed for the project. Make sure they have bought into the schedule and the project outcomes.

Have your schedules suffered from gotchas I haven’t mentioned? Do you regularly look for other warning signs on your schedules? If so, share with us in the comments section.

For more about project scheduling, check out my Project Management Foundations: Schedules course.

Coming Up

Marlene Chism is an expert in conflict, anger management, working with difficult people, and having difficult conversations – things most of us want to avoid. Despite the tough topics, she’s a truly lovely person. In this LinkedIn Learning Office Hours, we’re going to dig into some of the concepts she teaches for dealing with conflict. We’ll spend the rest of the session providing practical advice for dealing with conflict and other difficult situations. Bring your questions about the conflict you need help with, and we’ll provide advice for as many as we can fit in!I hope you will join us on Wednesday, January 17, 2024, 11am MT, 1 PM ET for this no-nonsense, advice-packed session on dealing with conflict with composure.

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 55,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.

_______________________________________

Tips for Handling a Phony Scope Item Owner

Tips for Handling a Phony Scope Item OwnerA recent Project Pointer talked about controlling project scope by confirming that each scope item has a true owner behind it. That is, someone who understands the business processes related to their scope items, has funding for it, and has time to work with the project team to realize its benefits. But what do you do if a powerful senior leader is pushing scope, but isn’t its true owner? Here are a few tips if you find yourself in this situation. 

  • Ask your sponsor for help. Scope ownership is the responsibility of the project sponsor or product owner — project managers oversee managing scope. The sponsor should handle challenges or questions about new proposed scope. You can also run proposed scope through your change management process. Either way, the scope request and its ownership should be scrutinized. When the sponsor or change control board decide on the proposed scope, be sure to define and document its impact on the project. Then integrate this impact into your project management deliverables, including the cost, schedule, and risk plan.
  • Find additional stakeholder(s) with similar interests. Business processes rarely involve only one area of the business. So, process improvements might benefit more than one senior stakeholder. If you’re struggling with a scope owner, look for another stakeholder who’s interested in the proposed scope. Two stakeholders might be able to fulfill all the scope ownership criteria. Note: Make sure the stakeholders are willing to work together before keeping the scope item in your project.
  • Consider a different business justification. A proposed scope item might have business merit, but the explicit income or cost savings isn’t there, or it’s theoretical to calculate. In this case, think about a different way to justify the scope. For example, risk reduction could justify scope items. A friend of mine just upgraded his mobile phone. He didn’t upgrade because it was broken or because he’s a new tech geek. His phone wasn’t compatible with new versions of the operating system. He justified the purchase so he could keep the operating system up to date and reduce the risk of data security breaches.
  • Determine if delegation can support the proposed scope. Sometimes, the issue with scope ownership isn’t funding but with business process knowledge or time to support the effort. In this case, the answer might be to delegate scope management responsibilities to someone with the requisite knowledge and time. This approach presents a significant risk: that the person who delegated authority overrules decisions that the delegate makes. This can negatively affect the project schedule and cost. Try to ensure that the delegate’s authority is “veto-proof”, so their decisions won’t be overturned. This way, you can move the project forward with confidence.

Do you have other tips for ensuring that scope items are represented by true owners who can fulfill their ownership duties? Or do you have questions about a specific situation you’ve encountered? Share with us in the comments section.

For more about scope, check out my Project Management Foundations course.

Coming Up

Anna Lung’aho Anderson and I get so many questions from people who want to transition into a career in project management. In this LinkedIn Learning Office Hours, we’re going to dig deep into the work YOU have to do to move into project management. Yes, it does require some effort on your part. We will talk about how to figure out if project management is a good fit for you; learning project management hard skills and terminology; how to update your resume, LinkedIn profile, and approach to networking; and finally, how to research companies you apply to so you have a better chance of getting their attention. We’re also going to explore how to move into project management from non-traditional backgrounds, such as sales, real estate, customer service, nursing, and (fill in your current role here).

I am really excited about this event because Anna provides many more services and resources related to project management careers than I do: Career Development Coaching, Resume Writing, Interview Preparation, Negotiation, Resume Review, Change Management, Executive Coaching, and Leadership Development. I hope you will join us on Friday, December 8, 2023, 11am MT, 12 PM CT for this deep dive into the first steps to moving into a project management career.

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 54,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.

_______________________________________

 

You Know They’re the Scope Owner If…

You Know They’re the Scope Owner If…When project ideas flow freely, it’s challenging to manage scope. One sure way to keep scope in line is to evaluate whether the owner of each scope item is the true owner. If they aren’t and you can’t find the true owner, you can remove that scope item from the project. Here’s how to tell if someone is the true owner of a scope item:

  • True owners supply funding. The true owner will fund the development of their scope item and can increase the funding (within business case parameters) if the cost of delivering that scope increases. The true owner can defend the priority of their scope against other people’s scope. If they can’t do either of these, they aren’t really the owner.

  • True owners can provide capable resources for requirements, verification, and implementation of scope items. If they provide new or lower-level resources, they might not be the owner. Delays in getting resources could mean other scope items have higher priority. If there are resource delays, re-evaluate whether the scope item is actually out of scope.

  • True owners can make decisions about the scope. They can make decisions about how to build and implement the scope item. Others may be involved in decision-making, but the true owner has the final say. They need to understand the current business processes as well as how those processes will change when the project deliverables are implemented. When scope decisions affect others, the owner is able to resolve stakeholder conflicts by consulting with and influencing others about the scope in question.

  • True owners have time to support the project. True owners make time to support the project effort to handle questions and issues. They are able to participate so they won’t delay the schedule.

In the next newsletter article, we’ll look at what to do if a senior leader is pushing scope but doesn’t fit the criteria of scope owner.

Have you encountered scope that seems to be orphaned without an owner? Or someone promoting scope that doesn’t seem to fit the project goal and objectives? Would these criteria have helped you figure out whether the items were in or out of scope? Share with us in the comments section.

For more about defining scope, check out my Project Management Foundations course.

Coming Up

Anna Lung’aho Anderson and I get so many questions from people who want to transition into a career in project management. In this LinkedIn Learning Office Hours, we’re going to dig deep into the work YOU have to do to move into project management. Yes, it does require some effort on your part. We will talk about how to figure out if project management is a good fit for you; learning project management hard skills and terminology; how to update your resume, LinkedIn profile, and approach to networking; and finally, how to research companies you apply to so you have a better chance of getting their attention. We’re also going to explore how to move into project management from non-traditional backgrounds, such as sales, real estate, customer service, nursing, and (fill in your current role here).

I am really excited about this event because Anna provides many more services and resources related to project management careers than I do: Career Development Coaching, Resume Writing, Interview Preparation, Negotiation, Resume Review, Change Management, Executive Coaching, and Leadership Development. I hope you will join us on Friday, December 8, 2023, 11am MT, 12 PM CT for this deep dive into the first steps to moving into a project management career.

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 54,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.

_______________________________________

Drop the Extraverted/Introverted PM Debate

Drop the Extraverted/Introverted PM DebateFor the hundredth or thousandth time, I got pulled into a discussion about whether a project manager needs to be an extrovert. It’s a useless argument. None of the key behaviors that separate struggling project managers from successful ones relate to extroversion or introversion. Here are several effective behaviors that introverted and extroverted project managers demonstrate.  

  • Believe in the project objectives. Buy-in from stakeholders starts with the project manager. You need to understand the value (and outcomes) the project brings to the business, demonstrate a pathway to success, and respond to queries to build stakeholders’ belief in the project. You can do all these face-to-face, as well as through project status reports or targeted emails to key stakeholders. Both extroverted approaches and introverted approaches work. The key is prompt and accurate communication. 
  • Use active listening when interacting with people. Getting stakeholder support depends on them feeling heard and understood. When you talk to stakeholders, focus on what they say and what they need. Don’t get distracted. They want to feel like you heard what they said and can act on that information. It doesn’t matter whether you’re talkative or reflective. The key is that stakeholders believe you have their interests in mind. 
  • Be gracious and convey gratitude. Project management is a team exercise. Team members, management, vendors, product owners, and product users need to pull together to deliver a project. Be gracious when you ask them to participate, and be grateful when they deliver. In return, they will dedicate themselves to you and the project. You can do this quietly with a well-placed conversation or written note, or with bold, outgoing actions. Genuine kindness and gratitude go a long way.
  • Make decisions effectively and confidently. Many people think that quick decisions inspire confidence. Nope. Effective decision-making uses a combination of data, experience, and team input. Sure, some decisions require immediate action. In other situations, it’s better to take time to collect more data and opinions. Neither approach to making decisions has anything to do with extroversion or introversion.  

This list is by no means complete. What other important PM behaviors can be handled by introverts and extroverts alike? Share your thoughts in the comments section.

Coming Up

Anna Lung’aho Anderson and I get so many questions from people who want to transition into a career in project management. In this LinkedIn Learning Office Hours, we’re going to dig deep into the work YOU have to do to move into project management. Yes, it does require some effort on your part. We will talk about how to figure out if project management is a good fit for you; learning project management hard skills and terminology; how to update your resume, LinkedIn profile, and approach to networking; and finally, how to research companies you apply to so you have a better chance of getting their attention. We’re also going to explore how to move into project management from non-traditional backgrounds, such as sales, real estate, customer service, nursing, and (fill in your current role here).

__________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 53,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.

__________________________________

 

Embracing and Managing Cultural Diversity in Your Project Environment

Embracing and Managing Cultural Diversity in Your Project EnvironmentToday’s project teams often bring cultural diversity to a project. All your team members need to feel they belong and are accepted. That means cultural sensitivity is an important skill for project managers.  Here are tips to help you manage cultural diversity in your projects to improve project outcomes and address culture-related issues that arise.

  • Consider cultural sensitivity training. Identify your project team’s experience with working across cultures. If their experience is limited, schedule cultural sensitivity training. This training not only builds skills; it makes a statement that all cultures will be embraced during the project. It also helps facilitate communication. Look for specialized training programs, workshops, or online resources that cater to the specific cultures on the team.

  • Take advantage of diversity. Promote and celebrate the richness of the project team’s diversity as a strength. Diverse team members can provide valuable insights for navigating cultural nuances. Ask team members to share their experiences to build rapport as they work with other team members. Seek out their unique viewpoints to enhance problem-solving. In addition, share diverse team members‘ viewpoints with key stakeholders to expand stakeholder’s perspectives and their perception of the project’s value.

  • Align project controls with cultural norms. Consider cultural preferences when building your project plan, communication methods, and approach to conflict resolution. For example, build regional holidays and local working hours into your project schedule. Take into account cultural norms of hierarchical or consensus management as you develop your approach to decision-making. If team members are used to different norms (hierarchical or consensus), talk through the process and identify what will work best for the people and stakeholders involved. Making these adjustments builds trust and avoids misunderstandings.

  • Promote a culture of “positive intent.” Despite your best efforts, cultural misunderstandings are likely to occur. Promote a project culture where team members expect positive intent from each other. This helps ease tensions. Create a norm where team members immediately raise a concern if something makes them uncomfortable. The team members then meet and strive to understand the concern. Sharing the intent of the communication or action is key to understanding. Team members can agree about how to move forward in a way that is comfortable for all involved.

For example, one team member conveys their ideas bluntly and directly while others like to share their ideas as possibilities to consider. The blunt team member comes across as bossy or directive when that wasn’t their intent. The other team members can share their feelings about the bluntness, so they can talk it through and come up with a way to interact that works for everyone.

Do you have questions about how to solve cultural issues that arose in a project? Or techniques you’ve used to embrace cultural diversity to improve outcomes? Maybe you can share some of the nuances of your culture and how to work with those on a project. Share with us in the comments section.

For more about diversity, belonging, and inclusion, check out Pat Wadors’ Diversity, Inclusion, and Belonging course.

 

Coming Up

Anna Lung’aho Anderson and I get so many questions from people who want to transition into a career in project management. In this LinkedIn Learning Office Hours, we’re going to dig deep into the work YOU have to do to move into project management. Yes, it does require some effort on your part. We will talk about how to figure out if project management is a good fit for you; learning project management hard skills and terminology; how to update your resume, LinkedIn profile, and approach to networking; and finally, how to research companies you apply to so you have a better chance of getting their attention. We’re also going to explore how to move into project management from non-traditional backgrounds, such as sales, real estate, customer service, nursing, and (fill in your current role here).

I am really excited about this event because Anna provides many more services and resources related to project management careers than I do: Career Development Coaching, Resume Writing, Interview Preparation, Negotiation, Resume Review, Change Management, Executive Coaching, and Leadership Development. I hope you will join us on Friday, December 8, 2023, 11am MT, 12 PM CT for this deep dive into the first steps to moving into a project management career.

 

My updated Advanced Microsoft Project has been published to the LinkedIn Learning library. This update is completely rerecorded with a new, comprehensive sample project. It is half as long as the previous edition because I took out all the topics I cover in my other Project courses. My humble opinion is that it is also more engaging, because of everything I’ve learned about recording videos in the past 8 years! Here is a link that lets you watch the course for free for the first 24 hours after you begin watching.

https://www.linkedin.com/learning/advanced-microsoft-project-22898395

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 53,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.

_______________________________________

Which methodology is best for R&D projects?

Someone recently asked about the best methodology for managing a research and development (R&D) project. The answer depends on many factors. Here are a few things to consider and the methodologies you might use depending on the nature of your R&D project.

  • Project goals and objectives. R&D projects usually have lots of unknowns. You might be testing new materials, new processes, new tools, or all of these! Working through unknowns requires flexibility and taking small steps. You’ll want to promote learning during the project, too. Agile methodologies, using short iterations, are ideal for this type of situation. Each iteration might not produce a tangible product but can generate learning and knowledge, which help define the next step for the project. Projects where the driver of iterations is learning as you go are sometimes referred to as Spiral Projects. Each “spiral” will help identify and refine the goals and objectives for the next spiral or iteration.

  • Team size and location. Larger teams, or teams with critical skills working remotely, need more formal structure. It’s important to take time to ensure communication is flowing and information is understood. In this case, a more predictive methodology like waterfall is helpful. But, you rarely need to manage an entire project this way. A hybrid approach can be effective. A sub-team that is not co-located with the core team might use agile methods. Then, they can work with the core team to integrate their deliverables into the waterfall project that the core team manages.

  • How much you know about requirements. Agile projects are ideal when requirements aren’t well-defined. Requirements emerge through exploring and producing sample deliverables. However, R&D projects often have well-defined goals and well-understood requirements. Research and development come in with the processes for satisfying those requirements. For example, a car manufacturer has requirements for an electric car battery that is half the weight of current batteries with 20% more range. In this example, an agile project might be the way to go to try out new chemical and manufacturing processes.

(On the other hand, agile isn’t as good a fit when the requirement is to produce a chili pepper that is tasty but not hot. You need to plan to determine who your target market is. More planning, in the form of market research, might be needed to determine consumers perceptions of tasty peppers and hot peppers. Because of this planning, a waterfall project might be the answer.)

  • Your organizational culture and expertise. Because of unknowns, R&D projects are typically complex and costly. Introducing a methodology that your organization isn’t familiar with will escalate that complexity. If you decide to use an unfamiliar methodology, start slow. If possible, try the methodology in a small area of your project. Consider bringing in experienced people to help. You can then expand the use of this methodology as you learn. Iin other words, start with the methodology you know and migrate to new ones as you gain experience.

If you work on R&D projects, I’d love to hear about the methodologies you use and any best practices you’ve learned. Share with us in the comments section.

For more about agile and waterfall methodologies, check out my Project Management Foundations course and Doug Rose’s Agile Foundations course.

Coming Up

My updated Advanced Microsoft Project has been published to the LinkedIn Learning library. This update is completely rerecorded with a new, comprehensive sample project. It is half as long as the previous edition because I took out all the topics I cover in my other Project courses. My humble opinion is that it is also more engaging, because of everything I’ve learned about recording videos in the past 8 years! Here is a link that lets you watch the course for free for the first 24 hours after you begin watching.

https://www.linkedin.com/learning/advanced-microsoft-project-22898395

_____________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 52,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.

_______________________________________

Tips for Supporting Stakeholder Needs

Tips for Supporting Stakeholder Needs

Producing a useful product is one aspect of successful project delivery. Considering the thoughts and feelings of stakeholders is just as important because it helps prepare stakeholders for accepting and using your deliverables. Here are four recommendations to help you support your stakeholders’ needs.

  • Find which business areas your project affects. Include specific tasks to research the tools, processes, strengths, and weaknesses of each stakeholder area. If you have access to business analysts, this is a great first assignment for them to tackle. If you don’t, the project manager should conduct stakeholder interviews to collect this information. What you learn helps your project plan accommodate your stakeholders’ realities and prevent surprises during project implementation. You certainly don’t want your solution to make your stakeholders’ weaknesses worse.
  • Plan early exposure to the solution. You can generate ownership of the solution by letting stakeholders see early versions of your products. Encourage them to share feedback. They will be more confident when they take part in creating project outcomes. What does seeing a solution mean? Showing stakeholders anything that is an early view of an upcoming product or service: prototypes, business processes shown with sticky notes, early versions of IT user interface screens, or IT testing or design diagrams. Many project managers delay these activities because the solution may change. But that’s the whole idea of early exposure! Your stakeholder perspectives can be incorporated into your products to deploy positive changes. So, show the product early, even earlier than you’re comfortable with. You’ll increase stakeholder buy-in.
  • Identify business processes before committing to new tool deliverables. A risky way to run a project is to come up with what looks like a useful tool to build to help your business and move forward with a project to implement it. HOW and WHERE that tool could be used in your business should be analyzed first. Develop to-be business processes to figure out how your business could incorporate a new tool. Use those new processes to show stakeholders how the tool could create better outcomes. In short, if you want buy-in from stakeholders, create to-be processes first. Then you can start a new project to deploy the tool.
  • Let stakeholders drive project definition and organizational change. There are stories about the placement of new campus sidewalks. As the story goes, buildings were constructed and opened, and sidewalks were laid on the worn paths created by the campus’ occupants. This was better than laying sidewalks where designers THOUGHT people would walk. This is an excellent example of letting stakeholders drive change. Project teams are often guilty of thinking they know what stakeholders want. And they design projects according to that vision – often to catastrophic results. Letting stakeholders drive projects can build enthusiasm and help focus on what that stakeholders want changed or improved.

What other steps can you take to account for what stakeholders really want? Share your thoughts, questions, and anecdotes in the comments section.

For more about working with stakeholders, check out Natasha Kasimtseva’s Managing Project Stakeholders course.

Coming Up

  • Join Tiffany Uman and me on Wednesday, Oct 25, 2023 1:00pm MDT for our live broadcast “How to Provide Project Updates to Executives “. Your leadership team is not out to get you. That said, communicating with them effectively is essential, especially when providing pertinent project updates to drive the business forward. In this live Office Hours, Tiffany Uman and I will dive into the key DOs and DON’Ts for presenting updates to your leadership team with confidence and getting the buy-in you need. I’m excited to hear her advice about communicating project information to executives. Post your questions in the event comments or bring them to the live event!

Tiffany is a career coach, workplace expert, and fellow LinkedIn Learning instructor. Check out her course,  Nano Tips for Answering Common Interview Questions with Tiffany Uman.

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 51,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.

_______________________________________

How to write an effective project objective

How to write an effective project objective You may have defined a project with a set of scope statements. A better approach to defining a project is with a single project objective or goal statement. This statement focuses on the overall goal of the project, which helps obtain stakeholder buy-in. It also helps the organization focus on what the project’s supposed to do. Here are tips for creating an effective project objective statement. 

  • Keep scope definitions out of the project objective. You want the objective statement to be business oriented. What business change should the project achieve? Defining the project goal without scope does just that. It also creates organizational focus on what the project is supposed to achieve. Discussion of scope can follow later. At that time, you can confirm that the scope statements are appropriate to meet the project objective. 
  • Evaluate whether the objective statement clearly states the problem to be solved or the opportunity to be pursued. Make sure you have a clear statement about why the organization will pursue the project. Have someone – anyone – read the statement. The project purpose should be clearly understood, regardless of the reader’s role in the organization.
  • Confirm the statement’s ability to inspire. A project objective statement should inspire stakeholders to support the project. It should also excite project team members about participating to make the project objective a reality.
  • Verify that the statement presents an appropriately challenging goal. Stakeholders should see the objective as a challenge that will motivate and stretch their capabilities without being out of reach.
  • Ensure the statement allows flexibility for achieving the goal. In an agile world, the best approach is to let stakeholders determine the best ways to accomplish a goal. This generates the best solutions with the strongest stakeholder buy-in.
  • Include an objective measure of success. No goal is valid without a clear (quantitative or qualitative) way to identify that it has been achieved. An effective objective statement includes a clear way to confirm that the objective has been met.
  • Examples
    • Reduce aircraft costs by 15%, increase overall aircraft availability by 10%, and increase aircraft mechanic productivity by 25% measured by time spent on mechanical work versus overhead.
    • Design and implement hospital diagnostic capabilities to accommodate a 15% increase in patients, while limiting the increase in investment in diagnostic equipment to no more than 10%. (Notice this statement does not say “redesign” as this would limit the options available to the project team. This gives them the option to add a new diagnostic area if that is the best option.)
    • Increase consumer product division profits by 15% and increase market share over 2023 levels through new packaging, new products, or other approaches. (This does limit options to a specific area of the company, but that’s reasonable as that is where the concern for profitability and market share lies. Flexibility as to the approach or scope of activities is supported in this project objective statement.)

If you have other tips for writing an effective objective statement or examples of statements you’ve used in the past, share with us in the comments section.

For more about writing powerful objectives, check out Jessie Withers Goal Setting: Objectives and Key Results course.

Coming Up

My updated Advanced Microsoft Project has been published to the LinkedIn Learning library. This update is completely rerecorded with a new, comprehensive sample project. It is half as long as the previous edition because I took out all the topics I cover in my other Project courses. My humble opinion is that it is also more engaging, because of everything I’ve learned about recording videos in the past 8 years! Here is a link that lets you watch the course for free for the first 24 hours after you begin watching.

https://www.linkedin.com/posts/bonniebiafore_my-updated-advanced-microsoft-project-has-activity-7120114915880701953-wD1I?utm_source=share&utm_medium=member_desktop

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 51,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.

_______________________________________