BookMentionsBookMentions
Rapid Development
2 recommendations

Rapid Development

Taming Wild Software Schedules

by Steve McConnell

Recommended by Jeff Atwood

Recommended by Jeff Atwood

Check price on Amazon

Proof-backed recommendation

Amazon availability

Reading Profile

Difficulty:hard
Themes:schedule compression vs qualityplanning rigor vs adaptation

Should I read this?

Rapid Development reads like a pragmatic playbook for shrinking software schedules, aimed at developers, technical leads, and project managers. It mixes high-level philosophy with concrete techniques and tooling suggestions so you can spot quick wins and longer-term process changes. The practical sections—checklists, scheduling tactics, and risk-management moves—are the most useful. The limitation: tone can be prescriptive and procedural, and the book leans toward engineering-specific examples (notably Windows-focused), so readers wanting modern agile storytelling or softer leadership framing may find it less relevant.

Read this if...

  • project manager at a product company racing to recover a slipped release — needs concrete tactics to trim scope, reestimate, and manage stakeholder expectations quickly
  • technical lead responsible for multiple Windows-centric components facing unrealistic deadlines — wants engineering-oriented scheduling techniques and tooling recommendations to make delivery predictable
  • engineering manager at a mid-size shop standardizing estimation practices — seeking checklists and repeatable processes to tighten planning across several teams

Skip this if...

  • you'll likely put it down when the book shifts into long lists of templates, checklists, or scheduling math — readers who dislike procedural, prescriptive prose often stop here
  • annoying if you prefer modern agile case studies or human-centered leadership content — the tone is tactical and engineering-first rather than narrative or people-focused
  • frustrating for teams working on non-Windows platforms or very different development cultures — platform-specific examples may feel dated or inapplicable

Rapid Development Project managers, technical leads, and Windows programmers throughout the industry share an important concernhow to get their development schedules under control. Rapid Development addresses that concern headon with philosophy, techniques, and tools that help shrink and control development schedules and keep projects moving. Th...

Before You Buy

Reading Specifications

Difficulty:hard

Themes:
schedule compression vs qualityplanning rigor vs adaptationtooling details vs people problems

Audience Fit

Recommended for:
  • project manager at a product company racing to recover a slipped release — needs concrete tactics to trim scope, reestimate, and manage stakeholder expectations quickly
  • technical lead responsible for multiple Windows-centric components facing unrealistic deadlines — wants engineering-oriented scheduling techniques and tooling recommendations to make delivery predictable
  • engineering manager at a mid-size shop standardizing estimation practices — seeking checklists and repeatable processes to tighten planning across several teams
Not ideal if you want:
  • you'll likely put it down when the book shifts into long lists of templates, checklists, or scheduling math — readers who dislike procedural, prescriptive prose often stop here
  • annoying if you prefer modern agile case studies or human-centered leadership content — the tone is tactical and engineering-first rather than narrative or people-focused
  • frustrating for teams working on non-Windows platforms or very different development cultures — platform-specific examples may feel dated or inapplicable

Check formats, pricing, and availability options for Kindle, physical print, or audiobooks directly.

View available editions on Amazon

Key themes

schedule compression vs qualityplanning rigor vs adaptationtooling details vs people problemsshort-term fixes vs process change

Why recommended

Recommended by 2 sources and appears in Project Management, Most Recommended Books, and Programming.

Recommended by notable people

People and public figures who have recommended this book.

Recommendation Signals

Recommendation proof is sourced from public posts, interviews, reading lists, and cited references.

J

Jeff Atwood

Rapid Development isn't about rapid development. It's about the reality of failure .

Appears In

The Hard Thing About Hard Things
Try This Instead

Not sure if this is the right fit?

Consider The Hard Thing About Hard Things by Ben Horowitz. Recommended by 60 sources.

A blunt, conversational tour through the worst parts of building a company. Horowitz shares personal stories from his own startup failures and recoveries, offering practical wisdom on layoffs, pivots, CEO loneliness, and managing when times are bad. The value is in the honest, experience-based insight you won't get from business school. The limitation is its narrow focus on venture-backed tech startups—if you're not in that world, some advice may feel irrelevant. Reads like a wise mentor telling you what nobody else will.

Similar books

How recommendation signals are reviewed

Each recommendation is collected from a public source — interviews, articles, or curated lists — and linked to its original URL. Books with many verifiable recommendations from respected people rank higher.

Rapid Development

Rapid Development

View on Amazon →