Key Takeaways
Manage projects by joining hard controls to human judgment
More than a schedule. Knudson and Bitz define project management as coordinating people, time, money, quality, and work toward a unique deliverable with a clear beginning and end. Its technical side includes plans, estimates, schedules, and comparisons between expected and actual performance. Its human side includes communication, negotiation, conflict resolution, and motivating people who may not report to the project manager.
Tools need leadership. A chart cannot persuade a functional manager to lend a scarce specialist, clarify a vague request, or surface bad news. The project manager must combine analysis with active relationship-building, while keeping technical direction with the functional experts.
The book’s central strength is its refusal to treat project management as paperwork. The plan is a shared instrument for coordinating action, not a substitute for judgment. This resembles systems engineering, where a design must satisfy technical constraints while functioning in a real organizational environment. The tension is productive: too much emphasis on measurement can make teams optimize the report instead of the result, while too little structure leaves commitments ambiguous. The manager’s task is to keep both realities visible.
Do not launch until budget, authority, need, and timing align
Test the opportunity. The authors’ B-A-N-C criteria ask whether there is a Budget, an authorized decision-maker, a real Need, and a workable Cycle for action. A promising idea may still be a poor immediate project if funding is distant, the contact cannot approve it, or the organization cannot deliver without unacceptable risk. In those cases, conserve proposal effort, maintain contact, and revisit when conditions change.
Find the question first. The chapter opens with a story about Gertrude Stein being asked for the answer and replying by asking what the question was. The point is practical: before proposing a solution, establish what problem matters, who owns it, and why action is needed now.
This gatekeeping model protects organizations from confusing enthusiasm with readiness. It also resembles due diligence in investment: a compelling opportunity still needs a credible sponsor, resources, and a plausible route to execution. The criteria are useful as prompts, not as a mechanical scorecard. Needs can be discovered through a project, and authority may be distributed in complex organizations. A manager should therefore distinguish genuine uncertainty, which calls for investigation, from a missing commitment that makes planning premature.
Give one client ownership, then define acceptance in measurable terms
Name the accountable client. A whole department cannot make timely project decisions, and multiple clients can disagree about priorities or who answers for the outcome. The authors recommend one accountable person, or a small group led by one person, with enough influence and commitment to resolve disputes and approve changes.
Turn wishes into tests. Requirements should describe observable characteristics of the deliverable, not just its hoped-for importance. For a product, this could include performance, reliability, maintainability, ease of operation, regulatory compliance, or production quantity. The initiation record should identify the problem, scope, and completion criteria. Assumptions, risks, constraints, impacts, and resource needs can also be recorded so hidden disagreements become visible before detailed planning.
A single accountable client creates a decision path, while measurable acceptance criteria reduce the space for retrospective disagreement. This is closely related to contract design: parties need a shared definition of what counts as delivery, not merely a shared feeling that the work is important. The approach is strongest when the client also consults affected users. One empowered sponsor can settle trade-offs, but cannot reliably represent every operational need without listening beyond the leadership chain.
Build commitment before demanding performance from a borrowed team
Authority is often indirect. Project managers commonly depend on specialists assigned by functional managers, so staffing requires negotiation, not just names on a chart. A skills inventory shows who can do what; a responsibility matrix assigns one person prime accountability for each task and identifies supporting contributors. Team members should help shape assignments and understand what they have agreed to deliver.
Earn influence deliberately. The authors emphasize clear communication, listening, visible support, and ongoing management backing. A project manager can influence through reliability, negotiate exchanges when priorities conflict, and use formal authority only when necessary. Adding people is not an automatic shortcut: ten team members create 45 potential communication links, while eleven create 55. Sustained overtime also yields diminishing returns.
The practical insight is that staffing is a governance problem as much as a capacity problem. A responsibility chart clarifies work, but it cannot by itself overcome conflicting incentives between project and functional leaders. That is why sponsor support and meaningful input into performance reviews matter. The warning about adding people anticipates a broader coordination principle: communication costs grow with interdependence. Still, team size alone is not the issue; modular work and clear interfaces can make larger groups manageable.
Plan strategically first, then refine near-term work with evidence
Build one integrated plan. The plan connects scope, tasks, responsibility, schedule, resources, costs, and expected accomplishments through a shared work breakdown structure. The authors’ five-step planning model moves from defining the project, to modeling the work, estimating and scheduling it, balancing the plan, and securing approval. Team members should help create the plan so its estimates reflect both practical knowledge and real commitments.
Use a rolling horizon. Top-down planning gives the project direction but may miss detailed work. Bottom-up planning can capture tasks while including unnecessary effort. The rolling wave approach pairs an approximate view of the whole project with detailed planning for the next phase or milestone. As uncertainty falls, estimates and plans are refined rather than pretending early guesses are precise.
The combination of strategic direction and progressively detailed planning is a strong response to uncertainty. It avoids two familiar failures: committing too early to a false level of precision, and allowing detailed task lists to drift away from the actual purpose. Contemporary product development uses similar short planning horizons, though the appropriate cadence depends on the work. Replanning should improve the forecast, not erase accountability. Stable objectives and transparent records help distinguish learning from convenient revision.
Use task dependencies and resource limits to challenge impossible dates
Map the sequence before compressing it. The work breakdown structure lists the tasks; a project network shows which tasks depend on others. Estimators should break large efforts into manageable pieces and account for skill, interruptions, approvals, and waiting time. The critical path is the longest chain of dependent tasks, so delay on that chain can move the project’s finish date. Tasks outside it may have float, or scheduling leeway, but they share that leeway with connected tasks.
Test the trade-offs. A deadline can sometimes be shortened by overlapping work, improving a process, or moving qualified people to critical tasks. Each option has risks and costs. Resource loading reveals overcommitment; leveling can move work within available float or negotiate other adjustments. More staff, overtime, or removing product features may create new problems rather than solve the original one.
This approach replaces deadline theater with causal reasoning. A network makes visible why a finish date follows from dependencies, and resource analysis exposes conflicts hidden by a simple calendar. The key discipline is to treat acceleration as a change in risk, scope, cost, or sequence, rather than as a motivational demand. Critical-path calculations remain only as good as the underlying estimates and assumptions. A mathematically exact schedule can still be wrong if the work is poorly understood.
Treat every scope or baseline change as a priced decision
Separate product changes from plan changes. Scope changes alter what the deliverable must do; baseline changes alter agreed targets such as schedule, cost, or resource use. Both can arise from clients, regulators, external conditions, or problems inside the organization. Without a recorded process, small requests accumulate until the original commitments are impossible to meet.
Trace the consequences. For substantial scope requests, the authors describe a process in which the request is logged, its impact is investigated, and an authorized group decides whether to approve it. Analysis should consider effects on time, money, staffing, technical quality, and organizational risk. A small request may need only a brief comparison of the current plan with the proposed one. Approved changes should be documented and communicated.
Change control is not bureaucratic resistance to improvement. It is a way to make the exchange explicit: a new feature may be worth the added time, but decision-makers should see the cost and choose knowingly. This resembles configuration management in engineering, where a system’s current approved design must remain identifiable. The process should be proportional. A heavyweight committee for every minor adjustment creates delay, while informal, undocumented changes invite scope drift and blame.
Find trouble in daily conversations, then verify it in reports
Control is a continuing cycle. The authors’ project-control model updates status, analyzes its impact, acts on variances, publishes revisions, and informs management. Informal control means staying in contact with the team, observing work, and hearing problems early. Formal control uses periodic data and reports to compare actual performance with the approved plan. One cannot replace the other: monthly reporting may reveal a problem long after it began, while informal impressions need factual checks.
Report for decisions. A useful status report summarizes recent progress, near-term milestones, budget position, threats requiring help, and people deserving recognition. Review meetings should focus on causes, consequences, owners, and next actions. Trend analysis matters because a project can look acceptable today while forecasts of its finish date or cost steadily worsen.
The strongest control systems are both social and informational. Frequent contact lowers the cost of raising a concern, while consistent reporting gives managers a common record for deciding what to do. This aligns with modern safety practices in which near misses are surfaced before they become failures. Yet visibility can become surveillance if every update is treated as a performance test. Reports work best when bad news is rewarded with timely problem-solving rather than punished for disturbing the picture.
Measure completed value, not elapsed time or task-count theater
Count accomplishment, not activity. Achievement monitoring tracks whether milestones are complete. Accomplishment monitoring assigns each milestone a weight, then compares the value of work scheduled, the value actually completed, and the money spent. Weighting by budget is convenient but can overvalue expensive purchased items; person-hours, labor budgets, or expert-assigned points have different limitations.
A worked example exposes the danger of simple percentages. In a five-week task to produce 100 units, the plan scheduled 45 units by week three, not 60, because production was expected to accelerate over time. Producing 50 units was ahead of that schedule, yet spending $5,000 against a $3,375 planned amount showed poor cost performance. A nonlinear baseline gives a more honest reading than assuming output proceeds evenly.
Earned-value logic helps separate three questions that a single status label can blur: how much work was planned, how much was delivered, and what the delivery cost. The nonlinear example is especially useful because early setup or learning can make linear comparisons misleading. Weighted milestones still require judgment: a percentage complete is only credible if the chosen weights represent meaningful work. Metrics should challenge team estimates, not displace direct inspection of quality and usefulness.
Buy software last; invest first in method, training, and support
Software calculates, people decide. A project tool can compute start and finish dates, critical paths, resource loads, and comparisons between plans and actuals. It cannot define objectives, build the work breakdown structure, choose task owners, or create reliable estimates. The authors recommend defining organizational requirements first, testing candidate tools against representative project data, and checking reporting, resource, cost, and vendor-support features.
Make the practice sustainable. Training can include classroom instruction, self-paced computer lessons, simulations, and mentoring on live work. Administrative support can maintain standards, handle data and reports, and preserve historical plans. These supports free project managers to focus on coordination and decisions. They should be seen as part of the operating system for project work, not as optional extras after a software purchase.
The book’s technology advice remains useful because it distinguishes computation from judgment. Automation can make a weak method faster and more polished without making it sound. Organizational capability depends on a shared vocabulary, trained users, reliable data, and support for routine administration. Central standards also create a trade-off: consistency improves portfolio visibility, while local teams may need different workflows. A sound implementation standardizes the information needed for coordination without forcing every project into identical procedures.
Analysis
The book’s most durable argument is that project success depends on making commitments credible. A deliverable must be defined well enough to test, work must be decomposed into accountable units, estimates must come from people who understand the work, and plans must be revised when evidence changes. That chain explains why the authors repeatedly pair technical mechanisms with organizational behavior. A schedule without committed resources is fiction; a client without decision authority is a bottleneck; a report without trust is a delayed confession.
The book is unusually alert to matrix organizations, where project managers carry responsibility without direct control over many contributors. Its emphasis on negotiation, sponsor backing, role clarity, and informal contact addresses the real source of many project failures: not an absence of charts, but a mismatch between formal plans and actual authority. Its discussion of Frank, the manager who meets arbitrary deadlines by quietly degrading product quality, is a particularly sharp account of how incentives can corrupt reported success. On-time and on-budget delivery is not success if the product no longer meets its purpose.
The methods also have limits. Formal baselines and earned-value measures are most useful when work can be decomposed and accomplishment observed. Exploratory work may not yield stable task sequences or meaningful milestone weights early on. In those settings, progress measures should be treated as hypotheses and revised as learning develops. Likewise, a single accountable client streamlines decisions but should not silence users, technical experts, or affected communities.
The book was written before contemporary collaboration platforms and agile vocabulary, yet its rolling-horizon planning, frequent feedback, and change discipline remain recognizable. Its deeper lesson is not to freeze a plan. It is to make the current plan explicit, measure reality against it, and negotiate changes openly. Project management becomes valuable when it exposes trade-offs early enough for people with authority to choose among them.
Glossary
B-A-N-C Criteria
Project opportunity screenA four-part screen for deciding whether a project opportunity is ready to pursue: Budget, Authority, Need, and Cycle. It asks whether funding exists, the contact can secure approval, a defined need can be met, and the client’s timing permits action. Weak answers may justify waiting or declining rather than investing heavily in a proposal.
Work breakdown structure
Hierarchical task checklistA structured decomposition of the work required to produce a project’s deliverable. Major work areas are divided into smaller tasks until the work can be estimated, assigned, and monitored. Each lowest-level task should have an accountable owner and a measurable output. The structure becomes a foundation for schedule, resource, and budget planning.
Responsibility matrix
Task ownership mapA table that connects project tasks with the people responsible for them. Each task has one person with prime responsibility for ensuring completion, while other contributors may be listed in supporting roles. The matrix makes commitments visible to the project manager, team members, and functional supervisors, helping prevent gaps and overlapping accountability.
Integrated project plan
Unified project baselineA coordinated set of plans for project scope, schedule, costs, human resources, assets, and expected accomplishments. These components use a shared work breakdown structure so changes and progress can be compared consistently. The plan communicates commitments, supports resource coordination, and provides the baseline for identifying variances and considering corrective action.
Five-Step Planning Model
Sequence for building plansThe authors’ planning sequence begins by defining the project, then models its work, estimates and schedules that work, balances the plan against resource limits, and obtains approval before publishing it. Each stage depends on earlier decisions. The process aims to produce a realistic, coordinated set of commitments rather than a schedule assembled without team input.
Rolling wave approach
Progressive planning horizonA planning method that pairs an approximate view of the entire project with detailed planning for the work that can currently be understood. The detailed horizon may extend to a phase or major milestone. As uncertainty is resolved and the project advances, the next segment is planned with better information and the overall forecast is refined.
Critical path
Longest dependent task chainThe longest sequence of dependent tasks from a project’s start to its finish. It determines the shortest possible project duration under the current plan. A delay to a task on this path can delay the whole project, while tasks outside it may have some scheduling flexibility. The path can change when durations or dependencies change.
Float
Available schedule leewayThe amount of time a task can slip before it affects the project’s planned finish or a dependent task’s required timing. In the book’s network calculations, task float is found by comparing late and early finish times. Tasks on the critical path have no float, and tasks on a shared noncritical path may need to share available leeway.
Resource leveling
Balancing resource demandThe adjustment of task timing, duration, assignments, or other work arrangements to bring resource demand closer to available capacity. Tasks may be moved within their float, overtime or temporary help may be considered, or priorities and deadlines may be renegotiated. Leveling may preserve the finish date or extend it, depending on the chosen constraints.
Earned value
Budgeted value of workA way to assess project accomplishment by assigning planned value to completed work and comparing it with the value scheduled and the actual cost incurred. The comparison indicates whether progress is ahead of or behind schedule and whether completed work is over or under budget. Its usefulness depends on credible milestone definitions, weights, and baselines.
Schedule performance index (SPI)
Schedule efficiency ratioA project performance measure calculated by dividing the budgeted value of milestones performed by the budgeted value of milestones scheduled. A value of 1 indicates that earned progress matches the plan; below 1 indicates less value completed than scheduled, while above 1 indicates more. Repeated readings are more informative as a trend than a single reading.
Cost performance index (CPI)
Cost efficiency ratioA project performance measure calculated by dividing the budgeted value of completed milestones by the actual cost of completing them. A value of 1 indicates that completed work cost what was budgeted; below 1 indicates worse cost efficiency, and above 1 indicates better efficiency. It can support forecasts, but depends on trustworthy cost and accomplishment data.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.