PMBoK7 Perspectives: Focus on Value

In this edition of Project Pointers, we’ll explore how project managers can focus on delivering value the business, one of the new elements of project delivery in the Project Management Institute’s seventh version of the Project Management Body of Knowledge (PMBoK7.) Here are a few significant ways to deliver value to your business as you manage projects. 

  • Focus on your approach, not just outcomes. The way project managers deliver their projects can be as important as the outcomes they deliver. Many projects are disruptive because they take operational leaders away from their day-to-day duties. Project managers who focus on value consult with the business regarding the scheduling of work. When deadlines are in jeopardy, they strive to understand business circumstances. For example, project team members may be temporarily called away to address an urgent situation that’s a higher priority than the project. Considering this, project managers keep stakeholders apprised of project status and listen when concerns are raised. The business will be more likely to engage in future projects when there is a focus on professional project delivery throughout the project lifecycle, as well as the outcomes projects produce. 
  • See value as qualitative and quantitative. PMI defines value as “the worth, importance or usefulness of something.” It’s important to understand that stakeholders’ assessment of the value of “usefulness” involves a lot more than how deliverables satisfy a business case. Value is determined by how deliverables support familiar processes and are integrated with tools and downstream processes, much more than what balance sheets show. The difference between a deliverable and a solution is how stakeholders accept it as part of their daily routine. You contribute value when deliverables are viewed as a solution.
  • A valuable project is only the beginning. Project delivery that embraces value leads to – more projects! Value received inspires confidence and generates more ideas for business improvement. These may generate project change requests to add scope, which can add value (as well as introduce risk.) Great project managers discuss how to maximize value, either by incorporating the change request or staging the request for phase 2 of the project. And they learn from those requests how to design downstream projects to deliver further improvements. In that way, delivering value is the start of an improvement journey, not the end.
  • Value supports strategy. The way projects are delivered can support or detract from corporate strategy. For example, a new business application could rely on an existing technical platform, or it can take advantage of a new architecture that is part of the corporate strategy. In a different context, a building may be constructed with sustainable principles in mind, utilizing clean energy and eliminating waste. Though it may be more difficult to support strategic initiatives, good project managers work with their teams and senior stakeholders to guide their projects to satisfy the short- and long-term goals of corporate strategies.  

If you have suggestions for focusing on value in projects, share with us in the comments section.

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

Coming Up

Recording for Project 2021 and Project Online Desktop Client Essential Training is complete. Look for the course to be published in a few months.

PMBoK7 Perspectives: Creating a Collaborative Team Environment

Photo by Randy Fath on Unsplash

In this edition of Project Pointers, we’ll look at building a collaborative team environment, one of the new project delivery elements in the Project Management Institute’s Project Management Body of Knowledge (PMBoK7.) Here are a few ways to create a collaborative team environment for your projects.

  • Define roles, not just responsibilities. Productive teams have clear roles and approaches, which can be defined by the project manager, team leader or the team themselves. Team members need to understand their roles, so they know where each person’s responsibility begins and ends, and how information or process steps will be passed from one person to the next. For example, “perform testing” describes a responsibility. That isn’t enough for someone to understand the role. Are they supposed to test a product at various points as it is built, or only the end product? Do they perform testing themselves or include a customer or end user? How and where will the test results be recorded and shared?
  • Organize sub-teams. Often, the best way to tackle a set of tasks is with a small group of people. Define sub-teams and identify who will coordinate the team’s efforts to share status with the project manager. This isn’t necessarily a team leader, but rather the person who will ensure proper coordination and communication as the sub-team performs its tasks. To reinforce collaboration, recognize the entire sub-team when items are completed, not just the team leader or coordinator.
  • Establish support and review standards. Teams that produce outstanding work use the collective experience and expertise of its members. Leverage that with a peer review process to assure deliverable quality. The peer review process is not to find fault, but to identify ways to produce superior work. To reinforce this approach, recognize both the individual who identified an improvement and the person who adopted the improvement into their deliverable. This supports a team environment where collaboration is recognized.
  • Focus on communication approaches. The larger your team, the more communication processes need to be defined and followed. This used to be straightforward, when periodic meetings would be scheduled in a conference room. This isn’t as easy today when team members work from offices, homes, and other locations. Different tasks and reporting requirements necessitate different communication mediums. For example, reporting task completions can be done via a virtual meeting tool. Reviewing a complicated technical deliverable requires rich communication that’s beyond the average person’s and work location’s capability with virtual meeting tools. The lesson here is twofold. First, pick the communication medium based on what the meeting needs to accomplish. Second, understand each team member’s capability with virtual tools when face to face meetings aren’t feasible. Make sure well-trained team members can put the full capabilities of virtual tools to use. 

Do you have any tips on building a collaborative environment? If so, share with us in the comments.

For more about team collaboration, check out Dana Brownlee’s Essentials of Team Collaboration course and Communication within Teams by Daisy Lovelace.

Coming Up

Recording for Project 2021 and Project Online Desktop Client Essential Training is complete. Look for the course to be published in a few months.

PMBoK7 Perspectives: Be Adaptable

Being adaptable as you manage your projects can support the success of your projects, a new element of project delivery in the Project Management Institute’s seventh version of the Project Management Body of Knowledge (PMBoK7.) Here are a few beneficial ways to be adaptable as you manage projects. 

  • Don’t fixate on perfection. It would be nice to build a perfect plan with accurate estimates and task dependencies, but it’s not realistic. Instead, work on learning as your project progresses and being adaptable to change estimates and plans as events unfold. Change isn’t admitting you’re wrong! When proposing project plan changes, skilled project managers share what they’ve learned to educate their management teams. It’s far better to proactively change plans, rather than try to meet planned expectations that are now impractical or high-risk. In estimating, the focus should be on being “less wrong” as your project progresses and you can use new insights to construct better estimates and plans.
  • Watch and respond to your organization’s direction. Projects are launched to change capabilities for an organization and/or its customers. However, organizations aren’t static while projects progress. Circumstances can affect how the project fits into the organization’s direction. Projects may be postponed, slowed down, team members swapped, or project outcomes may need to be brought forward. Great project managers don’t wait until they’re told to alter a project’s direction. They watch what is happening in the organization and draft what-if changes to project plans for presentation to management. The adaptable project manager responds, versus reacts, to changes in the business. 
  • Launch open-ended organizational conversations. Great project managers develop ideas about how to deliver a project. And they are adaptable to the desires and ideas of key stakeholders. They initiate conversations with and between those key stakeholders to discuss approaches for delivering the project and they present their ideas in those conversations. They combine their ideas with ideas from stakeholders that hold merit and support the needs of the business. You might be nervous about conversations without knowing where they might lead, but the long-term outcome of collaborating and adapting to pragmatic stakeholder project delivery desires can outweigh those risks. 
  • Defer decisions. Better decisions are made when more information becomes available. Although waiting to set a direction can be stressful, delaying a decision can be the best way to adapt to some project situations. For example, your vendor may be coming out with an updated version of their product, but the release date isn’t finalized yet. Rather than gamble on using the new version or creating solid plans to use the current version, set the software decision point as late as possible in your plans. When your decision point arrives, you can use up-to-date information about the release to decide.  

How has being adaptable contributed to the success of your projects? Share your experiences in the comments section.

For more about adaptability, check out Dorie Clark’s How to Be an Adaptable Employee During Change and Uncertainty course.

PMBoK7 Perspectives: Apply Expertise

Photo by Jose Aljovin from Unsplash

Today, we’ll explore how project managers contribute benefits with their expertise, one of the new elements of project delivery in the Project Management Institute’s seventh version of the Project Management Body of Knowledge (PMBoK7.) Here are a few significant ways to apply your expertise in managing projects:

  • Complete project tasks. Most project managers have technical and industry expertise relevant to their projects. Completing technical tasks can be an appropriate and helpful contribution to the projects we manage (although it isn’t the project managers primary role.) But you shouldn’t take opportunities away from other team members, which they might perceive as restricting their growth.  
  • Coach your team members. The best project managers increase the capabilities of their team members who work on their projects. They provide technical guidance without dictating how to complete tasks. They also help others understand the practice of project management, so they can contribute to building work breakdown structures, verifying estimates, and confirming schedules. Because projects often have wide-ranging business implications, they coach people on business elements as well, such as communication, presentation skills, and managing risk.
  • Improve the practice of project management. Project managers are known for getting things done. They bring confidence to their management team that envisioned changes will come to fruition via the application of sound project management tools and perspectives. Applying your project management expertise can help improve your organization’s project management practices. Spreading the word about project management practices is an effective way to support your business. Guiding managers as they work with you to deliver projects is another impactful way to apply expertise and increase your business’ project delivery capability.
  • Provide perspectives for management. Respected project managers can help management understand which approaches to facilitating organizational change will be supported by line managers and which ones won’t be! Project work provides project managers with a view to how operational management handles the pressures of increased workload created by supporting projects. Project managers know who responds well, who doesn’t, and which competing workloads might interfere with project progress.

Have you contributed your expertise to your projects in other ways? If so, tell us about it in the comments section.

For more about project management, check out the Become a Project Manager learning path.

PMBOK7 New Perspectives: Caring Steward

In this edition of Project Pointers, we’ll look at the project management standard of being a caring steward, one of the new elements of project delivery discussed in the Project Management Institute’s latest version of the Project Management Body of Knowledge (PMBoK7.) In PMBoK7, Knowledge Areas are replaced with Performance Domains, which recommend additional activities in several areas, including adding project value. Let’s look at ways in which you can be a caring steward while managing your projects. 

Acting with care. A caring steward behaves as if they own the business and all the outcomes the business produces. In a project management context, a caring steward goes beyond managing the schedule and ensuring success criteria are met. It means treating project stakeholders with respect, managing all impacts on the physical environment (such as deploying conservation measures), and ensuring proper disposal of used assets like old computers. A big part of acting with care is engaging in organizational change management to ensure people understand what their role is as project deliverables are released. That way, they are put at ease as the processes they use in their work are enhanced.

Financial control. Financial stewardship is a fundamental responsibility for a project manager. This stewardship goes beyond ensuring project costs are within plan. It includes analyzing how to best use finances to support business goals. For example, it may mean spending more in the short run to save money in the longer term. An example of this is when a vendor announces special pricing for a volume purchase. While purchasing in volume might not have been in the project plan, a good financial steward will examine the advantages and disadvantages of making this volume purchase. Good stewardship also means assessing upcoming planned spending to make sure it’s still reasonable and in the best interest of the business, and constantly reviewing risk mitigation and contingency dollars to determine whether they should be adjusted up or down.

Appropriately exercising authority. Project charters identify the level of authority given to project managers. Caring stewardship involves applying that authority appropriately, such as not using coercion to get things done, not overstating one’s authority, or not exaggerating the project impact to influence others to perform work. The caring steward leads the project with compassion for the business, considers the project’s goals in relation to other initiatives, and acts with compassion while working with stakeholders.

Maintaining compliance. Business rules, project management methodologies and legal considerations should always be front of mind while project managers perform their duties. The caring steward understands the purpose and steps involved to be compliant and adheres to the compliance guidelines when making decisions – when it makes sense. However, caring stewardship doesn’t mean blindly executing processes. It is understanding the intent of those processes and proposing alternative actions when the processes won’t yield the intended results. For example, a standard deliverable in a project management methodology might not make sense for a given project. Rather than waste time producing a stripped-down version of that deliverable, the caring steward will work with management to forgo that deliverable for the project and seek to improve the project methodology to consider alternatives when the deliverable doesn’t make sense.

Have you come across other examples of being a caring steward? If so, join the conversation in the comments section.

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

Coming Up

I’m working industriously on updating the course Microsoft Project 2021 and Project Online Desktop Client Essential Training. With this update, I include additional homework for most movies so you can practice after following along during the video.

PMBoK7 Perspectives: Contribute Insights

In this edition of Project Pointers, we’ll explore the benefits of your project team contributing insights to your project, one of the new elements of project delivery in the Project Management Institute’s seventh version of the Project Management Body of Knowledge (PMBoK7.) Here are a few substantial ways to maximize project delivery by leveraging stakeholder insights.

  • Leverage team member experience. Even the most experienced project managers can learn more to help their projects succeed. Project leadership requires a lot of listening and learning. Team members have experience that helps them build a solid work breakdown structure, identify risks and determine risk responses, manage issues, and test products. Technical team members can also help avoid over-complicating project solutions. Tapping team experience helps maximize success and increase team buy-in!
  • Team up with key business stakeholders. Business team members provide insights to improve outcomes and enhance project delivery. They can also help avoid pitfalls and identify change management approaches to smooth transitions during project deliverable deployment. Engaged business representatives identify hot buttons that may negatively affect the opinions of influential stakeholders, so you can address those issues and protect the success of your project delivery. These critical insights surface you create a team atmosphere, where business and technical experience are valued. The best decisions are based on a broad set of shared experiences.
  • Capitalize on change agents. Change agents can improve your chances for success. Great project managers seek out change agents and involve them in project planning and delivery. The trick is finding the best change agent candidates, because they aren’t always the managers or team leaders that appear on the organization chart. How do you identify these change agents? Listen and watch carefully when requirements are collected. Who speaks up? Who do others look to for agreement? Identify the authors of substantial documents that have been provided. Find these promising change agents and invite them to coffee to do some change agent recruiting!
  • Collect project experiences. People who have participated in past projects can provide a wealth of valuable insights. They can provide the actual level of risk the organization accepts, which key stakeholders are short-term money focused, who will insist on including certain tasks or verification in your project planning, and who is likely to come up with new requirements after the project begins. These bits of critical information save time and frustration! Take time to pick project veterans’ brains. You’ll be happy you did!

Have success stories and anecdotes related to obtaining insights from team members? Share them in the comment section!

For more about working with your project team, check out Daniel Station’s Project Management Foundations: Teams course.

Coming up:

Bonnie Biafore and John Riopel will talk about how to manage dependencies, meetings, and overall communication in hybrid projects on February 17, 2022, at 1PM MT. Traditional and agile/iterative project management approaches have similarities and differences, so you might wonder how to manage hybrid projects that use both. Although the approaches differ, there are points within a hybrid project where deliverables need to align. For example, a traditional deliverable must be completed before part of the agile effort can start – or vice versa. Even in hybrid projects, the project team is a single team that needs good communication and occasional team-wide meetings to make sure the project is successful.

PMBOK 7 Perspectives: Tailoring Your Project Approach

In the Project Management Institute’s latest version of the Project Management Body of Knowledge (PMBoK7,) the section on tailoring recognizes that project management isn’t one size or style fits all. Tailoring means that you tweak your project management approach, governance, and processes to your organization’s environment and work at hand. In this edition of Project Pointers, we’ll look at organizational factors that should drive project tailoring. 

  • Use familiar methodologies (most of the time.) Deploying a new methodology takes time and practice. In most cases, familiar methods for project design and delivery will yield the best results. When possible, stick with what your team and management are used to.

That doesn’t mean you should never try other methodologies. Introduce them on small projects that aren’t critical, where you can afford to stumble for the benefit of education. Most organizations that have succeeded with agile started small and adapted the approach to leverage its benefits while avoiding its pitfalls. Over time, they became comfortable with agile methods, developed foresight to avoid problems, and obtained the speed and responsiveness agile provides.

  • Accommodate the business’ risk appetite. Although all projects introduce risk, the degree of risk within any given project should reflect the risk tolerance of your business. Businesses with small profit margins or in highly-regulated industries where new approaches require government interpretation and new rulings might not support a risky project. Conversely, small businesses in a highly innovative market might demand fast technological leaps from their projects, which are inherently high risk. 

Tailor your management approach to take into account the project objectives and risk tolerance of your business. Aggressive timelines and new technology are appropriate when higher business risk is acceptable. If you need to reduce risk, use known approaches, conservative timelines, and sufficient time for planning and market testing. 

  • Consider the depth of your customer relationships. Considerable project tailoring may be required based on the relationships you have with your customers and how familiar your customers are with your products and services. If you know your customers and their business processes, you might plan fewer activities to confirm requirements and verify solutions. Conversely, with a new market segment, you should plan for more market analysis, requirements validation and product verification. Whether you are adding an enhanced product to a respected product line or entering a new market with a brand-new offering, tailor your standard project planning and delivery approaches to match. If in doubt, plan more verifications with your customers – you and they will appreciate it! 
  • Be mindful of the pace of change. The pace of change your business and your customers can handle is a significant factor in how you tailor your project and its deliverables. You may be better off delivering your project in small phases if your stakeholders are already dealing with a lot of change. On the other hand, if you need to leapfrog a competitor, moving fast with a significant change may be required. The nature of your business will also impact the pace at which you introduce change. A public utility company needs to be cautious and deliberate to protect vital infrastructure, whereas a web technology company can introduce change very quickly, assess the results and roll back a change with little to no impact. Adopt to the pace of change your business can handle, as it can be the difference between success and complete failure of a project.

For more about project management methodologies, check out Cyndi Snyder Dionisio’s Hybrid Project Management: Do What Works course.

Coming Up: 

Bonnie Biafore and John Riopel will talk about how to manage dependencies, meetings, and overall communication in hybrid projects on February 17, 2022, at 1PM MT. Traditional and agile/iterative project management approaches have similarities and differences, so you might wonder how to manage hybrid projects that use both. Although the approaches differ, there are points within a hybrid project where deliverables need to align. For example, a traditional deliverable must be completed before part of the agile effort can start – or vice versa. Even in hybrid projects, the project team is a single team that needs good communication and occasional team-wide meetings to make sure the project is successful.

PMBOK7 Perspectives: Analyzing Stakeholder Attitude

In this edition of Project Pointers, we’ll look at stakeholder attitudes, one of the new approaches to analyzing stakeholders in the Project Management Institute’s latest version of the Project Management Body of Knowledge (PMBoK7.)

In PMBOK7, Knowledge Areas are replaced with Performance Domains, which recommend additional activities in several areas, including stakeholder analysis. Let’s look at challenging stakeholder attitudes and responses that increase your success in stakeholder management.

  • Inattentive/indifferent. Key stakeholders can behave as if they don’t care about the project or its outcomes even if they would be positively or negatively impacted by those outcomes. They might not pay attention due to their workload, business issues, or other distractions. Remember, your project isn’t the only thing on the stakeholder’s plate.
    • To gain the attention of a distracted stakeholder, talk to the stakeholder’s peers and support staff to find ways to engage the stakeholder.
    • Use clear and persuasive graphics or flowcharts to show how the project might impact the them. Share this information with the stakeholder’s department.
    • Demonstrate that the stakeholder needs to decide between the alternatives by a specific date. Clearly communicate that the project team will make the decision if the stakeholders doesn’t respond by that date. This approach doesn’t guarantee a response from the stakeholder, but it typically gets their attention. If the stakeholder disagrees with your choices, you have documentation that they had an opportunity to make the decision and opted not to.
  • Fearful. Stakeholders who fear negative project outcomes are challenging to manage. Their past experiences may have been bad. Fear can manifest through micromanagement, requests for overly-detailed status reports, and drawn out decision-making.

Talk to your stakeholder to understand their concerns. You may have risk mitigation plans in place that address their fears. Communicate your plans, or create new risk items, and obtain the stakeholder’s approval for the mitigation and status sharing strategies should their concerns come to fruition. You might reduce their fear by demonstrating that you understand their concerns and have plans to address them.

  • Demanding and self-centered. All stakeholders are affected by the project by definition. Some stakeholders act as if they are the only project stakeholder. They place demands on the project without regard for the needs of other project stakeholders. If the demanding stakeholder is your sponsor, that is likely their prerogative. If not, emphasize the other project requirements you are managing with this stakeholder. If they continue to show no regard for other stakeholders, get your sponsor involved to negotiate with this demanding stakeholder. (Remember, the project sponsor is responsible for the project and its outcomes, and wants to see the project succeed.) The sponsor can then help you reprioritize the project requirements. At that point, you can cite the sponsor’s directions when you deal with the demanding stakeholder.
  • Wheeler/dealer. Stakeholders might offer funding or resources for a project in a bid to get their desired outcomes added to a project. They might be extraordinarily persistent! This can seem like a variation on the demanding stakeholder in the previous point. You might consider asking them to work with the sponsor to prioritize their outcomes. It might make sense to introduce new requirements or reprioritize requirements in exchange for benefits. For that reason, the best approach is to handle these proposals through your standard project change management practices.
  • Indecisive. Slow decision-making by stakeholders impacts project schedules — and cost when resources assignments must be extended. Being proactive is the best way to address this situation. Major project decisions have to be made after stakeholders consider the pros and cons of alternatives. Include a specific task, assigned to the sponsor or key stakeholders, delineating the decision to be made and the time allocated for them to research and consider their position. In addition, calculate and communicate what it costs for each day that the major project decision is delayed. This can help illuminate highlight the impact stakeholder indecisiveness has on your project. You can also use this information to create a project change request to alter the project schedule and budget due to the decision-making delays.

Have experience with any or all of these stakeholder attitudes? If you have insights and suggestions for dealing with them, add them in the comments section.

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

Coming Up

Bonnie Biafore and John Riopel will talk about how to manage dependencies, meetings, and overall communication in hybrid projects on February 17, 2022, at 1PM MT. Traditional and agile/iterative project management approaches have similarities and differences, so you might wonder how to manage hybrid projects that use both. Although the approaches differ, there are points within a hybrid project where deliverables need to align. For example, a traditional deliverable must be completed before part of the agile effort can start – or vice versa. Even in hybrid projects, the project team is a single team that needs good communication and occasional team-wide meetings to make sure the project is successful.

Less Well-Known Benefits of Integration Management

Photo from collectspace.com

Integration management ensures project planning elements are connected properly, regardless of the methodologies being deployed. Here are some other benefits of integration management you might not have thought about:

Ensures accurate status reporting. A well-integrated project plan ensures that status changes are properly reflected throughout the project, no matter where those changes originate. For example, if you mitigate the risk of cost overruns by reducing the use of contracted skilled resources, tasks might take longer, impacting the project schedule. Other skill-related risks could become more likely. Also, product quality may decline. Impacts to the project often extend beyond one element. Sound integration management ensures you have a complete picture of the status of your project. 

Reduces stakeholder conflict. Project managers need to ensure stakeholders understand their obligations to the project. As new ideas or questions arise during the project, stakeholder obligations can change. Performing integration management ensures changes in obligations are identified early. That prevents conflicts later in the project when the pressure is on and project impacts are more significant.

Here’s an example. After your initial requirements are drafted, your contracts team notices that a vendor’s costs will increase considerably because of new demands from your project. To address this, your organization decides to perform the work in-house. This impacts project stakeholders through workload, cost, and schedule. Although it may be the best solution, sound integration management ensures that stakeholders understand the new project projections and workload impacts. That way, they can negotiate with project sponsors to seek other solutions or agree and respond to the new workload. 

Helps you manage in a virtual world. One of the greatest virtual team risks is increased errors in communication or process. In one example, Team A uses metric measurements and a geographically separate Team B used imperial measures, generating costly errors. Although integration doesn’t guarantee error-free processes, integration management activities do reduce risk. Integrated plans and integrated processes help your virtual teams work in lock-step.

Helps you produce accurate project plans. Ensuring that all project planning elements are properly integrated is a great way to ensure a sound project plan. Have you added a risk mitigation strategy in your risk plan but forgot to add budget for it? Have you added tasks to fulfill your quality plan but neglected to add them to your project schedule? Focus on integration management and you are unlikely to see omissions in your plans. Project planning deliverables will be complete, which helps deliver a successful project! 

Do you have examples of integration management providing project benefits? Share them in the comments section.

For more about integration management, check out Oliver Yarborough’s Project Management Foundations: Integration course.

Coming up:

Don’t miss Bonnie’s first LinkedIn Office Hours session of 2022, Leadership is Job One for Project Managers, at 1pm MT, January 25, 2022. Bonnie and bestselling project management author Eric Verzuh will talk about how shifting your focus to project leadership has a direct impact on project value. Bring your project management questions to this session.

Bonnie Biafore and John Riopel will talk about how to manage dependencies, meetings, and overall communication in hybrid projects at their LinkedIn Office Hours session, Managing Dependencies in Hybrid Projects, on February 17, 2022, at 1PM MT. Traditional and agile/iterative project management approaches have similarities and differences, so you might wonder how to manage hybrid projects that use both. Although the approaches differ, there are points within a hybrid project where deliverables need to align. For example, a traditional deliverable must be completed before part of the agile effort can start – or vice versa. Also, even in hybrid projects, the project team is a single team that needs good communication and occasional team-wide meetings to make sure the project is successful.

Less Well-Known Benefits of Scope Management

Scope management is all about ensuring your project produces what is required — and only what is required — to satisfy project objectives. It also delivers additional benefits you don’t often hear about:

Helps manage risk. Talk to an experienced project manager and you’ll likely hear a hard-earned lesson: the bigger your project, the riskier it becomes. For initiatives that require a lot of organizational change and project deliverables, you can break down scope into phases to make things more manageable. This breakdown into smaller chunks reduces risk and makes it easier for the organization to absorb the changes because they are applied in progressive steps. In many respects, the most effective way to manage project risk is to work closely with your stakeholders to manage scope.

Expands understanding of business requirements. Scope management is best performed through conversation. And conversation not only helps the project team understand business needs, but also helps the business recognize what is straightforward and what is difficult for the project team to produce.

In addition, good scope management means prioritizing requirements. This helps the project team understand what’s vital to the business and can enhance the business’s perspective on its own requirements! So, the business and the project team are better positioned to produce what’s most important, reducing scope and risk.

Builds confidence in the project. Detailed conversations about scope, including well-crafted questions to gain detailed understanding of business needs, can help build stakeholder confidence in the project team’s ability to meet its objectives. Good questions that inspire analysis and understanding of business needs can build trust that the project team knows what needs to be done. And starting off a project with trust from business stakeholders is a big plus.

Helps adapt to available resources. Skill shortages are everywhere and have been amplified by the impacts of the Covid pandemic. Scope management helps everyone be realistic about what can and cannot be done. Discussions about available skills help craft a realistic project schedule. Scope and resource management drive productive discussions about prioritizing work, particularly for scarce resources. The earlier these conversations and prioritizations are made and understood, the easier it will be to build a sound schedule and proceed through the project lifecycle.

Have you obtained other benefits from scope management? If so, share them with us in the comment section.

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

Coming Up

Don’t miss Bonnie’s first LinkedIn Office Hours session of 2022, Leadership is Job One for Project Managers, at 1pm MT, January 25, 2022. Bonnie and bestselling project management author Eric Verzuh will talk about how shifting your focus to project leadership has a direct impact on project value. Bring your project management questions to this session.