Skip to main content

Tag: Project Management

5 Key Reasons Why Some Projects Succeed and Some Don’t

It is just a fact in the project management world – some projects succeed, and some don’t.

Many studies place project failure – to some degree or another and by someone’s standards somewhere – at between 56% and 74% of all projects. I have also seen a couple of more optimistic surveys putting the success figure at closer to 54%. Still, none of those figures make any of us feel warm and fuzzy about our chances at project success. We all know that we tend to cut corners or that our methodology or process may not be the best. It is like continuing to eat fried chicken when your doctor tells you to stop for your health. We often still like to stick with what we feel comfortable with even if we know it could have (not definitely will have) negative consequences at some point later than tomorrow or next week.

That said, let’s look at five key areas that loosely fall under the logical concept of project management best practices that can, when practiced regularly and thoroughly, logically lead to better project outcomes.

1. Proper Planning

Proper upfront planning is always going to be a critical best practice that leads to project success more often than projects that lack the proper amount of planning. What is the right amount of planning? There is no yardstick for this, but it involves a combination of detailed requirements planning and documentation, setting up a proper way to regularly manage project financials and resource supply, risk and issue management, and of course, a planned and keen oversight of project scope and change control. Communication is the #1 responsibility of the project manager and helps everything else go much more smoothly. That is why I also consider a project communication plan – whether it is a formal project deliverable or just a casual spreadsheet for everyone to review and post on his or her office wall – as something that should be sent out at the beginning of every project. Yes, it is part of the planning process and ensures that everyone on the project knows who is responsible for what communication, how to contact all key stakeholders through just about any means possible, and when, where and how the regularly scheduled project meetings will be happening.

2. Close Budget Oversight

Close budget control is critical, but not practiced nearly enough. Involve the team and ensure the team is accountable for assigned tasks including the estimated effort, actual effort and the effort to finish tasks. If your team knows that you watch and manage the budget closely, then they are going to be more likely to charge their time to correctly to your project when working on multiple projects making it far less likely to charge junk time to your projects.

3. Project Team Ownership of Task

How do you get your project team to “own” their tasks assigned to them? Make them accountable for everything about those tasks. From defining them with you during project schedule planning work to tracking them while the project is in motion to reporting on their status to the project customer during weekly formal project status meetings. The sooner your can get your project team members assigned to their roles on the project, the sooner they can assist in the early project planning activities including the project schedule development and the individual task definitions and scope. Those are the tasks they will be assisting with and owning, and that planning phase helps them to feel and gain ownership of those tasks they will be working on soon and throughout the project engagement. It helps build in automatic ownership and accountability.

4. Error-Free Deliverables

Ok, perfection is not going to happen. However, you can certainly strive for it with your work and your team’s work on deliverables that go to the customer. Peer review everything to greatly reduce easily overlooked mistakes in project deliverables going out for customer review and sign off. Trust me – I know from personal experience that sending off the same great functional design document three times with errors still visible – even simply typos – can lead to a significant decline in customer satisfaction and confidence in yours and your teams’ ability to deliver quality. I corrected the problem – almost too late for one project – by requiring peer reviews by all project team members of everything that went to the customer. Everything (except for the basic communication emails, of course). Our problem was a problematic free PDF creation program, but it was sloppy for us not to be checking and just sending errors off for the customer to find. That should never happen on a customer deliverable.

5. Solid Customer Engagement

The engaged customer is the one that is available to exchange ideas, supply and receive information, provide critical input on key project decisions that need to be made and can clarify requirements or business processes on the spot when progress requires it. If the project manager can keep the customer focused more on your project than the hundreds of other things that are trying to take up his or her time, then you win that battle in making it easier to get quick info when the situation requires it. You will be able to make sure that the customer is sitting in those weekly project status meetings helping make next step plans when they come up. Win-win.

Summary/Call for Input

I could write on this topic till the end of time and never really pound home any real guarantees of project success – there are no guarantees. In the end, adhering as much as possible to logical best practices, repeatable successful processes, practices and templates, and trying not to just bring a project home on the wings of luck are your best way of ensuring project success.

What are your thoughts on this topic? What works for you? What has failed miserably? Please share your thoughts and experiences in the comments below.

Launching a Project? That Means You’re Launching Performance

Many capital projects, particularly in the infrastructure space, tend to start with some launch session billed as a partnering session.

It becomes an accepted standard practice, and that could be a problem.

When a project launch session is a box to check or a rote and familiar exercise, it probably isn’t adding all the value it could – not by a long shot. If you do not have very high expectations about how your project launch will impact your execution, you will likely have a launch session where people go through the motions so they can “get on with it” into the project work.

Jumping in this way, without a powerful initial alignment among all the key players, can have its consequences. In fact, in almost every struggling project, joint venture, or alliance my colleagues and I are brought into, we find ourselves rewinding the project team’s focus back to the beginning of the venture to sort out the issues and prejudices that weren’t sufficiently addressed at the start.

What kind of launch sessions have you been having? If they seem like business as usual, they probably are, and that will not add a lot or increase your chances for success. However, you can make the shift from moderately valuable launch efforts – which may not have a sustained impact – to highly powerful launch efforts with sustained impact into high performance. A strong launch effort is like any foundation you lay: the stronger the foundation, the more solid the structure.

A project launch that leads to high performance demands rigorous thinking and conversation. It is not about saying the “right thing;” it is about addressing the right things and having the real conversation up front. The top leaders of a partnership must align on what they’re aiming to accomplish on the project and how they will do it. That alignment begins with a clarity of vision for success where everyone wins.

Then you must answer the question: For everyone on the project to win, what will that require? It is fundamental and critical that people are strongly aligned on the answer to that question. Without this alignment, there is no high performance.

Identify Undisclosed Perceptions, Then Set Commitments

However, as important as this collective alignment may be – and as much as people may agree on this in theory – in reality, it is far easier said than done. So what gets in the way? I cannot emphasize this enough: Perception and interpretation win over reality every time regarding determining people’s actions and behaviors. All people (and project team members are part of “all people”) will behave consistently with their perceptions about the people they are working for and with, and about the prospects for the project they are working on. Moreover, these perceptions determine how people will act – very often remain unspoken. That is a problem because these undisclosed perceptions end up determining much of the project’s performance.

It is not uncommon to see a project get started with project team members withholding information important to project execution, posturing to put “a good face” on matters, and people operating from past-based fixed points of view about other key stakeholders. All of these things lead to a weakened project launch.

If you want a powerful start to your project, it is important to identify the mindsets, opinions, and prejudices that may be in the way of the project delivering high performance, and constructively challenge those mindsets, opinions, and prejudices. This type of authentic discussion about the concerns and interests of all the players creates an environment in which senior leaders can agree to a very clear set of commitments.

For example, my colleagues were called in to support a high-stakes oil and gas joint venture that was in danger of not meeting first-phase deadlines for engineering and construction plans – which meant a risk of the project not moving forward at all and millions in investment being lost. It did not take many conversations with the two lead partners to learn that they held conflicting perspectives about the all-important project schedule that were getting in the way. People on one side of the venture were making assumptions that the other side had built in “cushion” which made for unnecessarily tight deadlines, and the people on the other side were blaming their counterparts for not being responsive to requests to commit to those deadlines.

We helped this project team get those privately held perceptions on the table, where they could be challenged. That spirit of open challenge prompted people to consider other more constructive ways of seeing each other and the project’s future direction. With that change in perception among the team, the project soon turned around. It went from behind-schedule to early approval for construction; from low levels of communication to regular, candid updates about was working and what wasn’t; from siloed work channels to a strong, collective effort to rescue the project.

Create an Environment for Straight Talk

In the turnaround, I just described, once the people at the top understood the dynamic at play, they were able to create an environment for “straight talk” that established a new way of working across the enterprise. From senior leadership to the rank and file, people were equipped to effectively address issues as needed, and steer the project from a place of jeopardy to one of unprecedented success.

All of this happened because senior leaders began to operate in a new way driven by authentic commitments – along with straightforward updates on those commitments, and interventions as necessary to deal with what’s not working. In their new way of working, the straight talk was welcomed, respected and encouraged. It is inevitable that there will be problems, but it is never a given that those problems will be handled effectively. If during the launch phase of a project you develop a common language for talking with candor about what’s happening, your odds of reliably and successfully intervening increase dramatically.

Essential to this work is establishing a no-blame culture, with clear accountabilities and a work environment where the truth is told about what is and isn’t getting done – at all junctures of the project. In doing this work, have people adopt a rigorous relationship to their word so that commitments are clear and honored; this is key to high performance.

My colleagues worked with the leaders of an alliance building a $600 million highway bypass in Australia. There was a nearly impossible schedule to keep with a myriad of environmental and safety concerns, and none of the key players had ever worked in this kind of partnership before. While observers predicted failure, the leaders engaged my firm to help them build the groundwork for a project that would defy the odds. The project ultimately came in under budget and ahead of schedule, with award-winning quality results.

What happened to allow that performance? We helped the stakeholders to agree on a common language for leading and managing the project. In this launch stage work, they set the ground rules for everything from how concerns would be communicated to how leaders throughout the venture would promote an environment focused on results and accountability, not who might be blamed if something did not go right. It called for an investment of time and energy up front, then resulted in a return on that investment in the form of high performance that set a new bar for the region and the industry.

Build Out a Roadmap, So People See the Way

The launch work is not done until people can see the path beyond the launch. It is important to build out a roadmap for reaching your desired extraordinary goals that will in turn call for high performance. This roadmap lays out some key markers on the path to long-term targets; those markers represent key milestones and interim wins that help establish the pattern and rhythm of high performance.

The roadmap has the most power when people can connect what’s in it to what’s important to them and the broader venture. You can do this through a strategic cascade of commitments that draws a line of sight from the project’s highest level goals and strategic priorities to the actions of individuals and teams. When people have that line of sight, it can be the thing that keeps them motivated later – even inspired – especially when everything is not going perfectly, and the inevitable unexpected obstacles have to be addressed.

Finally, the roadmap will be most useful when it is integrated into your traditional project plan and planning tools. In that way, this powerfully integrated project plan includes all of the usual stage-gated technical activities, plus it also includes the project’s more aspirational goals and key milestones drawn through the strategic cascade of commitments.

Focus Intensely on Inclusion, Rigor, and Ownership

  • More inclusive is more effective. The more stakeholders you can involve in the formative stage of a project, the more buy-in they will have for what the project team creates and the more they will contribute. Conversely, if people perceive they have been left out of the process, the likelihood of eliciting a high performance from them is low.
  • People’s commitments matter. At this early stage in a project, it is important to bring the intense focus to commitments and for people to adopt a rigorous relationship to their word so that commitments are clear and can be managed effectively. This offers a vital focal point for the early days of the work – when there may be no immediate visible results – and is essential to high performance.
  • Owning just your part is not good enough. The most impressive capital project successes my colleagues and I have seen consistently demonstrated a sense of collective accountability for the results. There has been a real sense of “us” – something to which everyone is contributing. As capital projects become more and more complex, it is critical for all groups to take ownership of the whole venture.

Again, this is about a real experience versus a check-the-box exercise. It has been our extensive, repeated experience that the quality of the alignment and momentum that comes out of a candid, thoughtful partnering session are orders of magnitude more powerful than when people are simply going through the motions.

My colleagues and I were recently brought in to conduct a partnering session for a North American infrastructure project. In the midst of implementing the steps I have described here, there was a moment when the people in the room were clearly struck by the nature of the conversation. They said that while the agenda was similar to those of countless partnering sessions they had had before, it was a distinctly original experience for them.

Why? They said: “Because we’re having a real conversation, The kind of conversation we never have. We are not saying what we think the other group wants to hear. We are saying what we think.” These are seasoned, well-credentialed professionals, but it was clear that they were not accustomed to having the perceptions and interpretations in the background being brought into the foreground – in a safe way where they could deal with them constructively. These project veterans were shocked because they had never had such an experience.

Was that the moment that made the difference? It was when we asked them to consider the radical idea of telling the truth rather than posturing to protect or defend their position.

If you have ever been involved in a powerful launch effort that initiates high performance, you do not soon forget it. It should not be so rare, and it does not have to be. We have seen it happen, and how it results in far less time, energy, and money spent on repairing and retooling down the road. It starts with leadership willing to put themselves on the line from the start, and stand for a project that deserves the best launch – and performance – possible.

3 Steps to Skyrocket Your Communication

Unlike Santa Clause, the Tooth Fairy and Unicorns, effective communication is not a myth. In fact, perfect communication is easily achieved with the right skills and software.

Don’t believe me yet? Let me show you!

Communication is important for project and risk management. Crucial, even. But it is not about following THE golden rules or going through pre-defined steps you found in some book that urged you to buy it because the title literally said: “BUY ME.” It’s actually simpler than that. The way to do it effectively is by understanding why it is important. Know how it works and what resources are out there to help you get a clear overview of your progress.

“The art of communication is the language of leadership.”
– James C. Humes

Be it an individual or an organization; everyone can benefit from improved communication, especially project managers. Working on a project with a tight deadline, solving customer problems, or dealing with risks are part of your everyday. Your interactions and ability to get results daily depend on the art of communicating clearly with others.

Effective communication relies mainly on psychology, the environment, and resources:

1. Psychology

“Ultimately, leadership is not about glorious crowning acts. It’s about keeping your team focused on a goal and motivated to do their best to achieve it, especially when the stakes are high, and the consequences really matter.”
– Chris Hadfield

Project management depends on psychology in the sense of how well do you know the people you’re working with? What are their personality traits? What do they respond to and what do they not? How well they work under pressure? What kind of results do they give back in response to incentives?

  • As the project manager, it’s beneficial to know who can do what
  • Better allocate tasks thus optimizing risk management
  • Know what to do to whom in order to get better results
  • Make sure that everyone is relatively at ease and are not overly stressing about a task they could not handle properly

2. Environment

As a PM, it is very important to make sure that the environment your team is in suits the importance of the task at hand. Meaning that, are they under constant pressure or are they working at ease? Is the aura of the workplace charged with tension or is it rather light? Is the team motivated enough? Do they feel overworked compared to what they are getting in return?

All of these questions decide what kind of atmosphere is surrounding your team. The environment greatly affects the quality of the end result, risk management, and how the work is submitted. This brings me to my final point which is, by the way, the easiest one of them all yet is still so crucial: the resources.

3. Resources

“The two words ‘information’ and ‘communication’ are often used interchangeably, but they signify quite different things. Information is giving out; communication is getting through.”
– Sydney J. Harris

There are ample project management resources out there. PMs get overwhelmed and underestimate the importance of using the right tools to keep track of the tasks at hand while managing risks. It is true that being a project manager is not the easiest job in the world! But it could be easier if you know what kind of resources to use in order to do the most of the job with the least amount effort.

Keeping track of all the apps, emails, feedback, and everything in between can be so overwhelming at times, no matter how small the project is! But let me make your day -more than I already have – and tell you that there are solutions out there!
Communication is the root cause for a lot of delays happening today to software development. Communication is a large frustration between technical (IT) and non-technical (Business) people. It takes much more than a project management tool to optimize communication and present it communications at different levels of complexity. We need to focus on ensuring the tech talk is translated into the non-tech talk, hence giving the right information to the business people they need to make faster decisions and remove blockers from any software projects.

Editors Note: It’s a good practice for Project Managers to put together a communication plan that clearly defines the audiences that you will need to communicate to during your project. These audiences have communication preferences around the level of technical language in the communication. Each audience also has communication preferences such as email, meetings, or presentations. To effectively ensure you are communicating well for your project, create a communication plan that includes communication preferences, the frequency of communication, communication method and level of technical expertise for all your audience types (executive or C-level, development leadership, IT leadership, non-technical business teams, and others).

7 Key Things for Large Project Success

We all know that large IT projects are often bound to fail or end up consuming enormous resources.

Furthermore, the more ambitious the project, the higher risks. So, what can we do to avoid costly mistakes?

First, we must realize that this is a global challenge. Statistics published by the Standish Group in their annual report reveal the scale of the problem (see references below). Less than one-third of IT projects are successful. The definition of successful is that the project fully met deadlines, budget, and functional requirements.

Nearly a half of all projects (48%) are completed, but don’t meet the above requirements and end up being too expensive, drawn-out, or offer less functionality than originally planned. Moreover, a frightening 23% of projects are abandoned during their execution. These figures should be enough of a motivator for anyone to start looking for ways to mitigate risks and increase the chances for success.

A big project is very much like a long and often exhausting journey. Remember the race to the South Pole? Amundsen won because he planned carefully, brought the right team and equipment and was an outstanding leader himself. He had no time to wait for help, so he made the best use of his existing resources. Planning is a treasured skill to learn in business, too.

Here are seven key Points for Project Planning based on my practical project management experience:

1. Place Greater Focus on Clear Business Requirements

High-quality Business Analysis lies at the core of project success. Poorly defined requirements lead to overlooked customer needs and missed deadlines, according to the Business Analysis Benchmark Report.

Experts advise treating business requirements as a process rather than filling out a template or creating a document. Ask for customer feedback constantly to check on the requirements to make sure they align with the business goals by performing requirements traceability. Trace requirements to scope, design, and testing to ensure requirements are not dropped or missed.

2. Set Realistic Deadlines

The ability to set realistic deadlines largely depends on the previous point of ensuring requirements are understood and traceable. Only when you have clearly defined requirements and scope of work, will your expectations of the business solution be realistic. Clear expectations and common understanding of the business solution ensure that resources can estimate the effort to build the business solution more accurately. What’s important is not to overpromise. Performing analysis on records of similar projects and employee timesheet data assist in creating realistic estimates and deadlines.

You may need to amend or revise the business solution design as the project moves forward. Additionally, the resources necessary to build and deploy the updated business solution may change. Estimate to complete tasks will drive new deadlines. Managing change on a project is critical to keeping the project moving forward quickly. Changes that are not addressed and managed could send the project out of control.

3. Build a Solid Team

People are everything. If you are heading out to the South Pole, you will need the best-experienced people next to you. The same applies to a large project. Pick competent staff and get them all involved in planning and executing. Keeping your team motivated is essential.

Don’t count too much on the individual skill as teamwork and collaboration are also important. Whatever it takes, you need to have experienced leaders to bring your team together.

4. Communicate Wisely

Efficient communication is critical on every level. First, make sure that your product owners and business analysts have good contact with the customer, understand the customer’s needs thoroughly and actively manage the customer’s expectations on the business solution.

Second, establish efficient communication inside your project team. Frequent status meetings are a must. Their goal is not only to learn about the project progress but also identify problems, deal with conflicts and coach your team. These practices will contribute to better collaboration.

Make sure you know where to stop so that meetings do not turn into an all day event. Status meetings that as a half an hour to one hour is typically sufficient with a well thought out agenda.

5. Executive and Sponsor Support

It all starts with the executives and sponsors. If the executives and sponsors are not engaged in a project and show no interest in it, it can be reasonably anticipated that your project will have difficulties. If it becomes increasingly clear that the plan lacks support, employee motivation drops dramatically as a result.

With strong executive and sponsor support to assist in identifying and mitigating risks, allocate or acquire resources and skill sets as required, and consistent oversight at every stage of the project will result in a greater success rate for large projects.

6. The Agile Methodology

Experience shows that smaller projects have better chances for success than large ones. Breaking down a large project into smaller manageable parts does the trick. Try aiming for smaller milestones and shorter development sprints. Potentially achieve both with an Agile methodology.

According to the statistics gathered by the Standish Group, Agile projects succeed three times more often than projects with a traditional methodology like Waterfall although these results are disputed due to the definition of project success used in the study it is widely defined. Agile can help manage customer expectations by continuously delivery of working product and validating the business solution with your customers.

7. Keep Your Finger on The Pulse

On every stage of the project, it is essential to track your progress and know how you are performing. You can choose out of plenty of tools that allow you to view spent and remaining resources, and report on them.

There’s no need to use broad and complex systems such as Microsoft Project that require much effort and time to configure. Opt for a simple but functional timesheet software, such as actiTIME. It can be a good choice to set up budgets, manage user rates, and track spent hours. This way you will always be alert and able to plan.

Summary

The success of a large-scale project is defined by multiple factors. To ensure that your project is delivered on time and budget, you would have to build the process carefully, starting from high-quality business analysis and accurate estimates.
Prepare well for your journey by picking a strong team and encourage them to communicate. Try to win the management’s support and follow the agile principles. Track your progress regarding work done and time spent with the help of a handy tool.

References 
Mountain Group – Agile Succeeds Three Times More Often Than Waterfall – http://www.mountaingoatsoftware.com/blog/agile-succeeds-three-times-more-often-than-waterfall
IT Success and Failure — http://www.cafe-encounter.net/p1183/it-success-and-failure-the-chaos-report-factors
The Standish Group CHAOS Report Success Factors – Standish Group Chaos Reports Revisited – https://theagileexecutive.com/tag/the-standish-group/
Success to Standish is Failure in Agile – https://tobeagile.com/2017/02/15/success-to-standish-is-failure-in-agile/

The Project Mindset – Fact or Fiction?

I have been thinking about this project management topic for many years. Is the Project Mindset real?

Is there a culture or a set of habits or behaviors that can define the Project Mindset? Do Project Managers have a Project Mindset?

What makes some people more suited to projects than others?

What are the traits to look for when selecting a team for a project that may not necessarily have direct project experience?

What can essential knowledge sharing do so that the team members are clear on the project culture?

This scenario is becoming more relevant as operational staff in many organizations are increasingly expected to work on projects as they have intimate knowledge of the business processes impacted. Although operational targets are similar – they tend to be repeated, so the team knows how to achieve and repeat them.

The Project

When we look at a project in general and key elements of a project, here are some of the ways in which a Project can differ from an operational environment.

  • A Project Has a Beginning. It is not a pre-existing entity.
  • A Project Has an End. Once the scope is delivered, the project will finish.
  • A Project is a Temporary State – it will not continue forever. Project teams, Rooms and Ways of Working are temporary.
  • A Project is Unique. Even if the delivery of a project is part of a wider program, the project is unique to its team, site, and installation. A project is not repeated.
  • A Project is Not Part of Business as Usual. Projects are not defined operational processes and tasks which are easily repeatable.

Project Resources

Looking at the above features. The First two items, i.e. the Project has a beginning, and the Project has an end is obvious to most people and needs no explanation or introduction.

The other three elements Temporary State, Unique and Not Part of Business as Usual create some of the biggest challenges for Operations or Support teams that are suddenly thrust into projects or find themselves on a project team.

Operations and Support teams are used to a routine. Each week looks and feels that same, standard work practices, standard tasks and a fixed meeting schedule for each week.

A Project pace of activity will vary as it moves from Kick off to Specification, Design to Build, Build to Test, Test to Qualification, Qualification to Implementation and Implementation to project close.

With each of these project phases comes a different challenge, a different pace and the ability of the project resources to adjust. The pace and change to the level and type of activity are critical to the success of the project. This change of routine, pace and activity are what most operations based people can tend to struggle with for the first time they are working on a project.

Project Culture

A Project Manager or Engineer with years of experience will instinctively know when to adopt a different pace within a project whereas the operations resources will just become comfortable with varying levels of pace and change.

When the pace changes some of the resources will adapt and deliver even if they are moving out of their comfort zone. Personally, I have always encouraged people to keep learning and to move out of their comfort zone from time to time as this experience will promote the individual growth.

As Project Managers and Project Leaders should we avoid or to address the aforementioned comfort zone? Is prevention better than cure? If a resource has no project experience, should we consider them for business-critical projects?

Alternatively, should we offer them advice, coaching, and support to facilitate the transition from a non-project to a project way of working? Are people capable of adopting the “Project Mindset?” This is an opportunity for you to develop as a leader by coaching someone into a position of confidence in their new role.

Team Selection

When selecting Operations based resources for projects consider the factors above. Is the person suited to a change of pace, change of activity, or change of routine? Directly asking the person may not yield the correct answer. You need to do a little research on the individuals as you would when recruiting for any role.

Find out if they have a track record of adopting change into their daily work. What has their past response to new company policies, procedures, processes, and systems? How have they responded to pressure situations in the past or to last-minute changes of direction?

You need to do your research when hiring project resources for several reasons, but above everything else the biggest constraint is time. As projects have a fixed planned duration, you may not have the time to take a risk on a resource.

In Summary

Moving from operations to project based work should be seen as an opportunity to grow as an individual and expand the capability of the person and the organization.

There no hard and fast rules to selecting project resources but I look for the “Project Mindset.” I define this as a set of characteristics that will provide an indication of how a person will respond to a project.

How I summarize this is:

  1. The ability to cope positively with change
  2. A willingness to dig deep to complete a milestone
  3. Does not tend to knee-jerk react to surprises encountered on a project
  4. The Capability to move roles and work multiple roles to get the job done
  5. The ability to switch off and chill after a period of high-intensity working
  6. Must not take any work-related discussions personally
  7. Can keep focused on the end goal
  8. Believe the end goal is possible
  9. Can support the team to deliver the scope at all costs

Sounds easy, yes? I would love to know your thoughts on this topic.