Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Project Management for Small Business

Project Management for Small Business

A Streamlined Approach from Planning to Completion
Run client projects without letting missed details, scope changes, or late payment erase the margin.
by Joseph Phillips 2011 304 pages
3.85
26 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Run each project as a small, temporary business with a profit test

Projects are temporary promises. A project turns a customer need into a defined result, then ends. Its success depends on four interdependent roles: the customer funds and accepts the result, the team creates it, the project manager coordinates the work, and the owner carries the business risk. Treating these roles as opponents undermines the shared outcome: reliable delivery and a sustainable profit.

Keep the method lean. The triple constraints are scope, time, and cost: changing one usually affects the others. A small firm need not apply every formal process to every job. Use enough structure to make commitments clear, coordinate work, and protect margin. Planning is not paperwork for its own sake; it is a way to reduce expensive surprises.

Analysis

The project-as-business framing usefully puts operational discipline beside customer value. It also exposes a classic principal-agent problem: owners, managers, workers, and customers hold different information and incentives, so shared expectations matter as much as authority. A lightweight process can reduce that friction without importing the bureaucracy of a large enterprise. Profit, however, is not a complete definition of success. A project can meet its margin target while damaging safety, trust, or long-term capacity. The strongest version of the approach treats profit as a viability test, alongside the promised result and the quality of the working relationships.

Price only work whose scope, cash flow, and contract risk make sense

Choose before committing. A promising contract can still be a poor project if its costs, duration, constraints, payment timing, or stakeholder demands overwhelm its benefits. Compare the expected profit with the people, capital, and attention the work will consume. The book's example of a $25,000 sale with $18,500 in costs leaves $6,500, a 35 percent markup on cost. That figure matters only if the estimate includes the real work and overhead.

Know who carries risk. Under a fixed-price contract, the seller generally absorbs overruns. Time-and-materials contracts charge for labor and materials as used, and should set a not-to-exceed cap. Agree in writing on deliverables, acceptance, payment dates, and how proposed changes are handled. Attractive revenue is not the same as healthy cash flow, especially when expenses arrive before customer payments.

Analysis

This is a practical application of opportunity-cost thinking: capacity assigned to one contract cannot be used elsewhere. The useful question is not simply whether a project earns money, but whether its return justifies tying up labor and cash for its duration. Contract form allocates uncertainty, so price and governance cannot be separated. A fixed price rewards accurate scoping but can punish a seller for ambiguity; a capped time-and-materials arrangement shares some uncertainty while limiting exposure. The book's simple markup calculation is a starting point, not a full profitability model, particularly where overhead allocation and delayed payment are significant.

Find the customer's real problem before building the requested solution

Listen for the cause. Requirements are the specific outcomes and conditions a customer expects. The book describes a shop owner who wanted to replace a costly machine because it produced faulty goods. Investigation found that the equipment had not been balanced, operators lacked training, and its software was installed incorrectly. Replacing the machine would have treated the visible symptom, not the underlying causes.

Make expectations testable. Gather requirements through focused interviews or workshops, then record and confirm them. Brainstorming can generate possibilities; prioritization helps stakeholders choose what matters most. A prototype makes an intended result visible before full production. Where work processes are involved, observe current conditions and record a baseline, meaning a measure of performance before the project. Define exclusions and measurable acceptance conditions so words like “better” do not become competing interpretations.

Analysis

The machine example captures a core diagnostic discipline: separate a customer's proposed intervention from the problem the intervention is meant to solve. This resembles clinical reasoning, where a symptom is evidence, not yet a diagnosis. Observation and prototypes also reduce the gap between verbal descriptions and actual use. That said, discovery should not become an excuse to override the customer. The provider's expertise is most valuable when it makes alternatives and trade-offs legible, then secures explicit agreement on the chosen outcome. A baseline is especially useful because it makes claims of improvement answerable to evidence rather than confidence.

Break every promise into deliverables before turning it into tasks

Map what completion means. A work breakdown structure, or WBS, decomposes the approved project scope into smaller deliverables called work packages. It describes what the project must create, not the sequence of tasks used to create it. A home-building project might divide a kitchen into cabinets, flooring, plumbing, and appliances. Each element can then be estimated, assigned, checked, and matched to the customer's requirements.

Build the task list second. Once the deliverables are visible, identify the activities needed to produce them. The book offers an 8/80 guideline: work packages often work best when they take between 8 and 80 labor hours, though this is not a rigid rule. The WBS also helps reveal missing requirements, costs, resources, quality checks, and risks. Templates can speed repeated work, but each project still needs review for its distinct conditions.

Analysis

The WBS is powerful because it creates a shared model of the work before people argue about dates or ownership. In systems engineering, this resembles decomposing a system into components whose interfaces and acceptance conditions can be checked. The distinction between deliverables and activities also prevents a common planning error: confusing being busy with producing the promised result. The 8/80 guideline is useful as a prompt to inspect work-package size, not as a universal standard. Too much decomposition creates administrative drag; too little hides uncertainty. The right level is the one that supports accountable estimates and meaningful inspection.

Replace guesswork with calibrated estimates and records of actual work

Match precision to evidence. A rough order of magnitude estimate is an early ballpark, illustrated in the book with a possible range of plus or minus 50 percent. A budget estimate uses clearer requirements and may be expressed within plus or minus 25 percent. A definitive estimate, built from detailed scope and the WBS, may narrow to plus or minus 5 percent. These are illustrative confidence ranges, not guarantees. More detail and trustworthy historical records generally improve estimates.

Plan in waves. Rolling-wave planning means outlining the whole project broadly while detailing the next phase closely, then revising the plan as new information arrives. Record actual labor, material costs, and activity durations, then compare them with estimates. Repeated projects can use past results as a starting point, but similar jobs are not identical. Software can organize and update the evidence; it cannot replace sound assumptions or team knowledge.

Analysis

Estimation is a form of calibrated judgment, not prophecy. Stating an uncertainty range helps prevent an early guess from being mistaken for a firm commitment, a cognitive anchoring effect that can distort later negotiations. Recording actual results turns each completed job into organizational memory, provided the records distinguish unusual events from repeatable patterns. Rolling-wave planning is a sensible response to uncertainty: it delays detailed commitments until they are useful without abandoning the larger direction. Its limitation is that late decisions can create procurement or scheduling bottlenecks, so near-term detail must coexist with a sufficiently clear long-range view.

Schedule dependencies and scarce people, not just dates on a calendar

Model the order of work. A project schedule depends on activity duration, prerequisites, and available resources. The critical path is the longest chain of dependent activities; delay on that chain delays the whole project. Other activities may have float, meaning some delay is possible without moving the completion date. In the book's sample network, the critical path takes 16 days, while alternate paths take 15 and 14 days.

Compress with care. Adding people to effort-driven work is called crashing, and it can shorten duration while raising labor costs. Fast-tracking overlaps activities that would normally happen in sequence, saving time but increasing the chance of rework. Neither approach makes fixed-duration work, such as drying, finish faster. Padding every task can also encourage work to consume all the time allotted, so use historical durations, explicit reserves, and regular progress checks instead.

Analysis

A network schedule is more than a calendar because it represents causal structure: which tasks unlock others, and where delay propagates. This is a useful connection to queueing and bottleneck analysis, where a system's throughput is limited by constrained steps rather than by average effort. Float offers flexibility, but it is not free time if the same scarce person is needed elsewhere. Schedule compression is therefore a trade-off, not a trick. A faster plan can reduce delay costs while increasing coordination demands, defects, or safety exposure. The relevant measure is the total system outcome, not the earliest date in isolation.

Make changes visible, priced, and approved before work absorbs them

Protect the agreed scope. Scope creep is the accumulation of small, undocumented additions that consume time and money without formal approval. A change control system records a request, assesses its effects, and documents whether it is accepted or declined. Review more than the requested feature: changes can affect schedule, costs, quality, staffing, risks, communications, procurement, and the contract. Approved changes should update the relevant plans and deliverables; verbal requests should not quietly become obligations.

Inspect quality before handoff. Quality means meeting the agreed requirements, not adding unrequested extras. Quality assurance is the preventive approach that sets standards and prepares people to do work correctly. Quality control inspects completed work for defects before the customer receives it. The book stresses that rework makes a business pay twice: once for the faulty work and again for correction. Its Plan-Do-Check-Act cycle turns inspection findings into improvements.

Analysis

Change control functions as governance for a shared commitment, not merely as a barrier to customer requests. It makes hidden costs negotiable and protects the relationship from the resentment that accumulates when informal favors become assumed entitlements. The quality distinction is similarly valuable: conformance is not the same as luxury, and adding features without consent can create more complexity rather than more value. Preventive standards and inspection complement one another, much like process control and feedback in manufacturing. Still, a rigid system can suppress valuable adaptation. The goal is not to eliminate change, but to make its consequences and authorization explicit.

Make risk everyone's job, including the search for upside

Keep uncertainty visible. A risk register is a record of possible events, their likelihood and impact, planned responses, owners, and outcomes. Risks include threats, such as injury or vendor delay, and opportunities, such as a material discount or a faster method. Start by reviewing scope, activities, estimates, assumptions, constraints, and past projects. A quick qualitative ranking can identify risks that deserve closer analysis; numerical analysis is useful when a major decision requires a clearer estimate of probability or cost.

Assign action before trouble. Responses can avoid, transfer, or reduce a threat, or accept it; opportunities can be pursued, strengthened, or shared. Name a risk owner and define a trigger, a signal that action should begin. A contingency plan describes how to recover from a serious failure. Responses themselves can create secondary risks, so monitor results and update the plan rather than treating the register as a one-time form.

Analysis

The inclusion of opportunities prevents risk management from becoming a catalogue of reasons to say no. In decision theory, uncertainty can have asymmetric value: a modest experiment may limit downside while revealing whether a larger gain is attainable. Risk ownership also matters because a hazard without a person responsible for monitoring it is only a note. At the same time, probability scores can create false precision when evidence is thin. Qualitative ranking is often enough for ordinary uncertainties; numerical analysis earns its cost when it changes a consequential decision. The register should support action and learning, not merely reassure managers that risk has been documented.

Map who can block the work, then give each stakeholder the right information

Identify influence early. A stakeholder is anyone affected by the project or able to affect it. A stakeholder register records roles, expectations, contact details, contributions, and communication needs. Analysis distinguishes supporters, opponents, and people who are neutral, then considers their power and influence. The book illustrates the communication burden with 12 stakeholders: the possible links among them number 66. The point is not to calculate every conversation, but to see how quickly coordination grows.

Make communication two-way. Decide who needs what information, when, and in what format. Use status meetings, concise reports, direct conversations, and written records where appropriate. Listen for misunderstanding, not just acknowledgment. Clear assignment of responsibility helps the team coordinate, while genuine recognition can support motivation. Expectations should be realistic: demanding speed and flawless work at once without providing the needed time, training, or authority invites failure.

Analysis

This section treats communication as architecture: the project manager must design channels, responsibilities, and feedback rather than assume that information will travel on its own. That connects to network theory, where each additional participant can create more potential ties and more coordination costs. The practical implication is not to centralize every message, but to establish useful routines and reliable routes for decisions. Stakeholder mapping should also remain revisable. Power and attitudes change as projects unfold, and a person initially viewed as neutral may become central when the work affects their operations. Listening is therefore an ongoing diagnostic practice, not a ceremonial opening step.

Close with customer sign-off, clean accounts, and reusable lessons

Finish the contract, not just the work. Closure means confirming that every promised deliverable is complete, inspecting the final result, resolving claims, closing vendor contracts, and obtaining customer acceptance. A punch list is the final set of corrections or unfinished items identified during inspection. Agree on payment terms at the start, invoice according to the contract, and document the handoff so responsibility is clear. A project may also need an operational transfer plan for training, support, or maintenance.

Make the next project smarter. Archive the plans, actual costs and durations, decisions, and communications. Record what worked and what failed while the experience is fresh. Recognize the team's contribution in a way that is proportionate and genuinely valued. A final report can summarize the result for the customer and preserve useful lessons for the business. Even a canceled project needs orderly closure, including clear agreement about work completed and obligations remaining.

Analysis

Closure is a control point where operational work becomes an accepted asset, a paid invoice, and a record the business can use. That makes it both administrative and epistemic: the team turns experience into information for future decisions. The handoff deserves attention because responsibility can become ambiguous once the project team disperses, particularly when support obligations continue. Recognition also has a practical dimension: it signals which contributions the organization values. Yet a celebration cannot compensate for poor treatment during the work. The book's strongest lesson is that the closeout ritual should confirm a relationship built through consistent delivery, not attempt to repair one at the finish.

Analysis

The book's central argument is that small firms need project discipline without institutional bulk. Its most useful move is to connect familiar project controls to small-business survival: a missed requirement becomes rework, rework erodes margin, and weak closure delays payment and learning. The result is a practical chain of cause and effect, from customer discovery through acceptance, rather than a collection of isolated forms. Its underlying model is feedback-driven. Plans establish expectations, execution produces evidence, inspections reveal variance, and change or corrective action adjusts the work. The WBS makes promises inspectable; historical records improve estimates; risk ownership turns uncertainty into assigned action. These mechanisms create organizational memory, a crucial advantage for small firms that cannot afford to repeat expensive mistakes. Templates and common routines are valuable not because uniformity is inherently good, but because they preserve attention for the differences that matter in each job.

The book also contains a productive tension. It argues that projects should be managed for profit, yet its methods depend on trust, listening, competent work, and a willingness to surface bad news. Those are not soft additions to financial control. They are conditions that make cost and schedule information credible. Still, the book's profit-first language can understate other constraints, especially safety, regulatory duty, worker capacity, and long-term customer value. These cannot always be reduced to margin or negotiated away.

The framework is strongest for small firms delivering defined work for customers, particularly where projects repeat enough to generate useful cost and duration histories. Novel or highly uncertain work needs greater emphasis on experimentation and staged commitment, rather than confidence in a detailed early estimate. The book's enduring contribution is not a fixed sequence of paperwork. It is the habit of making promises explicit, tracing them into work, checking reality, and learning before the next contract begins.

Summary in 30 Seconds
Choose contracts by weighing expected profit against costs, cash timing, and who carries the risk. Confirm customer needs and acceptance conditions, then break promised results into estimable deliverables. Use past work to improve estimates, and schedule around task dependencies and limited staff. Assess and approve changes before they alter commitments. Assign owners to threats and opportunities. Close with customer acceptance, final accounts, and recorded lessons for future projects.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.85 out of 5
Average of 26 ratings from Goodreads and Amazon.

Project Management for Small Business receives mixed reviews on Goodreads, with an overall rating of 3.85 out of 5 based on 26 reviews. Some readers found it useful for upcoming projects, while others described it as boring. One reviewer gave it 3 out of 5 stars, while another rated it 2 out of 5. The book is available at the NLB library under the call number 658.404. Despite the varied opinions, it appears to be a resource for those interested in project management for small businesses.

Your rating:
4.4
81 ratings
Want to read the full book?

Glossary

Triple constraints of project management

Scope, time, and cost

The three linked limits that shape a project's commitments: what it must deliver, how long it may take, and how much it may cost. A change in one often affects the others. The framework helps a manager explain why added scope generally requires more time, money, or both.

Work breakdown structure

Deliverables broken into packages

A hierarchical breakdown of the project's approved scope into smaller deliverables, ending in work packages that can be estimated, assigned, and tracked. It describes what the project will create, rather than the activities or sequence used to create it. It also helps reveal omissions and support cost, schedule, quality, and risk planning.

Rolling-wave planning

Plan near work in detail

A planning approach that outlines the entire project at a broad level while defining the nearest phase in greater detail. After that work is completed, the next phase receives detailed planning. This allows a small business to respond to new information without requiring exhaustive plans for distant work whose details may not yet be known.

Critical path

Longest dependent activity chain

The sequence of dependent project activities that takes the most time from start to finish. A delay to an activity on this path delays the overall project unless corrective action changes the schedule. Activities on other paths may have float, or time they can slip without changing the completion date.

Scope creep

Unapproved scope additions

Small, undocumented additions to project work that bypass the agreed change process. Each addition may seem harmless, but together they consume labor, materials, and schedule capacity while diverting effort from promised deliverables. Scope creep can also introduce new risks and complicate customer acceptance.

Risk register

Record of project uncertainties

A working record of identified project risks and opportunities, including their likelihood and impact, planned responses, responsible owners, triggers, and eventual outcomes. It is updated throughout the project as conditions change. A spreadsheet may be sufficient for a small project, provided the team uses it to guide monitoring and action.

Stakeholder register

Directory of project stakeholders

A record of people or groups affected by, or able to affect, a project. It may include their contact information, roles, expectations, contributions, influence, and communication needs. The register helps a project manager identify who should be consulted, informed, or involved in decisions, and it should be updated when stakeholders change.

Plan-Do-Check-Act

Cycle for improving work

A quality-improvement cycle in which a team plans an approach, carries it out, checks the results, and acts on what it learns. In project work, inspection identifies defects or confirms that deliverables meet requirements. The resulting lessons guide correction and improve how subsequent work is performed.

RACI chart

Roles mapped to activities

A responsibility matrix that indicates who is Responsible for doing an activity, Accountable for its outcome, Consulted for input, and Informed about progress or decisions. It gives a project team a quick view of each person's involvement and helps reveal work with no clear owner or too many competing decision-makers.

Punch list

Final work needing attention

A final list of corrections, incomplete items, or checks identified during a project inspection or customer walkthrough. The team resolves the listed items before treating the project as complete. A punch list makes last-stage obligations visible and helps prevent a vague sense of completion from replacing verified acceptance.

About the Author

Joseph Phillips, PMP is an experienced project management professional who has made significant contributions to the field. As a consultant, instructor, and business owner, he has founded Project Seminars, Inc. and Instructing.com. Phillips has authored several books on project management, including "PMP: Project Management Professional Study Guide" and "IT Project Management: On Track from Start to Finish." His expertise spans various aspects of project management, making him a respected figure in the industry. Phillips' work aims to provide practical guidance and insights for professionals seeking to enhance their project management skills across different domains.

Download PDF

To save this Project Management for Small Business summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.33 MB     Pages: 18

Download EPUB

To read this Project Management for Small Business summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.37 MB     Pages: 22
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 25,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...