The real world and its constraints have this terrible tendency to intrude on the idyllic visions imagined around software development methodologies. Budget cuts, people quitting, timelines changing every week, internal politics, sabotage, personality issues - basically everything but the "methodology" itself.
The advice often comes (including in one of the XP books) that the answer to "bad projects/people/environments that you can't change" is to get a new job; this may work at the individual level (sometimes), but it does nothing to actually fix the broken projects, environments, or people themselves.
There is indeed no silver bullet. All these decades later, and many people still refuse to accept that.
The advice often comes (including in one of the XP books) that the answer to "bad projects/people/environments that you can't change" is to get a new job; this may work at the individual level (sometimes), but it does nothing to actually fix the broken projects, environments, or people themselves.
There is indeed no silver bullet. All these decades later, and many people still refuse to accept that.