What Is Fear-Driven Development (FDD)?
Fear! It's the first word in Fear-Driven Development. And it's probably a big part of your software development process but, if you're building software for customers instead of yourself, shouldn't it be Customer-Driven Development? Fear-driven development (FDD) is a term invented by software developers when the fear of making mistakes or negative consequences prevents a team from trying something new. Fear-driven development can stifle whole groups, making it difficult for them to innovate or be creative and efficient. The root cause of fear-driven development is usually a management style that stifles risk-taking, preventing people from learning from their mistakes and delivering quality software faster. Fear-driven development (FDD) is an anti-pattern in software development that limits creativity and increases risk; fear-driven development is often attributed to Scott Hanselman. He describes "organizational fear" and "analysis paralysis", which can lead companies to become obsessed with double-checking and triple-checking code, restricting meetings, and trying to throttle feedback and otherwise attempting to control the process based on the fear that something will turn out wrong. Experts explain how this doesn't just undercut the ability of developer teams to innovate but can be extremely harmful to your company. Fear-driven development is the most extreme form of productivity. It's when company leadership rules by instilling fear in their employees. It might push employees to work overtime, including weekends and evenings, or otherwise make them perform by telling them their jobs are at stake. It's a common approach in many industries, but productivity experts would not recommend this punitive management process and often describe how it might break a company down. Fear-driven development has been a popular topic in the software industry for years. Fear-driven development has been a popular topic in the software industry for years. This is because working under pressure can lead to mistakes and ultimately drive away your top talent. Fear-driven development has been a popular topic in the software industry for years. You might have heard of it being called "tiger teams" or "fire drills." Or perhaps you've known a team whose leader had to yell at people to get them to care about their work. It's when the company's management style causes employees to feel afraid. It can be terrible if it happens over long periods because it saps morale and often leads people to leave your organization.
Related Terms by Software Development
Join Our Newsletter
Get weekly news, engaging articles, and career tips-all free!
By subscribing to our newsletter, you're cool with our terms and conditions and agree to our Privacy Policy.
































