Posts

From Newbie to Know-it-all

/in , , , /by

technology expertI knew nothing about Project, QuickBooks, Visio, Basecamp and other tools when I started. I was a project manager and business owner faced with complicated tools I needed to do my jobs. Here are the techniques I use to master software quickly:

Take classes: Take more than one. Different teachers cover different topics and might provide great tips you haven’t heard anywhere else. Students learn in different ways – listening, watching, doing, and so on —  so it’s important to find an instructor who teaches in a way that resonates with you.

Read a book or two: If you’re really serious about mastering a product, get a book about it. Books can go into a lot more detail. Plus they have indexes to help you find topics and paper books are easy to flip through. eBooks are easy to search.

Read blogs about the product: Whether it’s the product blog or a blog from another organization, you can find incredibly helpful information there.

Search help: But don’t start in the in-product help. Use your browser and try different combinations of keywords or phrases. You’ll find results from product help but also from numerous other sites. Those other sites often have more detailed answers and great troubleshooting tips. Click the results that sound most like your question. If you don’t find an answer, click other results or try new keywords in your search. I have a very old HP LaserJet printer that works like a champ. I followed many links and eventually found info on the driver I needed to get the printer to work with Windows 10 – buried deep within HP help.

Post questions in product forums/groups: Product-related groups on LinkedIn, forums on the product website or forums hosted by other organizations have lots of knowledgeable people willing to share their expertise. You’re more likely to get helpful answers if you describe your issue in detail. Include the steps you took, what you expected, and what happened instead.

Explore on your own: Poke around the software. Try things. Test what happens when you perform different steps or use different software options. Use sample files to experiment. The more you do this, the better you’ll get at discovering things on your own.

Note: It’s tempting to immediately jump to asking an expert for an answer. That’s reasonable when you’re facing a tight deadline. However, you’ll learn and remember more when you expend some effort finding your answer.

Check out my courses on Linked In Learning here.

This post contains affiliate links, and I will be compensated if you click my links and make a purchase.

#project, #quickbooks, #projectpointers, #bonniebiafore

 

Can you have too much authority as a project manager?

/in /by

Here’s another video Bob McGannon and I recorded where we talk about whether a project manager can have too much authority. We also talk a bit about what to do to make sure that the project manager and project sponsor agree on what is an appropriate level of authority.

https://youtu.be/uRyLRbJnh1Q

To learn more about project organizational structure, check out this video from my LinkedIn Learning Project Management Foundations course.

The Power of Out of Scope

/in /by

The most important section of the scope statement may be what’s out of scope. By discussing what’s out of scope, the project manager and stakeholders can refine their perception of the project’s purpose and how it will improve the business. This allows the project manager to focus the project team, and stakeholders who try to expand project scope. The out of scope section:

Demonstrates priority. Being specific about what is in and out of scope helps you get the best value by concentrating on the most impactful business outcomes.

Reduces scope. A smaller scope allows for more focused effort, a smaller team to manage, and less need for integration. These significantly reduce complexity and increase the probability of successful project completion.

Creates early debate. Proposing what is out of scope inspires senior stakeholders to express their views and discuss needed outcomes. These discussions ensure stakeholder support of the project scope and avoid delays later.

Reduces time and cost. Restricting scope reduces the overall project effort, reducing the cost and time to deliver project outcomes. Productive discussions about out of scope items can also help reduce scope if schedule or cost constraints surface as the project progresses.

When might you start a project without a business case?

/in /by

While I was in Australia, Bob McGannon and I talked about when, if ever, you would start a project without a business case. It was a fun discussion. Click here to watch!

Alexandria Bay

Can something be too small to need project management techniques?

/in /by

I spent some time in Australia with my good friend and project manager/LinkedIn Learning author extraordinaire, Bob McGannon. We talked about several interesting questions in the project management and leadership domain. Check out the video of our discussion!

How long can I live with project assumptions?

/in /by

How long should you proceed with your project without validating assumptions?

Assumptions about a product’s or idea’s marketability should be validated quickly. Money spent on a product with unvalidated marketability is at risk. Share product specifications, drawings, or a mock-up built with Legos, but produce a prototype to validate your product’s marketability.

Key stakeholder assumptions about funding or staffing should also be validated quickly. Get with your stakeholders early and convert assumptions into commitments.

Assumptions about the availability or capability of a product you need are sometimes critical to confirm, sometimes not. If the product is unique, confirm your assumption ASAP. If there are alternatives, the assumption can probably wait.

Assumptions about government legislation, licensing or approvals can be tricky.Often, they’re a make or break proposition for your project. Unfortunately, you only know what you’re dealing with after the government passes a law (or not) or grants a license. Plan your project around these approval events, and weigh the risks of working before you fully understand the government’s decision.

Assumptions about data being available to support your project is important to resolve early. For example, you might obtain a new software system that depends on critical data to operate properly. Purchasing that system before validating that the required data is available is VERY high risk. Determine how to obtain and determine the accuracy of that data as soon as possible.

Project assumptions can be broad and varied. What inaccurate assumptions have you heard about that created issues? Share those in the comments section so we can all learn together!

What should you do if you don’t agree with the project business case?

/1 Comment/in /by

The answer depends on what makes you uncomfortable.

The project business case forms the basis of the project. Get it wrong and the likelihood of a successful project is low.

If you believe the business case data lacks integrity, discuss this with your sponsor immediately. Contrast your information with what’s in the business case and work through the differences. The business case sets expectations, so you’ll eventually need to compare project outcomes against the business case. Don’t wait until the end of the project to challenge the business case. Take action now!

If you’re concerned with risk in the business case, seek to understand your sponsor’s risk profile. As a project manager, part of your role is to ensure your sponsor and key stakeholders understand the project risks. Your role is NOT to ensure risk goes away, When you’re concerned with business case risk, point out the risks to stakeholders and establish response plans. When you understand the risks your sponsor is comfortable and uncomfortable with, you can perform risk management effectively.

If the business case was not built collaboratively, review the business case with key stakeholders. They usually focus on their own interests and perceptions of risk and may be uncomfortable with the business case or its approaches. Discussions to analyze and align the business case with key stakeholders are critical. Moving forward with a business case that hasn’t been reviewed and agreed upon makes it difficult to get staffing and decision-making support.

Proactively addressing issues in the business case will help you deliver your project successfully as well as establish your authority with project stakeholders.

What if the sponsor doesn’t want a feasibility study – they want a 100% guarantee!!!

/in /by

Projects are risky by definition! You are trying to create something that has never been created before. Some executives find this uncomfortable and request a feasibility study to determine whether the project is viable. It’s a smart thing to do: it helps you build a good initial scope statement and project charter. However, if the feasibility study is supposed to create certainty about the project outcome – meaning no risk – you’ve got a problem. Here are some tips if you find yourself in this situation.

  1. Focus on creating a risk plan and sharing it enthusiastically. This may seem a bit counter-intuitive. You have executives who don’t want risk, and the advice is to shove a risk plan in their face! The fundamental truth is that projects involve risk. Embrace that! Presenting a methodical way to approach risk is the best way to balance the reality of those risks with a sense of control.
  2.  Package your project approach as a story. When your executive sees how the project can come to pass via a believable story, you can ease their fears and allow a reasonable project to move forward.
  3.  Focus on the steps in your plans and how you can validate each step as they occur. Executives often fear that they will lose control and incur large expenses or delays. Building sound plans and project controls can ease your executives’ anxiety. Make your sponsor comfortable that they will have control over the project and can act proactively if things go sideways. Doing so will put your sponsor, yourself and your organization in a much better position to deliver a viable project.
  4. Understand your sponsor’s greatest concerns and communicate status about those concerns. If they are concerned about spending, create as detailed a budget and spending plan as you can and review status regularly. When the status isn’t good, report it quickly  — along with actions that can be taken. Ensure a sense of control and understanding is present regarding your project, and you and your sponsor are more likely to work together to produce great project outcomes.

Top 5 Project Management Skills You Never Knew You Needed

/in /by

As a project manager no two days are the same. Business changes, project dynamics, and the myriad stakeholders you deal with are just the beginning. For daily entertainment, here are a few additional project management skills you must develop and deploy to be effective:

  1. Storyteller – Effective conversations and project documentation are the beginning of your project story. What you really need is vivid communication–the story of how your project can progress from idea to reality. Senior leaders need reassurance, often in the form of hero reports and processes that save the day. Practice telling the story of your project. To be certain your story will sell your senior leaders, make it part Marvel action movie and part warm snuggly lullaby. Do that, and you’ll be in your project’s driver’s seat.
  2. Non-insulting Consultant – One of the more challenging things a project manager does is turn away work. That’s right – you have to say no to some project assignments. Pet projects, impractical projects that sponsors erroneously assume employees will buy into, and other unrealistic project concepts will cross your desk for justification. When you find yourself in this position, you need to put on your consulting hat and convince your enthusiastic sponsor their idea won’t fly. You have to be firm and direct and, at the same time, avoid insulting them. Take the approach of steward of your sponsor’s business and assure them that your job is to protect them from issues that impact the bottom line. Consider telling a good project horror story (see item 1).
  3. The Battle-revealer and Peacemaker – Your project sponsor may be totally convinced about a project, while other key stakeholders think differently. Finding those not-so-on-board stakeholders and revealing the battle that needs to be fought is critical for success. Otherwise, you’ll have one significant stakeholder tell you to go north while another tells you to go south. Good luck with THAT! Find the requirement and prioritization mismatches, get the combatants in a room, and help them clearly articulate their differences. You act as the peacemaker and look for compromise, if necessary. Then your life as project manager will be much easier.
  4. The Discoverer of wobbly truth – The people you need to work on your projects are almost always working on other things, too. (If you run a project with 100% dedicated resources, you haven’t experienced the full fun of being a PM!) Your project team members are juggling things and almost always underestimate. They try to be diligent, but they’re usually optimistic about what they can produce, in quantity and quality. Gently and compassionately, you need to find the truth about what your project team can produce and the status of their work. Wobbly truth (a well-intended statement that isn’t a lie, but doesn’t turn out to be accurate) has spawned more nightmares than Dracula—at least for project managers. Be persistent and kind, but don’t stop poking until you get the truth.
  5. Executive Whisperer – Anticipating your sponsor’s reactions to project twists and turns is a useful skill. Even more important is understanding the fears that these project situations will awaken in your senior leaders. Understanding those fears helps you identify the information to share to either reassure them or give them clear options to help you address the concern. Executive whispering is best performed going into a project, when you can have a conversation with your sponsor and other stakeholders about the risks they are most concerned about and the positive outcomes they value most. That way, you can whisper to your senior leaders to help you guide the project and control their fears!