
In project management, the SWAG estimate is a rough estimate of the work required to complete a project. This estimate is typically made during the early stages of a project when there is still a lot of uncertainty about the scope and requirements. Because it is based on the estimator’s experience and judgment rather than detailed data, it is best expressed as a range rather than a single number.
A SWAG is a range, not a number. At the idea stage, estimates can miss by a factor of 4 in either direction, so give stakeholders a low and a high figure.
Break the work into chunks first. Guess low, best and high for each chunk, then add them up. The widest chunk is the unknown to investigate first.
Write down your assumptions. Scope, team and exclusions turn a guess into an estimate people can challenge, and the gap to your 80% number is your contingency.
Swap SWAG for PERT as you learn. Once tasks are known, use E = (O + 4M + P) / 6. Only 8.5% of 16,000 large projects hit both budget and schedule.
SWAG is a simple yet effective technique used in project management as a tool that helps to roughly estimate the cost, time, and resources required for a project. SWAG stands for Scientific Wild Ass Guess. The SWAG technique can be used for various projects, from small tasks to large-scale initiatives. If you are planning a project, this tool can help you estimate the resources you will need and the time it will take to complete the project.
Estimating techniques like SWAG are covered in depth in a 4-day project management PMP certification training carried out by PMI’s authorized training partners, like Vinsys.
Benefits of Using SWAG Estimate

In project management, time can be money, and accurately estimating the time required to complete a project is essential to avoid unforeseen delays or cost overruns. Using this tool can be beneficial for your organization, especially during early planning stages when leaders may also be trying to evaluate offshore SDR candidates with limited performance data.
- It is swift and easy to do, just like a ballpark estimation
- It can be used when there is very little information available about a project
- It can be accurate enough for early go or no-go decisions
- SWAG can be done without formal training, although it relies on relevant experience
- It can be used for a variety of different projects
Overall, the estimating technique is a valuable tool that can help save time and money on projects.
Real-life example
A 12-month gut estimate can really mean 3 to 48 months
Barry Boehm first drew the “cone of uncertainty” in 1981, and Steve McConnell later popularized it for software project managers. At the initial concept stage, a quick estimate can be off by 4x on the high side or 4x on the low side, a 16x spread. That is why a SWAG is valuable for fast go or no-go decisions, but only when it is stated as a range.
Source: Construx, Software Development’s Cone of Uncertainty
Expert view
“Software organizations inadvertently sabotage their own projects by making commitments too early”
Steve McConnell, author of Software Estimation: Demystifying the Black Art (source)
By the numbers
- 16x
spread between the high and low estimate at the initial concept stage
- -50% / +100%
widest expected accuracy of an AACE Class 5 (concept screening) estimate
- 0% to 2%
project definition behind a Class 5 estimate, the stage where most SWAGs are made
How is the SWAG Estimate Determined?

This estimate is based on scope, time, and resources. It is crucial when determining the project’s budget and organizing its timeline. In agency project management, rough estimates can be especially useful early on when teams need to assess client work before the full scope and requirements are finalized. SWAG estimates can be determined using a scoring system that considers the project’s complexity, the team’s experience level, and customer expectations.
This system is designed to provide a more consistent estimate of the effort the software development team will need to deliver the work. In projects that involve complex datasets or reporting requirements, working with specialists in data visualization consulting can also help teams present project metrics more clearly and support better planning decisions.
SWAG Estimate in Agile

Now that we clearly understand SWAG, we can look at how it is used in project management with an Agile project. Many Agile teams discuss SWAG estimation. Estimating the story points for backlog items is a common practice in Agile. In Agile software development, estimating the time to complete a task or project is often needed.
When estimating, you can use a scoring system that takes into account the following points:
- The complexity of the project
- The team’s experience level
- The customer’s expectations
A SWAG estimate represents the effort the software development team will need to deliver value to the customer. This estimate will be based on several factors, such as:
- The complexity of the task
- The size of the team
- The experience of the team members
Time estimation is difficult because each team has its own definition of a point. However, you can determine a rough estimate for your team using techniques like T-shirt sizes, while some other teams use the Fibonacci sequence to size work relative to other work before turning it into a timeline.
Components of a SWAG Estimate Project Management

When estimating the cost of a software project, a few key components must be considered to get an accurate project estimate. These components include:
SWAG Cost Components
Add the three components together to get the cost side of your SWAG estimate.
| Component | What It Includes | How to SWAG It |
|---|---|---|
| Cost of Materials | The cost of materials includes software licenses, hardware, cloud services, equipment, and any supplies the project needs. | List the big items and use current prices or the last similar project. |
| Cost of Labor | The cost of labor includes the hours each person or role will spend on the project, multiplied by their rates. | Guess low, best and high hours per role, then multiply by each rate. |
| Cost of Overhead | The cost of overhead includes the cost of office space, internet access, and any other indirect costs that may be associated with the project. | Apply your organization’s usual overhead rate to the labor cost. |
Taking all of these factors into account can give a more accurate estimate of the actual cost of a software project.
Creating a SWAG Estimation and Making it Accurate

A work breakdown process can turn the project scope into high-level components and present them in a structured format using a flipbook maker, while estimating each part using a standard or knowledgeable approach. You should focus on achieving tangible and measurable objectives and goals, so focus on the most essential things and deliver results.
For example, imagine you’re a construction loan expert in Texas working on a VA construction loan project. Without a detailed blueprint or team in place, you might quickly estimate costs by breaking the project into broad categories, such as land preparation, construction materials, and labor, and then use industry averages or past experiences as a basis for your SWAG estimation. You can also leverage construction accounting software to track these estimates and refine them over time. This approach allows you to provide a rough estimate that helps the client understand potential costs while you gather more detailed information later.
What if you don’t have a team and need to estimate your project quickly? A SWAG estimation can be your go-to method for an initial assessment while ensuring transparency with stakeholders about its high-level nature.
SWAG Range Estimator: Build Your Estimate
Use this free estimator to turn your guesses into a range you can share. Break the project into chunks, enter a low, best and high guess for each one, and the tool adds them up, shows a PERT figure and the number to plan to, and writes a summary with your assumptions. It opens with the e-commerce example below already loaded.
Ranges from AACE estimate classes 5, 4 and 3.
Enter your best guess for each chunk. Add a low and high guess, or click “Fill low and high” to apply the range above.
| Work chunk | Low | Best guess | High | PERT |
|---|
- Low0everything goes well
- Best guess total0sum of best guesses
- Plan to0about 80% confidence
- High0most things go wrong
The PERT column uses (Low + 4 x Best guess + High) / 6. “Plan to” adds about 0.84 standard deviations to the PERT total. Everything runs in your browser; nothing is sent or saved.
Agile SWAG Estimate Example
Imagine you’re the project manager for XYZ Corporation and have just been assigned to develop an e-commerce store for an X client. The question is: How much will this project cost? Based on your expertise and knowledge, you can quickly sum up all the components and estimate the time depending on your team size and their skills.
For example, you GUESS it takes 6 months to develop this software, which may cost $200,000 to complete. The sum of your estimates for all the components is your SWAG number. Once you have an overall estimate, you will have a rough number to give you a general idea of the project. But it will be defined by GUESSES. SWAG estimates work best when you treat them like a range with assumptions (scope, team velocity, unknowns), not a single “final” number, because the fastest way to blow a budget is to make an early guess sound like a commitment, suggests market commentary from SmartInvestorsDaily.
However, this number sometimes leads to errors with resources and time. This is why this estimation should always be followed up with more detailed and accurate techniques like the PERT formula.
Research example
Students guessed 33.9 days for their thesis and needed 55.5
In a 1994 study by Roger Buehler, Dale Griffin and Michael Ross, 37 psychology students estimated how long their honors thesis would take. Even their worst-case guesses, averaging 48.6 days, came in short. The same optimism shows up when a project manager guesses a single number for a whole project, which is why a SWAG should list its assumptions and a high figure.
Source: Planning fallacy, summary of Buehler, Griffin and Ross (1994)
Famous adage
“It always takes longer than you expect”
Douglas Hofstadter, Hofstadter’s Law, Gödel, Escher, Bach (1979) (source)
By the numbers
- 33.9 days
average best estimate the students gave
- 55.5 days
average time they actually needed
- About 30%
of students finished within the time they predicted
PERT vs. SWAG Estimate

Although the PERT formula is more accurate than SWAG estimation, it can be more time-consuming and detailed. PERT (Program Evaluation and Review Technique) is a more reliable way to estimate the time necessary to complete a project because it estimates:
- The individual task duration
- The uncertainty of the tasks
- How much buffer to plan for if tasks take longer than expected
The PERT formula takes into account the three main variables that can impact the timelines of a project:
- The Optimistic Estimate (O): What is the shortest amount of time the project could take?
- The Most Likely Estimate (M): What is the most likely amount of time the project will take?
- The Pessimistic Estimate (P): What is the longest amount of time the project could take?
To calculate the PERT estimate, you multiply the most likely estimate (M) by four, add the optimistic (O) and pessimistic (P) estimates, and divide the total by six. This weighted average gives the most likely estimate the most weight, and for teams running this calculation across dozens of tasks, some project managers turn to Power Automate consulting services to automate the repetitive math rather than recalculating it manually each time.
This is the formula:
E = (O + 4M + P) / 6
Although the PERT formula is more time-consuming than the SWAG estimate, it is considered much more reliable.
Industry research
Large IT projects run 45% over budget on average
McKinsey and the University of Oxford compared the budgets, schedules and promised benefits of more than 5,400 IT projects with their actual results. Early numbers that were treated as commitments, rather than ranges to refine, are a big part of the gap. Moving from a SWAG to a task-level PERT estimate before the budget is approved helps project managers avoid becoming part of this statistic.
Source: McKinsey, Delivering large-scale IT projects on time, on budget, and on value
By the numbers
- 45%
average budget overrun on large IT projects
- 56%
less value delivered than predicted
- +15%
extra cost overrun for every additional year a project is scheduled to last
Pitfalls When Doing an Agile SWAG Estimate in Software Development
Software development is a complex process, and estimation is one of its most challenging aspects. Estimating the time and resources required for a project is essential for its success, but it is also notoriously tricky to get it right. The video below walks through seven Agile estimation techniques Scrum teams use to size work more reliably.
Video: 7 Agile Estimation Techniques Every Scrum Team Should Know. Watch it on YouTube.
Cons Of SWAG Estimate

- Not recommended for extremely unusual projects
- It is not very accurate and can lead to unrealistic expectations, giving stakeholders a false sense of confidence in the estimate’s accuracy.
- It is essential to remember that SWAG estimation is only an approximation and should not be used as the sole source of information for planning and decision-making.
- It’s not a guarantee, and it’s essential to have a contingency plan in place in case the amount of work required exceeds the estimated amount.
Real-life example
The Sydney Opera House was estimated at A$7 million and cost A$102 million
The 1957 estimate projected a cost of A$7 million and completion in January 1963. Construction started before the design was finished, and the building opened in 1973, ten years late and more than 14 times over budget. A single early number, taken as a promise, is exactly the risk this section describes.
Expert advice
“Think slow, act fast”
Bent Flyvbjerg, co-author of How Big Things Get Done (2023) (source)
By the numbers
- 8.5%
of about 16,000 large projects were delivered on time and on budget
- 0.5%
were on time, on budget and delivered the expected benefits
- 10 years
late for the Sydney Opera House, which opened in 1973
SWAG Estimate Facts Worth Checking
Early estimates attract a lot of myths. Here is what standards bodies, researchers and primary sources actually say.
Ten common claims about SWAG and early estimates, checked against standards, studies and primary sources.
| # | You may hear | What the data says | Source |
|---|---|---|---|
| 1 | SWAG is an official PMI estimating method. | PMI’s standards describe techniques such as analogous, parametric, three-point and bottom-up estimating, plus expert judgment. SWAG is informal shorthand for a judgment-based rough estimate. | PMI, PMBOK Guide |
| 2 | A rough order of magnitude estimate is within 10%. | The PMBOK Guide, Sixth Edition gives a rough order of magnitude range of -25% to +75% early in a project. | PMI, PMBOK Guide |
| 3 | An experienced guess is usually close to the final result. | At the initial concept stage, estimates can be 0.25x to 4x the actual outcome, a 16x spread. | Construx white paper |
| 4 | Early cost estimates are accurate to plus or minus 10%. | AACE classifies a concept screening (Class 5) estimate at -20% to -50% on the low side and +30% to +100% on the high side. | AACE 18R-97 matrix |
| 5 | PERT averages the optimistic and pessimistic times, then adds the most likely. | The PERT formula is E = (O + 4M + P) / 6, so the most likely time carries four times the weight of the other two. | PERT formula and calculator |
| 6 | Story points are just hours under another name. | The Scrum Guide does not define story points at all. Points are relative sizes, and each team calibrates its own. | The Scrum Guide 2020 |
| 7 | Most large projects finish on time and on budget. | Only 8.5% of about 16,000 large projects hit both time and budget, and 0.5% also delivered the expected benefits. | Flyvbjerg and Gardner, HBR 2023 |
| 8 | Large IT projects usually land close to their budget. | Across 5,400+ IT projects, large ones ran 45% over budget and 7% over time, while delivering 56% less value than predicted. | McKinsey and Oxford |
| 9 | Knowing that past tasks ran late fixes optimistic estimates. | Students predicted 33.9 days for their thesis, needed 55.5, and only about 30% finished on time, even though they knew their own track record. | Buehler, Griffin and Ross, 1994 |
| 10 | Famous projects prove early estimates can be trusted. | The Sydney Opera House was estimated at A$7 million in 1957 and cost A$102 million, finishing ten years late. | Google Arts & Culture |
Sources checked November 4, 2026.
Conclusion
SWAG estimates provide project managers with a quick, flexible way to gauge project scope, cost, and timelines when detailed data is unavailable. While not highly precise, they serve as a valuable starting point for planning and discussion. Combining SWAG with more structured methods like PERT ensures better accuracy and informed decision-making throughout the project lifecycle.
SWAG Estimate FAQ
SWAG Estimate FAQ
What Is the SWAG Estimate in a Nutshell?
SWAG (Scientific Wild Ass Guess) estimation is a quick, informal tool used in project management to determine the approximate time, cost, and resources needed to complete a project. It is especially useful in the early stages when detailed information is still unavailable.
How Accurate Is the SWAG Estimate?
SWAG is an informed approximation based on experience and intuition, not precise data. It is not considered the most accurate assessment and does not guarantee actual cost, time, or effort. It should always be followed up with more detailed estimation methods for better reliability.
What Are the Key Components Needed for a SWAG Estimation?
A SWAG estimation considers three key components: the cost of materials needed for the project, the labor costs based on the number of people involved, and overhead expenses such as office space and internet access that indirectly affect the overall project budget.
What Are the Skills Required to Create a SWAG Estimate?
Creating a SWAG estimate requires no specialized training. However, relevant industry experience, familiarity with similar past projects, and strong intuitive judgment are essential. A skilled specialist can quickly provide a reasonable, rough estimate based on their expertise and prior knowledge of comparable project scopes.
Suggested articles:
- Risk Control In Project Management
- Project Schedule Compression Techniques for PMs
- Understanding Project Testing and Its Phases
Shane Drumm, holding certifications in PMP®, PMI-ACP®, CSM, and LPM, is the author behind numerous articles featured here. Hailing from County Cork, Ireland, his expertise lies in implementing Agile methodologies with geographically dispersed teams for software development projects. In his leisure, he dedicates time to web development and Ironman triathlon training. Find out more about Shane on shanedrumm.com and please reach out and connect with Shane on LinkedIn.